leedesmond’s blog

Having completed the definition of your Lync Standard Edition topology with Topology Builder from Step 5a, it is finally time to publish the authored information. We shall conduct this step on the target Lync Server.

1. On the tree view pane, right-click on the top most node “Lync Server 2010″ then pick “Publish Topology”.
2. Review and ascertain that the information on the “Publish the topology” page have been adhered to before hitting Next. In particular, the file share must be readily accessible* otherwise errors will surface later.
3. Notice on the “Select Central Management Server”, the only Front End pool available to host the Central Management Store (CMS) is your Standard Edition Server named lyncse.yourdomain.com in the Lync site (Zurich in our case). Pushing the Advanced button reveals that the radio button “Automatically determine the file location” is selected; this should remain unchanged for a SE deployment. Hit Next.
4. The publishing process begins during which the Lync Setup UI connects to the lyncse.yourdomain.com\rtc, installs the SQL Server 2005 compatibility fix, creates the CMS, database xds, lis (DbFile/.mdf, LogFile/.ldf), sets permissions before finishing off with publishing and enabling the topology and simple URL settings.
5. On the “Publishing wizard complete” page, double-check that a green tick mark as well as “Success” both appear next to each of the steps. Optionally, you can hit “View Logs” to inspect the respective deployment logs.
6. The “Click here to open to-do list” link opens up NextSteps.txt containing to-do instructions. This is essential for Lync Server 2010 to correctly route traffic based on the published topology in your deployment. A sample is depicted here: “     In order for changes to the following simple URLs to take effect, you must update the corresponding DNS records. Depending on how the certificates on your Front End pools and Director pools are configured, you may also need to update the certificates. For details, see the production documentation. https://dialin.yourdomain.com
   https://meet.yourdomain.local
   https://meet.yourdomain.com
   Update Lync Server 2010 with the changes defined in the topology by running local setup on each server in the following list.
   Server FQDN: lyncse.yourdomain.com, Pool FQDN: lyncse.yourdomain.com     “
7. Hit Finish to end.

This concludes the crucial step of publishing the Lync topology into the master CMS. Before the actual setup of any Lync Server components can commence, it is necessary to execute the task “Install Local Configuration Store”. We shall look at this in a subsequent blog post.
* see Part 1: Prerequisites / Readiness

Technorati tags: Lync Server, Communications Server ‘14′

No Comments »