Skype for Business Event ID 1034.

After migrating to Skype for Business and removing Lync 2010/2013 pools, you may encounter an event ID 1034 stating that the LS File Transfer Agent encountered an error while accessing a file share.

The file share referenced will be the share on the removed Lync 2010/2013 pool. If you run the command Get-CsCentralManagementStoreReplicationStatus -CentralManagementStoreStatus, you will se an entry of DeletedReplicas that states the server FQDN of your deleted Lync pool/server. If the server is deleted from the topology not to be used again, you can proceed with deleting the server from the XDS database.

 

The easiest way to accomplish this, is to make sure that all Lync server components are removed from the Lync server in question. Simply go ahead and remove the Lync components from the server using Add/Remove programs. Make sure to reboot the server after the removal of the Lync components. The error message in the event log should disappear after this operation.

If this is not successfull, you will have to remove the replica ID’s from the SQL database(XDS).

This procedure from the UC Lobby blog by David Paulino should do the trick.

Skype for Business Online and PSTN Conferencing

As you all probably know, Microsoft has enabled the possibility of having Dial-in PSTN Conferencing in Skype for Business Online. In order to do this, you either have to have an E5 license plan in O365, or you can purchase the add-on for PSTN Conferencing in your excisting E1 or E3 plan.

PSTN Conferencing is a very valuable add-on to the O365 Skype for Business as it will enhance the possibilities of joining meetings without having to use a client.

To read more about PSTN Conferencing, visit this site on Microsoft.com:

Dial-in conferencing in Office 365

To se which countries have PSTN Conferencing available, check out the list here.

Skype for Business Server 2015 Updates and Build Numbers.

In this post I will try to keep you updated with the current releases and build numbers for Skype for Business 2015 Server.

As of now, there has been released five updates for Skype for Business Server 2015. The Microsoft download page is updated with the latest SkypeServerUpdateInstaller, so the link will always point to the most recent CU.

Server updates and Build Numbers:

May 2017 Update – Build number 6.0.9319.281(CU6)
Be adviced: CU6 has been reported to break Web Conferencing Edge service due to updates to the .Net Framework.
Check out this TechNet article if you experience problems.

February 2017 Update – Build number 6.0.9319.277(CU5)

November 2016 Update – Build number 6.0.9319.272(CU4)

June 2016 Update – Build number 6.0.9319.239(CU3)

March 2016 Update – Build number 6.0.9319.235(CU2)

November 2015 Update – Build number 6.0.9319.102 (CU1)

 

This post will update as new CU’s are released.

Upgrading to Skype4B, things to consider.

Wrote this blogpost in May when attending the Microsoft Ignite Conference in Chicago.
Should have been posted then, but I still think it’s relevant 🙂

As you all know, the Skype4B server upgrade can be done as an in-place upgrade from Lync 2013. However, there are things to consider.

If the server is a Lync 2010 server, there is no way to do an in-place upgrade. Migration is the only way.

Lync 2013 supports the in-place upgrade as long as you can schedule downtime because the services are removed during the process.

When it comes to the server OS, you would want to concider upgrading the server if you’re on WinSrv 2008 or 2008R2. The Skype4B server install will upgrade windows fabric to the latest version, but only on 2008R2.

Recommendation: Win2008 or 2008R2 should be upgraded to 2012R2.

Implication: The upgrade process to Skype4B will have to be done as a migration if your servers are on Win2008 or Win2008R2.

Skype for Business – Recover Your Deployment from a Deleted or Corrupt CMS

Incredibly useful post by Mark Vale(@unifiedvale) on how to recover from a corrupt CMS. Please do note the points in the article about making a backup of your Lync environment. You never know when you need it.

Source: Skype for Business – Recover Your Deployment from a Deleted or Corrupt CMS

Implementing backup of your Lync/Skype for Business environment can be accomplished in many ways. Please check out MVP Lasse Wedoe’s blog on how to as one of several resources.

Skype4B/Lync Edge Server not replicating.

In a short period of time I’ve encountered two different cases of the Edge server not replicating. Everything seems OK, but the changes simply won’t move to the Edge.

I found a great blogpost by Jaap Wesselius here that describes the exact problem and how to fix it.

Simply add the following to the registry of the Skype/Lync Edge server:

New REG_DWORD(32bit) ClientAuthenticationTrustMode with value “2” in HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SecurityProviders\SCHANNEL

Restart the Edge server(not just the services) and toggle the Skype/Lync replication service on the FrontEnd server. Wait a few and the replication should be OK.

Lync client showing duplicate numbers on contact card.

A customer contacted me with a request to look into a problem regarding duplicate numbers in the Lync client contact card. When a Lync user would call a colleague, the numbers displayed in the list would be duplicates with normal eight digits and the same number with a + sign in front. After some digging in AD, Exchange and Lync without figuring out where this number came from, I kind of stumbled across the solution.

I created a normalization rule that normalized all numbers starting with a +, removing the + and adding +47(for Norway):

RegEx Matching pattern ^\+(\d{8})$ (for Norwegian eight digit phone numbers, replace with your own digit length), Translating rule +47$1 (Norwegian national prefix, replace with your own).

This change in normalization for workaround purposes turned out to be a valid solution to remediate the problem with duplicate numbers. Seems like Lync is collapsing the numbers based on the newly created normalization rule, thereby de-cluttering the number lookup in the contact card and call rooster.

Maybe this is documented somewhere in MS documentation, but if not, here’s how to fix the problem if you stumble across it 🙂

Comments greatly appreciated.

Upgrading to Skype4B, things to concider.

Blogging from the Microsoft Ignite conference in Chicago.

As you all know, the Skype4B server upgrade can be done as an in-place upgrade from Lync 2013. However, there are things to concider.

If the server is a Lync 2010 server, there is no way to do an in-place upgrade. Migration is the only way.

Lync 2013 supports the in-place upgrade as long as you can schedule downtime because the services are removed during the process. For enterprise pools you would have to stop the entire pool to upgrade, so users will have to be moved to secondary pool or downtime will occur(there is no option for co-excistense of Lync 2013 and Skype for Business in the same pool).

When it comes to the server OS, you would want to concider upgrading the server if you’re on WinSrv 2008 or 2008R2. The Skype4B server install will upgrade windows fabric to the latest version, but only on 2008R2.

Recommendation: Win2008 or 2008R2 should be upgraded to 2012R2.

Implication: The upgrade process to Skype4B will have to be done as a migration if your servers are on Win2008 or Win2008R2.