Publishing the Updated Topology to Add Archiving Databases

Topic Last Modified: 2012-10-01

After updating your topology in Topology Builder, you must publish the topology to the Central Management store before you can configure and use Archiving. 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 your updated topology

On a computer that is running Lync Server 2013, or on which the Lync Server administrative tools are installed, log on using an account that is a member of the local Users group (or an account with equivalent user rights).

Note:
You can define a topology by using an account that is a member of the local Users group, but to publish a topology, which is required to add a server to the topology, you must use an account that is a member of the Domain Admins group and the RTCUniversalServerAdmins group, and that has full control permissions (that is, read, write, and modify) on the file share that you are using for the Lync Server 2013 file store (that is, so that Topology Builder can configure the required discretionary access control list (DACLs), or an account with equivalent rights.

Note:

You can define a topology by using an account that is a member of the local Users group, but to publish a topology, which is required to add a server to the topology, you must use an account that is a member of the Domain Admins group and the RTCUniversalServerAdmins group, and that has full control permissions (that is, read, write, and modify) on the file share that you are using for the Lync Server 2013 file store (that is, so that Topology Builder can configure the required discretionary access control list (DACLs), or an account with equivalent rights.

Open the topology you created in the previous section using Topology Builder.
In the console tree, right-click Lync Server 2013, and then click Publish Topology.
On the Publish the topology page, click Next.

On the Create databases page, verify that the database is selected, and then click Next.

Note:
If you do not have the appropriate permissions to create databases, you can cancel the selection of 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 Deployment documentation. Only databases on dedicated SQL Server servers can be installed by using Topology Builder. Databases on SQL Server servers that are collocated with other server components must be installed by running local setup on that computer.

Note:

If you do not have the appropriate permissions to create databases, you can cancel the selection of 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 Deployment documentation.

Only databases on dedicated SQL Server servers can be installed by using Topology Builder. Databases on SQL Server 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.

Important:
After publishing the topology, you must configure options and policies for Archiving before any content can be archived. For details, see Configuring Support for Archiving in the Deployment documentation.