Microsoft Lync Server 2013 is a comprehensive suite that is designed to completely change the way you think about telecommunications.  With Lync, your companies existing phone system can be combined with instant messaging, video chat, and more.  This article provides a basic instruction set to deploy it in a lab environment.

Note: Do not consider this a comprehensive guide to install Lync Server 2013.  It is merely more of a place to get started in deploying your test lab.

Table Of Contents:

  1. Pre-Requisites
    1. Software
    2. Active Directory Permissions
    3. Server Roles
    4. Server Features
  2. Installation
    1. Prepare Active Directory
    2. Prepare First Standard Edition Server
    3. Create A Topology
    4. Install Lync Server
    5. Starting Services
  3. Configuring DNS
  4. Administrate Lync Server 2013
    1. Adding Users (GUI)
    2. Adding Users (CLI)
  5. Logging Into Lync
  6. Known Issues

1. Pre-Requisites:

I. Software

  1. Lync Server 2013 Disc Image
  2. .NET Framework 4.5
  3. Remote Server Administration Tools (RSAT)
  4. Visual C++ 11 Redistribution

II. Active Directory Permissions

  1. Schema Admin
  2. Enterprise Admin (for forest)
  3. Enterprise Admin OR Domain Admin (for domain)

III. Server Roles

  1. Active Directory Certificate Services (If using self-signed certificates, this must be installed somewhere on the domain)
    1. Certification Authority
  2. IIS
    1. Common HTTP Features
      1. Static Content
      2. Default Document
      3. HTTP Errors
    2. Application Development
      1. ASP.NET – (Note: For Windows Server 2012, ASP.NET 3.5 & ASP.NET 4.5 are required.)
      2. .NET Extensibility
      3. Internet Server API (ISAPI) Extensions
      4. ISAPI Filters
    3. Health and Diagnostics
      1. HTTP Logging
      2. Logging Tools
      3. Tracing
    4. Security
      1. Windows Authentication
      2. Client Certificate Mapping Authentication
      3. Request Filtering
    5. Performance
      1. Static Content Compression
      2. Dynamic Content Compression
    6. Management Tools
      1. IIS Management Console
      2. IIS Management Scripting and Tools

IV. Server Features

  1. Windows Identity Foundation / Windows Desktop Experience
  2. Media Foundation
  3. .NET 4.5 Framework
    1. WCF Services
      1. HTTP Activation – (Note: Required for Windows Server 2012.)

2. Installation:

It kind of goes without saying, but if you just installed all those prerequisites then restart the server before continuing.

Setupamd64setup.exe
Load Deployment Services pre-requisite check and select a target to install to

I. Prepare Active Directory

image-238
Click the “Prepare Active Directory” link from the deployment wizard options and follow each step, the option to run each step will become available as the previous step is successfully completed.
image-239
After the Active Directory has been prepared, you will need to add “CSAdministrator” and “RTCUniversalServerAdmins” to the list of groups you are a member of under your Active Directory account. This security group was just created during step 3.

II. Prepare First Standard Edition Server

Each installation of Lync will require a “Central Management Store” which is essentially an SQL database with the configuration, you have the option to host it on another system and reference it later however for the sake of this HOWTO we are going to install it on this server as well.

It is recommended you restart the server before continuing with this step to avoid issues installing SQL Server

The Central Management Store cannot be installed on a domain controller!!

image-240

Click the “Prepare Active Directory” link from the deployment wizard options and follow each step, the option to run each step will become available as the previous step is successfully completed.

After completing this step, a green check mart MAY NOT appear next to the step – you may ignore this.

4
image-241
Install Administrative Tools

III. Create A Topology

image-242

6
image-243
  1. Select “New Topology”
  2. Save to a location for later reference
image-244

Set the primary SIP domain, it is recommend you set it to your top level domain.

For example if you also run an Exchange server somewhere on your network that handles e-mail for your organization you should set your primary SIP domain to match the domain name handled by your exchange server such as “mycompany.com”. By doing this, all the logins for Lync will be the same as each users e-mail address greatly simplifying the user experience.

For the sake of this HOWTO I am going to use “lynctest.local” which is my Active Directory domain since I don’t have a top-level-domain to use.

image-245

If your organization has multiple top level domains, this would be the point where you would define them. Otherwise skip this step.

Continue to follow each step until you get to the last screen.

image-246
Ensure this checkbox is checked before selecting “Finish”
image-247

Set the “Fully Qualified Domain Name” of the server you are installing Lync on, the computer name registered in Active Directory is all you will need to type in here.

Select “Standard Edition Server” to install everything on one system

Select “Enterprise Edition Front Pool” if you have a SQL server within your organization and wish to run all the databases from there.

image-248
For the sake of this HOWTO we are not going to enable “Archiving” or “Monitoring”.
image-249
The scope of this HOWTO doesn’t cover Mediation Servers which are used to manage physical VOIP hardware, so we will leave this box unchecked.
image-250
The scope of this HOWTO doesn’t cover edge pools, so leave this box unchecked.
image-251

This next menu should look something like this, if it does you will not have to make any changes.

If not, you will have to define the SQL Server Store location (likely if you are doing an Enterprise Install).

Similar values should automatically populate themselves in these fields.

Now is the time to create a shared folder somewhere on the server listed under “File Server FQDN” with the name listed under “File share”.

Ensure that the group “Everyone” has all permissions

image-252
This section is asking you what base URL you would like to use for the web based management of Lync. For example, in this configuration your administrative URL will be this:

https://admin.lyncdomain.local/cscp

If you run an Office Web Apps Server this is the part where you would tell Lync where to find it.

The scope of this HOWTO does not cover this, so leave the box unchecked and select “Finish”.

image-253

You are now back in the main menu for the topology builder.

Right click “Trusted application servers” and select “New Trusted Application Pool”.

image-254

You may receive an error if you try to format the FQDN as the field requests (ie: lyncdomain.local), so you may omit the top level domain portion like in my example.

Since we are installing this on a single server, choose the “Single computer pool” radio option.

image-255

Select the “Associate next hop pool” and ensure your server is in the drop down menu like the example.

Select “Finish”.

image-256

Back in the main menu for the topology builder

Select -> Action -> Topology -> Publish…

image-257

Ensure the server you are installing Lync on is selected in the drop down menu.

Click “Advanced”

25
image-258
Select “Use SQL Server instance defaults”, otherwise the next step MAY fail.

IV. Install Lync Server

image-259
Click “Run” on Step 1.
You want to select the first option.
image-260
Continue with step 2.
image-261

This step assumes you are going to use self signed certificates generated on the Active Directory server.

Select “Request”.

image-262
We want to choose the first option.
image-263
Choose your Certificate Authority server, more than likely there will only be on to choose from.
image-264
Unless you know that you need to use alternate credentials, leave this blank and continue.
image-265
Unless you have a reason to need to change the template, leave this blank and continue.
image-266

Specify a name for this certificate that will be easy for you to find later. In reality, it doesn’t matter what you put here but it should be something relevant for posterity sake

Important: Check the “Mark the certificate’s private key as exportable”.

image-267

Continue filling out the details for the ownership information of the certification.

Once you get to this screen, make sure you select any check boxes that are in this menu as they are not by default.

Continue clicking next to generate the certificate.

image-268
Once the certificate generates you will be presented with the option to assign the new certificate to Lync. To do to this, make sure the checkbox in the menu is checked.
38
image-269
Select “OAuthTokenIssuer” and click “Assign”, select the certificate that was just generated and follow the steps to assign it.

V. Starting Services

Continue with step 4 and follow the prompts. This may take a few minutes the first time. Note: Some services may give a warning that they were unable to start. This may be normal and may take a few minutes before they can be started.
image-270
Continue with step 4 and follow the prompts. This may take a few minutes the first time.Note: Some services may give a warning that they were unable to start. This may be normal and may take a few minutes before they can be started.

3. Configuring DNS
image-271
Right click on your domain and select “Other New Records”
image-272
Choose “Service Location (SRV)” and click “Create Record…”
image-273
Service: _sipinternaltls
Protocol: _tcp
Port Number: 5061
Host: [Fully qualified name of your server]
image-274
Right click on your domain and select: “New Host (A or AAAA)…”
image-275
Create the following three “A” records that point to the IP address of your Lync server…

  1. meet
  2. dialin
  3. admin

4. Administrate Lync Server 2013
Navigate your browser to the administration console, the url will look something like this… https://admin.yourlinkserver.local/cscp
image-276
Navigate your browser to the administration console, the url will look something like this…https://admin.yourlyncserver.local/cscp
Select “Topology” from the navigation bar and lookat you’re the computer listed with the pool called “Standard Edition” or “Enterprise Edition” if you went that route. Under “Status” you should see the icon being pointed to, if not select the “Action” drop down and click “Start All Services”. However if everything went correctly the example shown above should be true on your install. If there were warnings when you were trying to start the services earlier in the deployment wizard that still haven’t rectified themselves, consult the “known issues” section at the bottom of the document.
image-277
Select “Topology” from the navigation bar and lookat you’re the computer listed with the pool called “Standard Edition” or “Enterprise Edition” if you went that route.Under “Status” you should see the icon being pointed to, if not select the “Action” drop down and click “Start All Services”. However if everything went correctly the example shown above should be true on your install. If there were warnings when you were trying to start the services earlier in the deployment wizard that still haven’t rectified themselves, consult the “known issues” section at the bottom of the document.

I. Adding Users (GUI)

NOTE: If the user you are attempting to add is also a member of the “Domain Administrators” group, you will not be able to add them in this gui; See the “Administrate Lync Server 2013 – Adding Users (CLI)” section below.

image-278
Select “Enable users”.
image-279
Choose “Add” next to the “Users” box.
image-280

Click “Find”

Select the new user

Click “OK”

image-281

Assign user to the pool

Generate user’s SIP URI (usually in the format of account@domain for ease of use)

Configure any other options you may wish to use

Click “Enable”

Repeat steps for other users

NOTE: You cannot add the “Administrator” user using any method.

II. Adding Users (CLI)

image-282
Open the “Lync Server Management Shell” on the Lync Server AS AND ADMINISTRATOR

Execute the following in the newly opened Lync enabled Powershell console

Enable-CsUser -Identity "Test User" -RegistrarPool "lyncserver.lynctest.local" -SipAddressType SamAccountName -SipDomain “lynctest.local”

This command will create a SIP address for “Test User” that looks like “testuser@lynctest.local”

If you simply want to take everyone in your Active Directory and assign them a SIP in Lync, run a command like this…

Get-CsAdUser -Filter {Enabled -ne $True} | Enable-CsUser -RegistrarPool "lyncserver.lynctest.local" -SipAddressType SamAccountName -SipDomain “lynctest.local”

NOTE: You cannot add the “Administrator” user using any method.

5. Logging Into Lync
image-283

Start the Lync desktop program, and ensure the user is logged into their workstation under their own account.

The Lync client will likely login automatically, however if it doesn’t enter the users sign-in address which is the SIP URI and click “Sign In”.

6. Known Issues
Persistant Chat Server fails to start http://support.microsoft.com/kb/2835433
“Presence Unknown” on users contact card This is due to conflicting contact cards trying to reference the previous SIP address assigned to the

Delete contact cards from the users contact list in Outlook

 

Leave a Reply

Your email address will not be published. Required fields are marked *