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.

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.

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.

Lync 2010 Enterprise upgrade to 2013, SQL requirements.

Topology Builder will display the following message to inform you of this issue: “The SQL server [FQDN of the server] already contains a SQL instance hosting role ‘User Store’.”

I recently discovered a small bump in the road when it comes to upgrading an excisting Lync 2010 Enterprise pool to Lync 2013 Enterprise.

The SQL server instance not only has to be unique to the Lync 2013 Enterprise Pool, but it also has to be on a dedicated SQL server not already in use by the Lync 2010 Pool.

This means, when upgrading from Lync 2010 Enterprise to Lync 2013 Enterprise, take into concideration that you would need a new SQL server as well.
The Microsoft documentation on the subject is not very easy to find(unless you search specifically for SQL migration scenarios), and even in this article http://technet.microsoft.com/en-us/library/gg425764.aspx it’s not clear that the requirement for a new SQL server is only for an Enterprise scenario.

A possible workaround(in a small organization) could be to install Lync 2013 Standard Edition, migrate users and move the CMS, then reinstall Lync 2010 Enterprise server as Lync 2013 Enterprise pointing towards the old SQL server and then move everything back…

Your Call 🙂