Publish the Updated Topology
Topic Last Modified: 2011-01-27
After updating your topology in Topology Builder, you must publish the topology to the Central Management store before you can install and configure the Archiving Server. Read-only copies of the data are replicated to all servers in the topology to keep all servers in sync with topology and other configuration changes.
To publish an updated topology
On a computer that is running Lync Server 2010 or on which the Lync Server administrative tools are installed, log on using an account that is a member of both the Domain Admins group and the RTCUniversalServerAdmins group, and that has full control permissions (that is, read, write, and modify) on the file share to be used for the archiving file store (so that Topology Builder can configure the required DACLs), or an account with equivalent user rights.
Start Topology Builder: Click Start, click All Programs, click Microsoft Lync Server 2010, and then click Lync Server Topology Builder.
In the console tree, right-click Lync Server 2010, and then click Publish Topology.
On the Publish the topology page, click Next.
On the Create other databases page, verify that the database is selected, and then click Next.
If you do not have the appropriate permissions to create databases, you can cancel the selection the database and someone with appropriate permissions can create the database. For details about the required administrator rights and permissions, see Deployment Permissions for SQL Server in the Lync Server 2010 Deployment documentation.
Only databases on dedicated SQL Servers can be installed using Topology Builder. Databases on SQL Servers that are collocated with other server components must be installed by running local setup on that computer.
On the Publishing wizard complete page, verify that the topology was successfully published, and then click Finish.
After publishing the topology, you must install Lync Server 2010 on the computer that you want to use as the Archiving Server, and then configure archiving support to complete your Archiving Server deployment.