Home > Articles > Operating Systems, Server

  • Print
  • + Share This
This chapter is from the book

Installation

This section outlines the steps for installing the Standard and Enterprise Editions of Lync Server. The Standard Edition is generally used for small deployments, whereas the Enterprise Edition offers significant benefits for redundancy and a scalability. The largest difference between the Standard Edition and Enterprise Edition of Lync Server is that the Standard Edition uses SQL Server Express, previously known as MSDE, whereas the Enterprise Edition uses a full version of SQL Server 2005 or 2008.

Lync Server Topology Builder

After preparing Active Directory, the next step is to install the Lync Server Topology Builder. This tool is new and powerful. With a single tool it enables an administrator to design and validate a Lync Server topology, and then publish it to Active Directory. This process greatly simplifies deployments compared to previous versions of Communications Server.

Installation of the Topology Builder comes with some prerequisites and requirements. First, the administrator must be a member of the Domain Admins account in Active Directory. The right to install the Topology Builder can be delegated, but only by a user who is a member of both the Domain Admins and RTCUniversalServerAdmin groups. The other requirements and prerequisites are outlined in the following list:

  • 64-bit edition of the following:
    • Windows Server 2008 R2
    • Windows Server 2008 SP2 or later
    • Windows 7
    • Windows Vista SP2 or later
  • Net Framework 3.5 SP1 or a later service pack.
  • Microsoft Visual C++ 2008 Redistributable x64 9.0.30729.4148. The Deployment Wizard automatically installs this package if it is not already installed.
  • Windows PowerShell 2.0. This is already installed for Windows 7 and Windows Server 2008 R2. For Windows Server 2008, it must be downloaded separately (Microsoft KB968930).

  • Message Queueing (MSMQ) services. Be sure to also install Directory Services integration during the "Features" Installation Wizard.
  • Backward Compatibility Pack for SQL Server 2005 v. 8.05.2312. Although this is not technically required to install Topology Builder, it is required to run the Install-CsDatabase cmdlets. These cmdlets are sometimes called by Topology Builder, depending on the chosen topology, and this should also be considered a prerequisite. This installation package can be found on the installation media in the \Setup\amd64 directory as SQLServer2005_BC.msi.

After the prerequisites are installed, the actual installation of the Topology Builder tool can begin. To install Topology Builder, follow these steps:

  1. Run setup.exe from the installation media. It is located at \setup\amd64\setup.exe.
  2. If the installer prompts you to install the Microsoft Visual C++ 2008 Redistributable, click yes and follow the Installation Wizard.
  3. Click Install Topology Builder in the right column menu of the Deployment Wizard.
  4. After installation is complete, there is a check mark next to the Install Topology Builder link, which is grayed out, as shown in Figure 5.5.
    Figure 5.5

    Figure 5.5 Completed Topology Builder Installation

The Topology Builder tool functions differ depending on your choice of Standard Edition or Enterprise Edition deployment. The process is outlined in each respective section that follows.

Standard Edition Installation

As noted previously, Lync Server Standard Edition is designed for smaller deployments. Standard Edition deployments can have only one server per pool and use SQL Server 2008 Express on the same server as the front end. This results in limited scalability and no redundancy. For this reason, Standard Edition is recommended only for small deployments or where high availability is not a requirement.

The first step for any Standard Edition deployment is to prepare the server as a Central Management Store and prepare the database.

  1. From the main Deployment Wizard screen, in the right pane, click Prepare the first Standard Edition Server.
  2. Click Next at the first screen.
  3. The window displays the actions performed to prepare the server as the first Standard Edition server, including the setup of the Central Management Store. This process takes a few minutes to complete.
  4. When it's done, ensure it completed successfully and then click Finish.

The next step is to define the topology with Topology Builder.

Topology Builder for Standard Edition Deployments

Lync Server uses the published topology to process traffic and maintain overall topology information. To ensure the topology is valid, it is recommended you run Topology Builder before your initial deployment and publish an updated topology after each topological change. This example shows a Standard Edition topology. Remember, if you change the topology later, it should be republished to ensure consistency.

When you first launch Lync Server Topology Builder, you see a partially blank MMC screen, as shown in Figure 5.6. Compare that to the detailed result at the end of this example.

Figure 5.6

Figure 5.6 Topology Builder without a Defined Topology

To begin using Topology Builder, follow the steps that follow:

  1. In the right side of the Action pane, click New.
  2. Define the default SIP domain. In many deployments, this is simply your domain name, as shown in Figure 5.7. In more complex deployments, additional SIP domains might be added by clicking the Add button. When you are done defining SIP domains, click OK.
    Figure 5.7

    Figure 5.7 Define Default SIP Domain

  3. The Next window will ask you to define the first site name as shown in Figure 5.8.
    Figure 5.8

    Figure 5.8 Define Site

  4. The next window prompts the Administrator for the geographic location of the first site. Click Finish to complete the wizard.
  5. This brings up the Define Front End Pool wizard.
  6. Define the pool FQDN and select the radio button for Standard Edition, and then click Next as shown in Figure 5.9.
    Figure 5.9

    Figure 5.9 Define Front End Pool

  7. Choose the appropriate workloads for your deployment, and then click Next. Choose the proper collocation options and click Next. Choose whether other server roles such as Archiving and Monitoring should be associated with this pool and click Next.
  8. Define the database to be used by the pool, as shown in Figure 5.10. For a Standard Edition deployment, the SQL box is grayed out because a local instance of SQL Express is always used. Click Next. Then define the file share to be used by the pool and click Next.
    Figure 5.10

    Figure 5.10 Define SQL Instance and File Share for Front End Pool

  9. When you are ready, click Next.
  10. Specify the Web Services URL and click Next. Specify the PSTN Gateway as shown in Figure 5.11 and click Finish.
    Figure 5.11

    Figure 5.11 Enterprise Voice Topology

This completes the initial topology definition. However, there are additional steps to complete a fully functional topology. The next step is to define easy-to-remember URLs for common Lync Server functions.

  1. From the main Topology Builder page where Lync Server 2010 is highlighted, expand Simple URLs in the main pane, as shown in Figure 5.12, and then click Properties in the right pane.
    Figure 5.12

    Figure 5.12 Expand the Simple URLs

  2. Enter easy-to-remember URLs, as shown in Figure 5.13.
    Figure 5.13

    Figure 5.13 Configured Simple URLs

Port information, such as https://dialin.companyabc.com:443, is invalid. If you choose the first option, the FQDNs need to be included as SANs on your certificates. If you choose the second or third option, note that the following virtual directory names are reserved and cannot be used as part of a simple URL:

  • ABS
  • Conf
  • LocationInformation
  • RequestHandler
  • AutoUpdate
  • cscp
  • OCSPowerShell
  • RGSClients
  • CertProv
  • GetHealth
  • ReachWeb
  • RGSConfig
  • CollabContent
  • GroupExpansion
  • RequestHandlerExt
  • WebTicket

Publish the Topology

The final step is to publish the topology to the Central Management Store. In a Standard Edition deployment, this is the first front end you define. Perform the following steps to publish your topology:

  1. In the Topology Builder tool, in the top-level menu item in the left pane, select Lync Server, as shown in Figure 5.14.
    Figure 5.14

    Figure 5.14 Top Level of Topology Builder

  2. In the right pane, select Publish Topology.
  3. At the opening screen, click Next.
  4. Ensure that correct Central Management Store is selected, and then click Next. This starts the publishing process and overwrites any existing topologies.
  5. The Publish Topology window displays the actions being performed. Ensure it says "Succeeded" at the bottom when it is finished, as shown in Figure 5.15, and then click Finish.
Figure 5.15

Figure 5.15 Successfully Published Topology

Installing the Front End Role

It is important to note that if you jumped to this section before completing the previous steps, you need to go back. Preparing the server for the first Standard Edition server and building a valid topology in the Topology Builder tool are both prerequisites to installing the Front End role. This is a different process from Office Communications Server 2007 and 2007 R2, and it involves more steps.

The following prerequisites are required to install the Standard Edition Front End role:

  • IIS with the following options:
    • Static Content
    • Default Document
    • Directory Browsing
    • HTTP Errors
    • HTTP Redirection
    • ASP.NET
    • .NET Extensibility
    • Internet Server API (ISAPI) Extensions
    • ISAPI Filters
    • HTTP Logging
    • Logging Tools
    • Request Monitor
    • Tracing
    • Basic Authentication
    • Windows Authentication
    • Request Filtering
    • Static Content Compression
    • IIS Management Console
    • IIS Management Scripts and Tools
  • Message Queueing with Directory Service Integration

After you've completed the steps outlined previously, the server is ready to install the Front End role. In the main Lync Server Deployment Wizard screen, click Install or Update Lync Server System from the main pane. Follow the steps that follow to complete the installation process:

  1. Click Run to Install the local configuration store and follow the wizard.
  2. For Step 2: Setup or Remove Lync Server Components, click Run.
  3. The next screen shows the actions being performed, as shown in Figure 5.16. This process takes a few minutes to complete.
    Figure 5.16

    Figure 5.16 Installing the Front End Role

  4. After the task completes, click Finish, and you are brought back to the Deployment Wizard.
  5. Review Step 3: Request, Install or Assign Certificates and click Run. This deployment requires a total of four certificates, so you need to run this step eight times: four times to request certificates and four times to assign them.
  6. Because this is a new deployment, choose Create a new certificate.
  7. At the next screen, choose Default as shown in Figure 5.17, and then click Request.
    Figure 5.17

    Figure 5.17 Request the Default Certificate

  8. Assuming you are using an internal CA, choose Send the request immediately to an online certificate authority and click Next. This is the default option.
  9. Select the appropriate CA for your environment from the drop-down list, choose a friendly name and key length, enable Mark the certificate's private key as exportable as shown in Figure 5.18, and then click Next.
    Figure 5.18

    Figure 5.18 Certificate Request Settings

  10. Enter your Organization Name and Organizational Unit, and then click Next.
  11. Select your country from the drop-down menu, and then enter your state/province and city/locality. Remember that full names must be entered, and abbreviations are not considered valid for certificate requests. When complete, click Next.
  12. The Deployment Wizard automatically adds the SANs required based on the published topology. Unless you have special requirements, select the option to Skip and then click Next.
  13. Review the information to ensure it is correct, and then click Next.
  14. This screen shows the commands executed, as shown in Figure 5.19.
    Figure 5.19

    Figure 5.19 Certificate Request Process

  15. Click Next.
  16. Ensure the Assign this certificate to Lync Server usages box is checked and click Finish. Click Next through the wizard to assign the certificate. Figure 5.20 shows the actions taking place.
    Figure 5.20

    Figure 5.20 Choose the Default Certificate

  17. Ensure the process completes successfully, and then click Finish.
  18. Click Close to close the wizard.
  19. After the certificates have been assigned, there is a check mark by step 3 as shown in Figure 5.21. If there is not a check mark, check your process because you might have skipped a step.
    Figure 5.21

    Figure 5.21 Certificate Process Completed

  20. If the file store for the pool is located on this system, you need to reboot before continuing. After the reboot, restart the Deployment Wizard by launching Setup.exe.
  21. Click Install or Update Lync Server System, and then click Run for Step 4: Start Services.
  22. Click Next.
  23. Ensure all services start, as shown in Figure 5.22.
    Figure 5.22

    Figure 5.22 All Services Started

  24. Click Exit to leave the Deployment Wizard.

The Standard Edition front end is now installed and ready for further configuration using the Lync Server Control Panel.

The following DNS records are required for client autoconfiguration:

  • SRV record of _sipinternaltls._tcp.<sip_Domain> for port 5061 pointing to the FQDN of your front end pool or Director
  • Host (A) record of sipinternal.<sip_Domain> pointing to the IP address assigned to your front end pool or Director
  • Host (A) record of sip.<sip_Domain> pointing to the IP address assigned to your front end pool or Director

Enterprise Edition Installation

Lync Server Enterprise Edition is designed for larger deployments or those that require high availability or redundancy. Enterprise Edition enables you to have multiple front end servers in a pool, and it scales to support larger user counts with an outboard SQL database.

Topology Builder for Enterprise Edition Deployments

Lync Server uses the published topology to process traffic and maintain overall topology information. It is especially important to ensure all information included in the Topology Builder is correct because it sets the initial configuration information for deployed server roles. To ensure the topology is valid, it is recommended you run the Topology Builder before your initial deployment and publish an updated topology after each topological change. This example shows a Enterprise Edition topology. Remember, if you change the topology later, republish it to ensure consistency.

When you first launch Lync Server Topology Builder, you see a partially blank MMC screen, as shown in Figure 5.23. Compare this to the detailed result at the end of this example.

Figure 5.23

Figure 5.23 Topology Builder without a Defined Topology

To begin using Topology Builder, follow these steps:

  1. On the right side of the Action pane, click New.
  2. Define the default SIP domain. In many deployments, this is simply your domain name, as shown in Figure 5.24. In more complex deployments, additional SIP domains might be added by clicking the Add button. When you are done defining SIP domains, click OK.
    Figure 5.24

    Figure 5.24 Define the Default SIP Domain

  3. On the right side of the Action pane, click Define Site. Enter the appropriate information, as shown in Figure 5.25, and then click OK.
    Figure 5.25

    Figure 5.25 Define the Site

  4. On the right side of the Action pane, click Define Front End Pool, and choose the radio button for the Enterprise Edition, and then click Next.
  5. Define the pool FQDN, as shown in Figure 5.26. When you are done, click Next.
    Figure 5.26

    Figure 5.26 Define the Front End Pool

  6. Define the Front End Server FQDNs and click Next.
  7. Choose the appropriate workloads for your deployment, and then click Next. Associate the appropriate Archiving or Monitoring Servers for your pool and click Next.
  8. Define the database and file share to be used by the pool, as shown in Figure 5.27. For an Enterprise deployment, SQL cannot be collocated on one of the front end servers. Also, you need to manually create the share on a server other than the front end before progressing past this step. After the share is created, Lync Server assigns the appropriate permissions. When you are ready, click Next.
    Figure 5.27

    Figure 5.27 Define SQL Instance for Front End Pool

  9. Specify the Web Services URL for the pool and click Next.
  10. Define an A/V Conferencing pool as shown in Figure 5.28.
    Figure 5.28

    Figure 5.28 Conferencing Settings

  11. If you deploy Enterprise Voice, define a PSTN gateway if required, as shown in Figure 5.29. Then click Next.
    Figure 5.29

    Figure 5.29 Specify Voice Gateway

  12. If you plan to allow external access or add any edge services, enable the Associate Edge Pool box and select an Edge Server. When complete, click Finish.

This completes the initial topology definition. However, there are additional steps to complete a fully functional topology.

Configure Simple URLs

The next step is to define easy-to-remember URLs for common Lync Server functions.

  1. From the main Topology Builder page where your site name is highlighted, expand Simple URLs in the main pane, as shown in Figure 5.30, and then click Edit.
    Figure 5.30

    Figure 5.30 Expand the Simple URLs Item

  2. Enter easy-to-remember URLs as shown in Figure 5.31.
    Figure 5.31

    Figure 5.31 Configured Simple URLs

Port information, such as https://dialin.companyabc.com:443 is invalid. If you choose the first option, all the FQDNs need to be included as SANs on your certificates. If you choose the second or third option, note that the following virtual directory names are reserved and cannot be used as part of a simple URL:

  • ABS
  • Conf
  • LocationInformation
  • RequestHandler
  • AutoUpdate
  • cscp
  • OCSPowerShell
  • RGSClients
  • CertProv
  • GetHealth
  • ReachWeb
  • RGSConfig
  • CollabContent
  • GroupExpansion
  • RequestHandlerExt
  • WebTicket

Publish the Topology

The final step is to publish the topology to the Central Management Store. Perform the following steps to publish your topology:

  1. In the Topology Builder Tool, in the top-level menu item in the left pane, select Lync Server, as shown in Figure 5.32.
    Figure 5.32

    Figure 5.32 The Top Level of Topology Builder

  2. Click Publish Topology.
  3. In the opening screen, click Next.
  4. Ensure that correct Central Management Store is selected, and then click Next. This starts the publishing process and overwrites any existing topologies.
  5. Enable the Create Other Databases box. Ensure the account used for installation has permission to perform this function. Click Next.
  6. The Publish Topology window displays the actions being performed as shown in Figure 5.33. Click Finish.
    Figure 5.33

    Figure 5.33 Publishing the Topology

Installing the Front End Role

It is important to note that if you jumped to this section before completing the previous steps, you need to go back. Preparing the server for the first Enterprise Edition server and building a valid topology in the Topology Builder tool are prerequisites to installing the Front End role. This is a different process from Office Communications Server 2007 and 2007 R2, and it involves more steps. Administrators new to Lync Server are advised to review the new features, requirements, and prequisites before beginning the installation process.

The following prerequisites are required to install the Enterprise Edition Front End role:

  • IIS with the following options:
    • Static Content
    • Default Document
    • Directory Browsing
    • HTTP Errors
    • HTTP Redirection
    • ASP.NET
    • .NET Extensibility
    • Internet Server API (ISAPI) Extensions
    • ISAPI Filters
    • HTTP Logging
    • Logging Tools
    • Request Monitor
    • Tracing
    • Basic Authentication
    • Windows Authentication
    • Request Filtering
    • Static Content Compression
    • IIS Management Console
    • IIS Management Scripts and Tools
  • Message Queueing with Directory Service Integration

After you've completed the steps outlined previously, the server is ready to install the Front End role. From the main Lync Server Deployment Wizard screen, click Install or Update Lync Server System from the main pane, and then click Run for Step 1: Install Local Configuration Store. Follow the steps that follow to complete the installation process:

  1. For Step 2: Setup or Remove Lync Server Components, click Run.
  2. As the screen that pops up, click Next.
  3. The next screen shows the actions being performed, as shown in Figure 5.34. This process takes a few minutes to complete.
    Figure 5.34

    Figure 5.34 Installing the Front End Role

  4. After the task completes, click Finish and you are brought back to the Deployment Wizard.
  5. Review Step 3: Request, Install or Assign Certificates and click Run.
  6. At the next screen, choose Default, as shown in Figure 5.35, and then click Request.
    Figure 5.35

    Figure 5.35 Request the Default Certificate

  7. Assuming you are using an internal CA, choose Send the request immediately to an online certificate authority, and then click Next. This is the default option.
  8. Select the appropriate CA for your environment from the drop-down list, choose a friendly name and key length, and enable the Mark the certificate's private key as exportable box as shown in Figure 5.36, and then click Next.
    Figure 5.36

    Figure 5.36 Certificate Request Settings

  9. Enter your organization name and organizational unit, and then click Next.
  10. Select your country from the drop-down menu, and then enter your state/province and city/locality. Remember that full names must be entered, abbreviations are not considered valid for certificate requests. When complete, click Next.
  11. The Deployment Wizard automatically adds the SANs required based on the published topology. Unless you have special requirements, select the option to Skip, and then click Next.
  12. Review the information to ensure it is correct, and then click Next.
  13. This screen shows the commands executed, as shown in Figure 5.37.
    Figure 5.37

    Figure 5.37 Certificate Request Process

  14. Click Next.
  15. Ensure Assign this certificate for Lync Server certificate usages is checked and click Finish.
  16. On the first screen, click Next.
  17. Review the certificate information and then click Next.
  18. Figure 5.38 shows the actions to assign the certificate. When the actions are complete, click Finish.
    Figure 5.38

    Figure 5.38 Assigning the Certificate

  19. After all the certificates have been assigned, a check mark by Step 3 displays, as shown in Figure 5.39. If there is not a check mark, check the process because you likely skipped a step.
    Figure 5.39

    Figure 5.39 Certificate Process Completed

  20. If the file store for the pool is located on this system, you need to reboot before continuing. After the reboot, restart the Deployment Wizard by launching Setup.exe.
  21. Click Install or Update Lync Server System, and then click Run for Step 4: Start Services.
  22. Click Next.
  23. Ensure all services start, as shown in Figure 5.40.
    Figure 5.40

    Figure 5.40 All Services Started

  24. Click Exit to leave the Deployment Wizard.

Configure Front End

The Standard Edition front end is now installed and ready for further configuration using the Lync Server Control Panel, as shown in Figure 5.41. The Lync Server Control Panel is the only GUI available to Lync administrators. It is assumed that most configuration will be done via the Lync Server Management Shell.

Figure 5.41

Figure 5.41 Lync Server Control Panel

For Enterprise Edition deployments, you need to manually add an A record in DNS for the pool name of your front end pool. This is the FQDN that is used when you select Lync Server Control Panel from the Start menu.

The following DNS records are required for client autoconfiguration:

  • SRV record of _sipinternaltls._tcp.<sip_Domain> for port 5061 pointing to the FQDN of your front end pool or Director
  • Host (A) record of sipinternal.<sip_Domain> pointing to the IP address assigned to your front end pool or Director
  • Host (A) record of sip.<sip_Domain> pointing to the IP address assigned to your front end pool or Director
  • + Share This
  • 🔖 Save To Your Account