Tuesday, March 22, 2016

Event 1034, LS File Transfer Agent Service fail after server removal

After a pool and his associated Edge server were decommissioned, I consistently receiving this error:


Skype for Business Server 2015, File Transfer Agent service encountered an error while accessing a file share and will continuously attempt to access this file share until this issue is resolved. While this condition persists, replication to replica machines might not occur.

Access denied. (\\RemovedServer.ad.local\xds-replica\from-master\data.zip)

Cause: Possible issues with file share permissions. This can occur if the computer hosting the file share has outdated cached credentials for the computer that is trying to access the file share.


For details about how to resolve file share permission issues, see the product documentation.

Event ID: 1034
Task Category: 1121

Next I need to check some leftovers from the decommissioning.
Checking the Central Management Store Status gave me a hint:

PS C:\Windows\system32> Get-CsManagementStoreReplicationStatus -CentralManagementStoreStatus

LastUpdatedOn                        : 22/03/2016 6:48:58 PM
ActiveMasterFqdn                     : ActiveServer.ad.local
ActiveMasterLastHeartBeat            : 22/03/2016 6:52:18 PM
ActiveFileTransferAgentFqdn          : ActiveServer.ad.local
ActiveFileTransferAgentLastHeartBeat : 22/03/2016 6:52:17 PM
ActiveReplicas                       : {ActiveServer.ad.local, EdgeServer.ad.local}
DeletedReplicas                      : {RemovedServer.ad.local, RemovedEdgeServer.ad.local}

PS C:\Windows\system32>

I was able and saw the DeletedReplicas.

Normal the Invoke-CsManagementStoreReplication should solve the problem, but simply it didn't work out.

Even if you had decommission a server proper, which is:
1. remove from Topology
2. must Disable-CsComputer

If you run Bootstrapper, the Disable/ Uninstallation is not working.

They stuck still in the DeletedReplicas.

The only solution,(but not support if you can run Disable-CsComputer any longer) is, you have to remove them manually from the XDS database.

Go the SQL CMS Server and execute the script finding the left over servers:

USE xds
GOSELECT [ReplicaId]
FROM [dbo].[Replica]

Than identify the DeletedReplica Server and delete them with:

delete [dbo].[Replica] where [ReplicaId] in (1,4)
where (1,4) are the column identified with the DeletedReplicas server.

This should support this issue.

Friday, March 18, 2016

Move User from a dedicated Pool via Powershell

How to move users to different pool or how to migrate user to another pool.

Simple and often forgotten:

The Get-CsUser command do not offer a -Pool or -SourceFQDN parameter!

Therefor you need to use pipelining and filtering.

Get-CsUser -Filter {RegistrarPool -eq "CurrentPoolFqdn"} | Move-CsUser -Target "TargetPoolFQDN" -MoveConferenceData

The Option CurrentPoolFqdn and TargetPoolFqdn must be specified in the form of: server.domain.local
MoveConferenceData : Please don't forget moving the users conferencing data stored in the File Share.
Note that you should not use the MoveConferenceData parameter if you are moving users as part of a disaster recovery procedure. Instead, you should rely on the backup service for moving conference data as part of a disaster recovery procedure

Care about users conferencing ID is not necessary while moving a user to new pool:

When you move a user to an Skype for Business or Lync Server 2013 pool, the data for the user is moved to the back-end database that is associated with the new pool.

This includes the active meetings created by the user. For example, if a user has configured a my meeting conference, that conference will still be available in the new Skype for Business/ Lync Server 2013 pool after the user has been moved.
The details to access that meeting will still be the same conference URL and conference ID.
The only difference is that the conference is now hosted in the new pool, and not in the source pool.

The Get-CsUser command has the following Properties which can be used for filtering:

Identity                    : CN=USER,CN=Users,DC=ADdom,DC=local
VoicePolicy                 :
VoiceRoutingPolicy          :
ConferencingPolicy          :
PresencePolicy              :
DialPlan                    :
LocationPolicy              :
ClientPolicy                :
ClientVersionPolicy         :
ArchivingPolicy             :
ExchangeArchivingPolicy     : Uninitialized
PinPolicy                   :
ExternalAccessPolicy        :
MobilityPolicy              :
PersistentChatPolicy        :
UserServicesPolicy          :
CallViaWorkPolicy           :
ThirdPartyVideoSystemPolicy :
HostedVoiceMail             :
HostedVoicemailPolicy       :
HostingProvider             : SRV:
RegistrarPool               : Pool or StdServer.ADDomain.local
Enabled                     : True
SipAddress                  : sip:USER@SIPDOM.COM
LineURI                     :
EnterpriseVoiceEnabled      : False
ExUmEnabled                 : False
HomeServer                  : CN=Lc Services,CN=Microsoft,CN=1:1,CN=Pools,CN=RTC
DisplayName                 : USER for TEST
SamAccountName              : USER

I always let the entire process being documented to >C:\User-Move.txt this is for later validation and error correction.

Get-CsUser -Filter {RegistrarPool -eq "lync2013pool.dom.ad"} | Move-CsUser -Target "SfBPool.dom.ad" -MoveConferenceData > C:\move-user.txt 

Move user in event of a Data Center failure:

Well if a DC is in failover mode, there are two things happen.
  • If the resiliency mode is active, the conferencing focus is still hold on the other side and therefor the conferencing ID stuck there and it will fail!
  • If the DC fail with a proper failover incl. the SQL copy and you have activated the failover manually! Everything is working fine.
If you google about Conferencing Focus Lync you find a lot for my fellow MVP mate writing about this.
Assuming, you move the user to new pool permanently, this conferencing focus will be copied as part of the user setting. So the same ID is valid.
Just last weekend I was migrating an entire pool to new pool and everything got moved and all conferences stood as expected.
and if everything failed:
This is from MVP mate Richard Brynteson, Lync MVP, Microsoft Certified Solutions Master, he work it out very proper, if you like to understand conferencing.

Btw you can also download my Skype for Business and Lync Troubleshooting Guide: https://gallery.technet.microsoft.com/lync/Skype-for-Business-and-7857597d

Sunday, March 13, 2016

Skype for Business Client Update Februar + March 2016

Let me give you an overview about the changes applied with the SfB Client Update from February and planned for CU for March:

  • Auto-accept presented content
  • Single click Desktop Sharing (single Monitor)
  • Meeting join with / without mic or speaker
  • better sharing real estate
  • Notify other when everyone can see presented content
  • fast switching to newly connected devices without call on hold
  • additional connected monitor: prompt fir sharing
  • auto hide sharing tool bar
  • smart Team Contacts
  • Meeting Reminder

A new video technology/ codec for P2P screen sharing is implemented:
The P2P sharing is changed from RDP to High Fidelity Video-Based Screen Sharing (VBSS)
With the targeted update for March, it should be implemented for Meeting too.
Requirement ist the Office 2016 client. NOT the Office 2013 updated client Version (15).

Fast and more efficient:
15 FPS with VBSS instead of 8 FPS with RDP



Therefor it becomes als more reliable


More news are:
Co-Author OneDrive Office Document.
You can now collaborate on Office document with OneDrive in a meeting. The Access is granted automatically to the office document (OD4B). you will see the editor who wrote to the document. It is a concurrent editing possible.

Most important request are implemented:
Offline Messaging
  • Send messages to contact even if they are not signed-in
  • Read missed messages in email of in Skype for Business
  • Use unread count badges to navigate through missed messages
  • Read on any device with SfB/Lync that supports missed messages

Some more info's were:
The SfB Client for MAC is coming soon to a preview.
And yes, it is true, try to discover how you can utilize Office 2016 Click2Run in your enterprise.
Several new feature are only available with the C2R version and will not be implemented in the MSI package.