Installing Server Role Prerequisites
Windows PowerShell can be used to automate
installation of the prerequisite roles and features instead of using
the Windows Server Manager graphical interface. To use PowerShell for
this purpose, use the following steps:
1. Log on to the server with an account that has administrative credentials.
2. Click Start and navigate to All Programs, Accessories, Windows PowerShell.
3. Right-click the Windows PowerShell shortcut and select Run as Administrator.
4. Click Yes when prompted by User Account Control.
5. Run the following command to make the server manager:
Import-Module ServerManager
6. Run the following command to install the Windows features and IIS role services required:
Add-WindowsFeature Telnet-Client,Web-Server,Web-Static-Content,
Web-Default-Doc,Web-Http-Errors,Web-Asp-Net,Web-Net-Ext,Web-ISAPI-Ext,
Web-ISAPI-Filter,Web-Http-Logging,Web-Log-Libraries,Web-Http-Tracing,
Web-Windows-Auth,Web-Client-Auth,Web-Filtering,Web-Stat-Compression,
Web-Dyn-Compression,Web-Mgmt-Console,Web-Scripting-Tools,Web-Dyn-Compression
7. Restart the server when complete.
2. Creating a Director Pool
After the server has been fully
prepared for installation, the topology must be edited and published to
reflect the new Director pool. This involves both editing the existing
topology and then republishing the updated topology so that the
Director role can be installed.
Edit Topology
The next step in deploying a Director is to edit the existing Lync Server topology. To edit the topology follow these steps:
1. Open the Lync Server Topology Builder.
Note
If the Topology Builder is not already
installed on the local computer or another computer in the environment
it can be installed from the Lync Server 2013 media.
2. When prompted to
select the source topology, select Download Topology from Existing
Deployment to retrieve the current topology.
3. Enter a location in which to save the temporary topology file.
4. Expand the Site node where the Director will be deployed.
5. Expand the Lync Server 2013 node.
6. Right-click on the Director pools node and select New Director Pool.
7. Leave Multiple
Computer Pool selected, enter the fully qualified name of the Director
pool in the Pool FQDN field, and click Next. Optionally, select Single
Computer Pool if the Director pool will never have more than one server.
8. Enter the fully qualified name of the Director in the Computer FQDN field, click the Add button, and click Next.
9. Select the Monitoring check box if CDR and QoE metrics should be collected from the Director pool. Click Next.
10. Select a file
store to be used by the pool. Enter a file server FQDN and file share
if one does not exist, and click Next to continue.
11. If the pool will
use DNS load balancing, check the box Override Internal Web Services
Pool FQDN and enter an FQDN for the internal web services.
Note
The internal web services FQDN must be
changed to a name different from the pool FQDN if DNS load balancing
will be used. This is because a hardware load balancer is still
required to manage the HTTPS traffic. If a hardware load balancer will
be used to balance all SIP and HTTPS traffic, or if the pool will
consist of only a single member, then the web services FQDN does not
need to be changed.
12. Confirm or modify the external base URL if necessary and click Next.
13. Select a Monitoring SQL Server store if the pool will collect CDR and QoE metrics. Click Finish to complete the wizard.
14. Review the Web Services URL and file share settings for the Director pool.
Publish Topology
After the Topology has been modified to
include the Director pool, the configuration can be published. This
step publishes the changes to the Central Management Store, and all
existing Lync Server 2013 servers will update their local configuration
stores to match.
1. Ensure that the Lync Server Topology Builder is still open and contains the Director pool recently added.
2. Click the Action menu, select Topology, and then and select Publish.
3. Click Next to begin publishing the topology.
4. Review the publishing wizard log for any errors or warnings and remediate as necessary.
Note
If a DFS share is used for the file store, a
warning might be generated that the file share permissions cannot be
read. This warning can be safely ignored as long as the DFS permissions
were configured properly in advance.
5. When the log indicates a successful update, click Finish to complete the wizard.
