I have recently been supporting a fault that a friend of mine (new to Lync) was experiencing in his lab environment but thought it would be a useful blog post!
The configuration was as follows;
- 1x Lync Server 2013 Standard Edition, deployed on host 1 – LYNCSE01.domain.local
- 1x Lync Server 2013 Standard Edition, deployed on host 2 – LYNCSE02.domain.local
- 1x Office Web Apps, associated with both of the aforementioned pools – OWA01.domain.local
- Clients homed on each pool connected successfully and consuming all communication modalities
The next step in his environment was for Pool Pairing to be configured, which is a great new addition to Lync Server 2013.
The topology can be see below, published successfully:
The next steps, as per the post installation ‘to do list’ were to:
Update Lync Server with the changes defined in the topology by running local Setup on each server in the following list.
Server FQDN: LYNCSE01.domain.local, Pool FQDN: LYNCSE01.domain.local
Server FQDN: LYNCSE02.domain.local, Pool FQDN: LYNCSE02.domain.local
Run the Invoke-CsBackupServiceSync cmdlet to ensure conferencing data is replicated.
Invoke-CsBackupServiceSync –PoolFqdn LYNCSE01.domain.local
Invoke-CsBackupServiceSync –PoolFqdn LYNCSE02.domain.local
Setup was ran on both standard edition servers, no errors there – but when it came to running the command ‘Invoke-CsBackupSyncService’, the following error was presented
Once quick look at the services running on the machine would identify the problem, the LyncServerBackupService was not running. Starting this allowed the command to be run:
Next up, confirming the status of the pool pair. Running the command ‘Get-CsBackupServiceStatus -PoolFQDN LYNCSE01.domain.local’ now presented a new error:
You don’t have required permission to perform Windows Communication Foundation (WCF) call to backup service instance on computer
One key point to remember, that is often overlook, is to always check the ‘to do list’ following topology changes being published. If this had been done, the account being used to deploy Lync would have been a member of RTCUniversalServerAdmins (this is also identified as a requirement when running Get-CsBackupServiceconfiguration (see below))
Once added to the RTCUniversalServerAdminsGroup, the cmlets were successful ran, and the ready state was output!