Login |  About us, Contact us & Follow us |   
Index   UC Articles... Important Links!

Merge 2007 or 2007 R2 Topology

Step by Step: How to install Lync Server 2010

After you have installed Lync Server 2010, Lync users should communicate with each other without any problem. But in a co-existence scenario you need to merge the OCS 2007 R1\R2 and Lync topologies. Otherwise OCS 2007 R1\R2 and Lync users wont be able to communicate with each other.

The Merge feature allows you to import information from your previous Office Communications Server environments, and integrate it into a consolidated view alongside your Lync Server 2010 deployment.

To complete the process, install WMI Backward Compatibility Package on the Lync Front End Server (or the server from where you’ll run the merge operation).

From your installation media, navigate to \SETUP\AMD64\SETUP\OCSWMIBC.MSI.

Install OCSWMIBC.MSI.




 

After you have installed WMI Backward Compatibility Package, start Topology Builder on the Lync Server.

Click Start, click All Programs, click Microsoft Lync Server 2010 (RC), and then click Lync Server Topology Builder.

Select the option to Download topology from existing deployment and then click OK.

In the Actions pane, click Topology and then Merge 2007 or 2007 R2 Topology.







 

Click Next to continue.

In Specify Edge Setup, do one of the following:

    • If you have Edge Servers in your Office Communications Server 2007 R2 environment, click Add and then enter the information about your Office Communications Server 2007 R2 Edge Server environment.
    • If you do not have Edge Servers in your Office Communications Server 2007 R2 environment, click Next to move ahead without providing edge info.




 

In Specify Edge Setup, click Next.






 

In Specify Internal Edge Settings Information, enter the relevant information for your Edge pool’s internal FQDN and ports as needed, and then click Next.




 

In Specify External Edge, enter the Web Conferencing FQDN information for your Edge Server and then click Next.




 

In Specify Next Hop, enter the FQDN of the next hop location in your environment, and select whether it is a Front End pool or a Director. Then click Finish.







 

In Specify Internal SIP port setting, select the default automatic discovery setting (that is, if you did not modify the default SIP port). Change as appropriate if you are not using a default port of 5061.




You may receive following error if SIP domains configured in OCS setup and Lync setup differ. You need to ensure that you have exactly same number and name of SIP domains configured in both environments.

  The value of default domain in  "Office Communications Server 2007" / "Office Communications Server 2007 R2" is "sip.in". The value of default domain in  Lync Server 2010 (RC) is "sip.com".These two values need to be equal before you can continue merging the topology.




 

After successful merge operation, you will see an additional site “BackCompatSite” in the topology builder.


 

Now, run the “Publish topology” wizard. From the Actions pane, select Publish Topology, and then click Next





 

 

When the Publishing wizard completes, click Finish to close the wizard.

 

From the Microsoft Lync Server 2010 program group, open Lync Server 2010 Management Shell

The final migration step requires running the Import-CsLegacyConfiguration cmdlet. This cmdlet commits the changes from your legacy environment to Lync Server 2010.

Run Import-CsLegacyConfiguration.

That’s all!!! The legacy and Lync setup are merged. This will enable the co-existence of Lync setup and OCS 2007 R1\R2 setup.

Note: You can either have Lync and OCS 2007 R1, or Lync and OCS 2007 R2. Having Lync 2010, OCS 2007 R1 and OCS 2007 R2 setup together is not supported.

 

By

Ram K Ojha

 





 

Latest updates...

Skip Navigation Links
Microsoft News center - UC
Ten Predictions for UC in 2009
Download Center
 
         
    
Copyright, OCSpedia.com. Microsoft, MS-DOS, Windows, Windows 2000, Windows XP, Windows Server 2003, Windows NT, Windows 98, Windows 95 are either registered trademarks or trademarks of Microsoft Corporation in the U.S.A. and other countries. All other names are registered trademarks of their respective companies. Should any right be ran afoul, it is totally unintentional. Send us an e-mail and we will promptly and gladly rectify it. All external sites will open in a new browser. Ocspedia.com does not endorse external sites and is not responsible for their content. For broken links, site problems or any feedback - please send at uc@ocspedia.com