The server installation itself is quite hands-off and can be automated to a large degree. Unlike most other Microsoft server platform products were installation of the actual server components is one of the very first steps, the Communications Server family has historically been different. If all configuration steps were performed correctly then the wizard should complete without any errors or warnings. The local server FQDN for the Central Management Store location should already be populated in the drop-down menu due to the previous step.
The final process is to publish the changes made to the topology into the Central Management Server database which also updates information in the RTC services container in Active Directory and sets up the folder structure and permissions on the file share.įrom the Action menu select Publish Topology.
fe.) as the location to install the CMS component on.
On the Specify the Web Services URL page the External Base URL will automatically be set to the same FQDN as the internal Front End server (e.g.
Later articles will cover the deployment of some of these additional features.
).Īdd any additional desired SIP domains at this point, but a single SIP domain is sufficient for most deployments as well as this series of articles. For the Primary SIP domain enter the desired domain namespace (e.g.Launch the Skype for Business Server 2015 Topology Builder and then select New Topology.Define Topologyīefore installing any additional server components the Skype for Business topology must be defined. Before performing these steps in this article make sure to successfully complete all of the prerequisite actions covered in Part 1 of this series.