The Lync 2010 Server Merge-CsTopology -TopologyXmlFilename Powershell command will fail with the following error:
WARNING: Total number of errors is 1
WARNING: Total number of warnings is 0
WARNING: Check for errors, warnings, and details in the log file at the following location:
Merge-CsLegacyTopology : The domain "contoso.com" in "Office Communications Server 2007" / "Office Communications Server 2007 R2" has authoritative "True".
The domain "contoso.com" in Lync Server 2010 has authoritative "False".These two values need to be equal before you can continue merging the topology.
At line:1 char:23+ Merge-CsLegacyTopology <<<< -TopologyXMLFilename c:\wave14\xml_filename5.xml+ CategoryInfo: InvalidData: (contoso.com:String) [Merge-CsLegacyTopology], Exception + FullyQualifiedErrorId :BuildTopologyError,Microsoft.Rtc.Management.Coexistence.GetOcsWMITopologyCmdlet
- The Communications Server Authoritative setting for the pool's SIP domains are set to a value of True
- The Lync 2010 Server Authoritative setting for the pool's SIP domains are set to a default of False
- The Lync 2010 Server Authoritative setting cannot be changed using the Lync 2010 Server Topology Builder
- The Lync 2010 Server Authoritative setting cannot be changed using the Lync 2010 Server Powershell cmdlets
Before the Lync 2010 Server Merge-CsTopology Powershell cmdlet can complete the Merge migration process between the Communications Server and Lync 2010 Server pools, the Communications server pool's SIP domains Authoritative value must be set to False.
Warning: The resolution for this issues requires making permanaent changes to Windows Active Directory, directory service domain that hosts the Communications server infrastructure. Please make sure that you perform a current back up of the Active Directory, directory service that hosts the Communications server enabled domain.
- From the console of a Communications Server that hosts the front end server role, open the Run feature from the Start menu
- Type in WBEMTEST and click on OK to open the Window Management Instrmentation Tester dialog
- Click on the Connect button, click on the Connect button again to accept the root\cimv2 default choice
- Click on the Enum Classes... button and choose the Recursive option
- Click on the OK button and allow the list of WMI classes time to load
- Scroll down the list of WMI classes and locate MSFT_SipDomainData WMI class
- Select the MSFT_SipDomainData WMI class from the list and double click on it
- Click on the the Intances button located on the Object Editor for MSFT_SipDomainData dialog to retrieve the active instance of the class
- In the Query Result dialog double click on the active instance of the MSFT_SipDomainData WMI class to access its properties
- Scroll down to locate the Authoritative property to select it
- Click on the Edit Property button and chose the Null option or replace TRUE with FALSE.
- Click on the Save Property button
- Click on the Save Object button
- Click on the Close button three times and then click on the Exit button
- The changes will be replicated from the Communications Server WMI store to the Windows Active Directory, directory service that is hosting the Communications Server infrastructure. These changes will be dependent on the Active Directory replication policies for the domain.
Article ID: 2429891 - Last Review: Nov 17, 2010 - Revision: 1