Wednesday, February 25, 2015

Speaking at Microsoft Ignite in Chicago

I am excited to announce I am going to Chicago and attend Ignite 2015 as a speaker. My proposal for a session on Backup and restore Skype for Business has been accepted. This is my third international event, and first one this year.

The session will be about what to consider when planning for a disaster recovery scenario, and how to do it.

Apparently, the TechedEU 2014 session was slightly more advanced than the advertised level 300, and this session has been marked as a lvl 400.

Be prepared for a lot of PowerShell commands during the presentation.

Title: Managing Backup and Restore in Skype for Business
Track: Skype for Business
Level: 400
Session: TBA
Link: Session details
Time: TBA
Room: TBA

Abstract:As unified communication becomes an important part of the infrastructure, it is equally important to have a good understanding on how to quickly restore its availability in the event of an outage. Even a well-designed High Availability solution may encounter loss of data, misconfiguration, or server failure. This session addresses which components the administrator will need to pay attention to when designing his disaster recovery plan in Skype for Business.

Friday, February 13, 2015

Lync client may connect to a non federated partner, even if you though it should not.

Here is an "interesting" observation I did a couple of days ago. The customer has chosen not to allow DNS discovery of federated partners, but will allow federation with selected partners on the allow list. After a while with this configuration, the customer called me and told me they had mixed experiences with the solution. There were times when meetings with a partner (NOT on the allow list) actually would work, even if they expected the meeting to fail.

They asked me to verify the settings, and to investigate why some users reported they could connect to a meeting others couldn't.

This is what I saw on a client who failed to connect:

5 messages. And the interesting one would be the 504 message: "Can not route".

And then the client stops trying, as I would expect it to.

But here is an interesting twist. Log on with the same client from a remote connection (through edge), and then let's see what happens.

The client does not honor the 504 message "Can not route". It continues and connects to the meeting, unexpectedly. How can that be?

The interesting part is what happens after the 504 message. First the client acknowledges the rejection, but then it does something it didn't do on the inside. There is a new invite, trying to connect anonymously:

And this connection is allowed. Quite confusing for the end user, actually. But now they know.

It is important to note the user was allowed for federation in this scenario, but the domain in question was not in the allow list and DNS discovery was not allowed. Also, the organizer on the other side was allowing anonymous invites.

Monday, February 9, 2015

Restore Lync User Data demo

I have created a video, showing how you may restore Lync User data with a backup created with the Lync 2013 backup script v3.5

The video is less than 2 minutes long, and shows a restore of my lab in real time. It has no sound, but the CC will explain what's going on.

The important giveaways from this movie should be:
  • Permissions required to run Lync commands are the same as previous demos. 
  • I have chosen to do an update rather than a full import
  • Service can be running during an import
  • User should log out and back in after the update is complete
As always, you can find the script right here.