Install and Configuration Lync Server 2010 Std

7/30/2019 Install and Configuration Lync Server 2010 Std

1/21

Step-by-step Microsoft Lync 2010 Consolidated Standard

Server Install Guide

September 15th, 2010 | Tags:Lync Server 2010

As many of you may well know the long awaited public release candidate RTM of Microsoft

Lync 2010 (previously Communications Server 14) is now available fordownload. This

major new release offers a radical difference to the previous architecture and unlike its

predecessors (Communications Server 2007 R1/2 and to a certain degree Live

Communications Server 2005) offers a streamlined and consolidated deployment, great for

smaller scale implementations which are not overly abundant to date.

This guide (update: video version now availablehere) will run through a consolidated

standard edition install (without voice gateway integration, Ill try and come back to this

later), whereby all roles will be deployed on a single virtual machine except monitoring,

archiving and edge rolesyes this is a supported scenario!

So first off Ill run you through some high-level preparation steps/assumptions:

Ive already installed a fresh copy of Windows 2008 R2 Standard on a Hyper-V 2008R2 host, as this is a lab install I have only allocated 2gb of VM RAM (not supported

in production) and a 72gb VM fixed disk (single partition)strangely during theinstall should you choose to install on a secondary partition i.e. D: rather than C: most

of the program files and database(s) end up on C:

Apply all Windows Updates, probably goes without saying, right? Add to your domain (the installation will fail when attempting to deploy on a DC-

see comments below) and login as domain admin or equivalent

Within this guide I have Active Directory Certificate Services deployed for certificategeneration

Now the prerequisites (based upon a Windows 2008 R2 install, 2008 x64 issupported, but unless your organisation has licensing constraints I would strongly

recommend you go down the R2 route)

Add RSAT (only AD DS and AD LDS Tools are required) from within features inServer Manager (used for performing remote schema updates etc.) this will also

prompt you to add the .NET Framework 3.5 feature, you mustaccept this

Add IIS, this is made easier by running this command line:ServerManagerCmd.exe -Install Web-Server Web-Http-Redirect Web-Scripting-

Tools Web-Windows-Auth Web-Client-Auth Web-Asp-Net Web-Log-Libraries Web-

Http-Tracing Web-Basic-Auth
http://imaucblog.com/archive/tag/ls2010/http://imaucblog.com/archive/tag/ls2010/http://imaucblog.com/archive/tag/ls2010/http://technet.microsoft.com/en-gb/evalcenter/ff808407.aspxhttp://technet.microsoft.com/en-gb/evalcenter/ff808407.aspxhttp://technet.microsoft.com/en-gb/evalcenter/ff808407.aspxhttp://imaucblog.com/archive/2011/05/12/microsoft-lync-2010-consolidated-standard-server-video-installation-guide/http://imaucblog.com/archive/2011/05/12/microsoft-lync-2010-consolidated-standard-server-video-installation-guide/http://imaucblog.com/archive/2011/05/12/microsoft-lync-2010-consolidated-standard-server-video-installation-guide/http://imaucblog.com/wp-content/uploads/2010/09/ms-lync-logo.pnghttp://imaucblog.com/archive/2011/05/12/microsoft-lync-2010-consolidated-standard-server-video-installation-guide/http://technet.microsoft.com/en-gb/evalcenter/ff808407.aspxhttp://imaucblog.com/archive/tag/ls2010/


2/21


3/21

A few minutes later the following dialogue will appear. Given my single partition setup, I

choose to accept the default installation directory.

Now you will be presented with a familiar looking wizard that will guide you through the

install process. In my case I have already completed the Active Directory preparation steps

and provided you are logged in with a Domain Admin or equivalent account and your AD is

in good shape this should complete without a hitch (it did in my case!). As per the installation

steps, once this is completed add your chosen admin account to the newly created

CSAdministrator group.
http://imaucblog.com/wp-content/uploads/2010/09/04-lync2010-standard-install.pnghttp://imaucblog.com/wp-content/uploads/2010/09/03-lync2010-standard-install.pnghttp://imaucblog.com/wp-content/uploads/2010/09/04-lync2010-standard-install.pnghttp://imaucblog.com/wp-content/uploads/2010/09/03-lync2010-standard-install.png


4/21

Head back to the main deployment wizard screen and select the option to Prepare first

Standard Edition Server (top right hand option). This will install a copy of SQL 2008

Express, Lync Server core installation files and create an RTC databaselet this take its

course and once complete youll be presented with the following dialogue.

Next install the Topology Builder via the main deployment screen, when this completes you

gain a green tick to signify a successful install. Now the fun stuff, we need to define our

topology by launching the topology builder via the start menu, as explained earlier Lyncoffers a difference in architecture to OCS 2007 and the Central Management Store (CMS) is


5/21

no exception. The CMS is a SQL database where you publish your chosen topology, this

takes away the dependency for Lync to require the AD for configuration purposes and is

required to complete the installation.

Upon launching the Topology Builder we are presented with three options, choose New

Topology (see below).

A dialogue will ask you to choose a save file/location, Im going to accept the default

location and call the file MyTopology.tbxml. Next you are asked for your primary SIP

domain, Ill be using my test AD domain for this Jacobs.local (see below).

You may notice that should you choose to input anything with invalid formatting, youll beasked to correct the problem and a RED square box will identify the bad string. Click next, I


6/21

didnt choose to add any additional SIP domains. Next give your site a name, Ill use MyLab

(see below).

Next site details, mine are below.

And with this completed you are prompted to open the New Front End Wizard, leave this

checked. Here youll need to define the New Front End pool.


7/21

First of all we need to input the pools FQDN, in my case it will be lync.jacobs.local (Lync is

the name of my server). Ill also be opting for the Standard Edition Server Topology (theyll

be no high availability and an additional SQL Express instance, this will host the user and

application store and will be installed automatically upon publishing the policy).

We are now going to select the features required and therefore destined to be collocated, Ill

be installing Conferencing (without Dial-in, Im not going for PSTN voice integration for this

lab setup), Enterprise Voice and Call Admission Control.


8/21

Ill choose to collocate the Mediation Server (it will be redundant for now, given my choice

to hang fire on voice integration).

Given my single server approach and lack of any need to archive, monitor or federate within

my lab, Ill choose to not select any additional server roles within the next screen.


9/21

I dont need to define my SQL store as my Standard Edition will perform the SQL Express

installation automatically.

Now well need to create a file share, create it locally and ensure the account you are

currently using to run the topology builder has read/write access to this folder. Ill call my

folder and share name LyncShare.
http://imaucblog.com/wp-content/uploads/2010/09/15-lync2010-standard-install.pnghttp://imaucblog.com/wp-content/uploads/2010/09/14a-lync2010-standard-install.pnghttp://imaucblog.com/wp-content/uploads/2010/09/15-lync2010-standard-install.pnghttp://imaucblog.com/wp-content/uploads/2010/09/14a-lync2010-standard-install.png


10/21

The next screen will ask you for an external URL, if you have a public facing FQDN for this

server, it goes here. On the next screen (specify PSTN gateways, click finish, if you, like me

are not configuring PSTN integration). You will now be taken back to the main topology

builder screen, where you can view a detailed summary of your chosen setup. Click edit

properties on the top right (below New Central Site) as you will need to add a few final

tweaks.


11/21

First, you need to add an administrative URL, in my casehttps://admin.jacobs.localand

select the front end server to install your CMS on (all things being equal you should have one

option here, your previously specified pool FQDN).

You are all set to publish your topology! To do so select this option from the right hand side

of the main topology builder screen.
https://admin.jacobs.local/https://admin.jacobs.local/https://admin.jacobs.local/http://imaucblog.com/wp-content/uploads/2010/09/17a-lync2010-standard-install.pnghttps://admin.jacobs.local/


12/21

If you followed the guide correctly validation should succeed, click next on the publish

topology wizard.

Accept the front end pool default by clicking next.
http://imaucblog.com/wp-content/uploads/2010/09/18a-lync2010-standard-install.pnghttp://imaucblog.com/wp-content/uploads/2010/09/18-lync2010-standard-install.pnghttp://imaucblog.com/wp-content/uploads/2010/09/18a-lync2010-standard-install.pnghttp://imaucblog.com/wp-content/uploads/2010/09/18-lync2010-standard-install.png


13/21


14/21


15/21

Choose step 2 to install Lync Server Components.

You may be asked to restart, should this occur click finish and manually restart your server.

After logging back in re-execute the deployment wizard and click step 2 from within Install

or Update Lync Server System for the second time, it will automatically resume from where

it left off. With this complete, click finish.


16/21

Step 3 is where certificates are requested and assigned to the server and both internal/external

web services. Click request (see below).

The following dialogue will be presented, choose to send the request immediately to anonline certificate authority (this will submit via AD Certificate Services).


17/21

Select your local CA via the detected server list, click next until you see the option to specify

a friendly name, Ill use Lync.

Choose friendly organisation names, country, state/city and click next. You now need to

configure and accept subject alternate names (SAN)this is where a single certificate can

handle multiple common names or domain names. In my case Ill accept my locally

configured SIP domain. You can add additional names where you have a public facing

FQDN, click finish to execute certificate commands. The assign the requested certificates

(see below).


18/21

Upon completion the following screen will be presented.

Gentlemen start your services, or just click step 4! If you want to verify everything went A

okay there is an option to launch services.msc. Looking good!


19/21

Lets launch the Lync Server Control Panel via the start menu and enable a test user,

provided you installed Silverlight and youre A records resolve in my case,

admin.jacobs.local you should be asked to authenticate with your CSAdministrator admin

details.

Within top actions enable a user for Lync Server. (see below)


20/21

Finally you will need to create a SRV DNS record for your new Lync Server, without this

your Lync client will be unable to locate the server location. To create, access your DNS

manager and right click the Forward Lookup Zone for your SIP FQDN. Then click other new

records and Service Location (SRV), complete using your own server settings as per the

illustration below.


21/21

All things being equal you should now be able to install and login with your Lync client by

using the corresponding sign-in address, give yourself a pat on the back!
http://imaucblog.com/wp-content/uploads/2010/09/35-lync2010-standard-install.png

Date post:	04-Apr-2018
Category:	Documents
Upload:	kemalr2601
View:	235 times
Download:	0 times

Install and Configuration Lync Server 2010 Std

Documents