Redeploy Communicator Web Access (2007 R2 Release) for IM and Presence
Topic Last Modified: 2012-10-17
If your organization needs to support browser-based instant messaging (IM) and presence, you need to do the following:
Decommission your legacy deployment, including Communicator Web Access, and then redeploy Office Communicator Web Access (2007 R2 release).
Use Topology Builder to merge and publish your topology.
Test the deployment by starting Communicator Web Access, and then trying to use the internal URL.
To decommission and redeploy Communicator Web Access
When you decommission your Office Communications Server 2007 R2 pools, also decommission Communicator Web Access. For details, see "Removing Servers and Server Roles" at http://go.microsoft.com/fwlink/p/?LinkId=205887.
During decommissioning, it is important that you do not run the Active Directory Domain Services (AD DS) Unprep step to remove Office Communications Server 2007 R2 schema. Active Directory schema for Office Communications Server 2007 R2 is a prerequisite for deploying Office Communicator Web Access (2007 R2 release).
Redeploy Office Communicator Web Access (2007 R2 release). In the Office Communications Server 2007 R2 Create Virtual Server Wizard, on the Select a Pool and Port page, select a Lync Server 2010 pool and the listening port of the pool to support anonymous users. For details about deploying Office Communicator Web Access (2007 R2 release), see http://go.microsoft.com/fwlink/p/?LinkId=218967.
When a user participates in a conference, messages need to be passed between the Communicator Web Access server and the user’s home server. The Lync Server 2010 pool you specify when you create the virtual server acts as a home server for anonymous users, who would otherwise not have a home server for relaying the messages.
To merge and publish the topology
Log on to the computer where Topology Builder is installed as a member of the Domain Admins group and the RTCUniversalServerAdmins group.
From the Standard Edition server or Front End Server, click Start, click All Programs, click Microsoft Lync Server 2010, and then click Lync Server Topology Builder.
Select the option to Download topology from existing deployment, and then click OK.
In Save Topology As, select the Topology Builder file you want to use, and then click Save.
In the Actions pane, click Merge 2007 or 2007 R2 Topology.
In Specify Edge Setup, click Next to bypass Edge setup.
In Specify Internal SIP port setting, select the default setting, and then click Next.
In Summary, click Next to begin merging the topologies.
In Invoke Merge, click Next.
In Import Office Communications Server 2007 or 2007 R2 Topology, you can view the logs. You will see a warning because you did not enable a legacy Edge for federation. Click Finish to complete the wizard.
In the left pane of Topology Builder, you can see the Communicator Web Access server under BackCompatSite in the Trusted application servers node.
From the Actions pane, click Publish Topology, and then click Next.
When the Publishing wizard completes, click Finish.