Deploying Lync Server 2010

7/18/2019 Deploying Lync Server 2010

http://slidepdf.com/reader/full/deploying-lync-server-2010 1/37

Deploying Lync Server 2010 (Part 1)

Introduction

You may have notice that Microsoft is grouping all technologies in product families and we can see that with

Forefront, System Center and the well-known family called Unified Communications (UC, in the UC family we havethe following core products !"change Server, Share#oint and $ync Server %&'& (former CS ffice Communications

Server product and this is the topic of this article series)

$ync Server is a great product with several options and * wouldn+t dare to e"plain everything in a single article

however, * would like to go over several features and roles of the product as we go along with the series) he main

idea of the article series is to understand how the pieces fit together in a $ync deployment and how to deploy them)

Using all products together your company will e ale to improve end-users+ productivity and share information in a

whole new level) he integration allows !"change and $ync Server to collaorate on several areas, such as.

/oice0elephony, #resence, Meetings and so forth)

*n this article series we will e creating an initial $ync Server %&'& deployment as simple as a single server can go and

from that point on we will e working on some additional roles to show you how they can e introduced in an e"istent

environment) 1dditionally, you learn how all elements integrate with each other and how they add capailities to the

$ync Server)

You may have read my article series pulished a couple of months ago here at MS!"change)org aout ffice

Communications Server %&&2 3% and !"change Server %&&2, the first article is4eploying !"change Server %&&2 and

ffice Communications Server %&&2 3% (#art ' and ear in mind that $ync Server is the newest version of CS %&&2

3% and for that reason some concepts are similar) 1lso, you may see some similar information in oth articles series

(this one and the CS one such as #lanning ool, 1utomatic logon and etc)))

New features introduced in Lync Server 2010

$ync Server %&'& raised the ar and rought a lot of new features and capailities compared to the previous version

(CS %&&2 3%) *t+s time to list some of the new features efore going any further with planning and deploying phases

of our article series) 5ere are some of the new features of the $ync Server %&'&.

• 6indows Server %&&7 and "89 support only) $ike other products 6indows Server %&&: and :%its are no

longer an option of installation)

• 4eployment improvements. 6e have a new component called Central Management store which is responsile

for all $ync Server %&'& deployment and topology, any changes have to e defined and validated in this

component first and then applied0deployed in your environment)

• Command $ine *nterface. Yes, now we don+t need to run /;scripts or 6M* to get stuff done, we have

#owerShell and tons of cmdlets to manage our $ync Server environment)

• 6e User interface to manage. <ow, we don+t need to install admin tools, we can use a simple and efficient

we administration tool to manage the ma=ority of settings of the product) <ote. some settings still re>uire you

to use #owerShell)

• 6e ased client. he new $ync 6e 1pp is uilt-in with Front-!nd Server and allows users that do not have

the $ync client to =oin meetings)

• 4irector role now is a real role that cannot host any users on it

• 10/ Conferencing Server can e separated from the Front-!nd for performance and scalaility reasons

http://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/deploying-exchange-server-2007-office-communications-server-2007-r2-part1.html






• Mediation Server can e collocated with Front-!nd Server

• elephony improvements that allow $ync Server to replace the e"istent #;? system

*t+s =ust some of the new features and we are going to check them out during this article series) ime to understand the

Front-!nd role and after that fire it up your $1; to start testing the $ync Server %&'&@

Lync Server and the ront!"nd role#$ync Server shares a lot in common with his ig rother !"change Server, you will notice that during this article

series and * can foresee some key areas, such as. 3;1C (3ole ;ased 1ccess Control, $ync Server Control #anel,

1utodiscover to allow clients to logon automatically, and deployment ased in roles)

*f you are an !"change 1dministrator you know that in order to have the asics to run an !"change Server without

any fault tolerance or high availaility you can use a single server (virtual or not and that server must have these three

roles. Client 1ccess Server, 5u ransport and Mailo")

1s a $ync 1dministrator you may ask a similar >uestion, and in the same scenario descried aove the answer would

e one server as well and that server will host a role called Front-!nd) So, y having =ust a single serve we can have

the following capailities in our environment.

• *nternal *nstant Messaging and #resence

• 1pplication Sharing

• 1udio and video calls etween $ync users

• elephony integration (if collocating the Mediation role on the same server

• Conferencing

$et+s stop a little it here and * will e"plain a sutle difference in naming when deploying $ync Server and also go

over capacity planning for the initial $ync Server)

Using $ync Server you have two versions of the product. !nterprise and Standard)

• "nterprise "dition

his version of the product provides high availaility and fault tolerance when deployed properly where we

can have our $ync 4ataases in a SA$ Server or servers (SA$ cluster is recommended ecause with the

!nterprise version you definitely aim at avoiding a single point of failure in your design not sharing resources

with the Front-!nd servers) 6hen you have an !nterprise 4eployment the series of Front-!nd roles is called

Front-!nd #ool)

• Standard "dition

his version is the simple one where the dataase and Front-!nd components are installed on the same server,

in some documentation they refer to it as Standard as well)

<ow that we know the asic difference etween those two roles you can talk aout siBing of the Front-!nd role) *n

order to understand the ig picture when the topic is Front-!nd role, let+s start for the numer ma"imum of users of a

single Front-!nd #ool (since * wrote pool *+m talking aout !nterprise, right is 7&,&&& users) *t+s not a fi"ed limit ut

that is the numer that Microsoft tested and recommends for an environment)

1 Standard edition is ale to support up to D,&&& users and each Front-!nd server of a pool (!nterprise !dition is ale

to support up to '&,&&& users) hese numers are for physical servers) ;ased on these numers a Front-!nd #ool can

have the ma"imum numer of servers to support the numer of users plus one server to e used in hardware

maintenance and updates when necessary) 5ow aout if you have 'D&k users to e enaled on $ync Server *n this

scenario the recommendation is to have two pools to handle that numer of users)



$ync Server is fully supported in a /irtual !nvironment (5yper-/ or /Mware however, the numer of users

supported is less than the physical environment and there are some gotchas when deploying several roles) he thum

rule is %,&&& users per Standard !dition /irtual, while for the !nterprise is D&&& users per virtual server)

*f you are thinking aout /irtualiBation, a few key points may e useful. the operating system must e 6indows

Server %&&7 3% and if all hardware allocated to the /irtual Machines is very similar to the re>uirements of the

physical o"es then you can have the same amount of users)

$nderstanding our initial scenario for this article series#

Since we are going to work a lot in deploying new components to our infrastructure, let me e"plain our initial scenario

and from there we can move forward) You can also deploy the same scenario in your test la in order to follow this

article series)

1ll servers have the prefi" #1 (*+ve receive this >uestion a couple of times, what is #1 6ell, that is the acronym

for my hometown #orto 1legre located etween ;raBil and Uruguay and my internal 1ctive 4irectory FA4< (Full

Aualified 4omain <ame is apatricio%local and my e"ternal domain name registered is andersonpatricio%org)

Server na&e Server 'ole IP Notes

P!D*01 4omain Controller 'E%)'87)'&&)'

P!*01 !nterprise Certificate

1uthority

'E%)'87)'&&)D

P!"+01 !"change Server

C1S05U;0M;?

'E%)'87)'&&)'&

,a-le 1

;ased on that scenario we will e introducing additional servers to support the new $ync Server workload that we will

e adding to our current environment ut efore doing that we are going to plan the entire process using a tool

called Planning ,ool which gives us guidance in deploying our $ync pro=ect and integrates with the 4eployment ool

of the product)

*onclusionIn this initial article we went over the Front-End server role and in our next article we will be

planning our deployment based on the above scenario, and then we continue with the Lync

Server 200 deployment itsel!"

Deploying Lync Server 2010 (Part 2)

Introduction

$ike !"change server the $ync Server %&'& has several roles and some of them can e comined and added in

different stages of the deployment) *n the previous article we have covered the asics for the Front-!nd Server roles

using either Standard or !nterprise versions) $et+s check a >uick review of the remaining roles to give you an idea)

hese will e discussed further during the #lanning ool (ne"t section and then we will e ale to understand each



role and how they interact within the $ync Server architecture) ;ear in mind that we are defining roles here using a

couple of sentencesG they are far more comple" than that) $et+s start with the rief e"planation.

• !dge Server

his is the role that will allow your users to connect to the $ync Server from the *nternet, and share

information with !"ternal companies and pulic *M (such as 6indows $ive, 1$ and Yahoo@)

• 1rchiving

he name is self-e"planatory ut in a few words it will allow a $ync 1dministrator to archive *Mcommunications and meeting content) 6e can archive either internal or e"ternal *M)

• Monitoring

his role enales C43 (Call 4etail 3ecording and Ao! (Auality of !"perience where the $ync

1dministrator is ale to monitor !nterprise /oice and 10/ Conference components, and use the monitoring

data to plan the growth of an organiBation)

• 4irector

;ack in the days, we can do an analogy with !"change Server %&&: Front-!nd Server where this role is the

interface etween e"ternal users coming from the !dge Server (e"ternal to the Front-!nd Servers (*nternal

network) *t improves the performance and security in organiBations with multiple front-end pools and it

cannot host users)

Planning the Lync Server 2010 deploy&ent

You will notice that in order to deploy $ync we have to think twice efore actually running the setup and install the

product on the server)

$ync Server %&'& has a great tool that helps administrator see the ig picture of the environment through the planning

wiBard) his tool is called #lanning ool and it is a wiBard tool where you will e asked several >uestions aout your

organiBation, features that you want to deploy, high availaility, and all that stuff)

Using that scenario you can check the hardware re>uirements, firewall rules, certificates, 4<S, etc) 1lso, the tool can

e"port the design to the opology ;uilder where the planning phase of the product is connected to the deployment

phase and we don+t miss anything etween these two important phases) 1nother nice feature aout the tool is that we

can e"port the server re>uirements to an !"cel File, or e"port the design to a /isio file and all that is =ust one click

away)

1t the time of writing this article the tool was in 3elease Candidate stage and it can e downloaded from here) he

installation process is pretty straight forward and as soon as you open the tool the Get Started page will welcome you

to start the process, =ust click on .et Started utton, as shown in Figure &')

igure 01

he first >uestion will e aout 1udio and /ideo Conferencing, for each >uestion there is a rief description of the

feature, and we don+t have to think too much - Yes or <o) *f you are not sure you can always say yes and go ack

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=bcd64040-40c4-4714-9e68-c649785cc43a

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=bcd64040-40c4-4714-9e68-c649785cc43a



afterwards to avoid using such feature, or you can leave the feature out in the summary page) his fle"iility allows us

to check differences in the final design)

*n the Figure &%, you can see on the top left the uttons that allows us to !"port to !"cel, /isio and opology ;uilder

or #rint the design) hey will e enaled at the end of this wiBard) 1lso, if you are impatient with all the >uestions that

are eing thrown at you, then you should keep an eye at the ottom of the right corner and you will see a ar which

indicates how much left you have to complete the wiBard)

Note.he wiBard is dynamic which means that ased on your answers additional >uestions may e re>uired) 1 good

e"ample is if you say Yes to !nterprise /oice, than !"change Unified Messaging will show up)

igure 02

* am not going in to detail for each >uestion ut the first round of >uestions is to understand which features are

re>uired in your organiBation and at this point the #lanning ool has no information or whatsoever aout your

organiBation)

6hich rings us to the second stage of #lanning ool where we can design sites (Figure &:, asically you =ust need to

type in the Site <ame and how many users you will e hosting there, and all features were selected ased on your

previous answers)

igure 0/

he ne"t >uestion will e aout your S*# domain which is the domain that your users will e using to logon in your

$ync !nvironment, on that page you can add as many as you want) You need to enter the S*# domain in the format

andersonpatricio)org (do not use H)

he #lanning ool will also ask you aout the !"ternal 1ccess for a specific site (in case you have more than one you

can select which site will host the !dge Server(s infrastructure (Figure &9



igure 0

*f you have more sites you can add them here and click inish and then click Draw to see the Iloal design of your

environment as shown in Figure &D) n the right side we have a list of all hardware re>uired for the desired

deployment)

igure 0

*f you doule click on the main site (in our current article is #orto 1legre you will e ale to see all server roles and

their location in the network infrastructure ased on your answers (Figure &8) You can go ack anytime to the Iloalopology clicking on 3iew .lo-al ,opology located in the Actions section of the tool) You can always hover the

mouse over a specific role and a rief description of that role will e displayed in a alloon)



igure 04

1re you not sure aout which hardware and ports aout a specific role for your deployment <ot a prolem, =ust

doule click on any $ync Server role on the diagram and you will have a summary (Figure &2 of the hardware and

port re>uirements)

igure 05

Most of the implementation time of $ync Server0CS spends a lot of time in the !dge Server deployment in previous

versions and the main reason is that sometimes the $ync 1dministrator is not the firewall administrator and there are

several ports to e opened ack and forth) So, in order to make it easier in this version, you can doule click on the

Firewall icon on the main diagram, and here you have all ports re>uired for the 3everse #ro"y and !dge Server in a

ack-to-ack firewall deployment (Figure &7



igure 06

*f we look at the ottom of the diagram page we have : (three tas. Site opology, !dge <etwork 4iagram and !dge

1dmin 3eport) *f you click on "dge Networ7 Diagra& ta (Figure &E you will see all the connections ased on *# to

the !dge and 3everse #ro"y server among 4MJ, !"ternal and *nternal networks) he eauty is that you can doule

click on any item displayed in red and you can edit the information to match your current infrastructure) *f you fill out

all that information you have a really good idea of all names, *#s and so forth that will e re>uired)

igure 08

1fter configuring the <etwork 4iagram to reflect your environment, you can click on "dge d&in 'eport ta and acomplete report containing 1dmin (a summary of all re>uirements, as shown in Figure '&, Certificate, Firewall

settings and 4<S will e availale with all information updated from the entries changed in the previous ta) *sn+t

that cool



igure 10

Finally, as we said earlier you can e"port all that information to several formats, such as. /isio, !"cel, opology

;uilder or =ust print that out)

$sing Planning ,ools and ,opology -uilder fro& a wor7station#

*f you are planning to use the tool on your workstation, and then install oth #lanning ool and opology ;uilder on

6indows 2 and from there you can create the design and use the same process to e"port and import the information

into opology ;uilder (Figure ''

Note9

*f you are going to install opology ;uilder on your 6indows 2, the $ync Server %&'& 4eployment 6iBard will allow

you to do =ust that, we cannot #repare 1ctive 4irectory from the workstation at this point)

igure 11



*onclusion

In this article we went through the process o! de#ning the Lync Server 200 deployment using

the $lanning %ool"

Deploying Lync Server 2010 (Part /)

Introduction

<ow that we ran the #lanning ool and validated how to install opology ;uilder on a workstation we will start the

process of deploying the product, Figure &' shows the process that we will e following in this article series) he

process itself is pretty straight forward ut you may have already noticed it re>uires a lot of planning efore actually

playing with installation and software configuration) (*t has een % articles and we haven+t touched the $ync Server

4eployment 6iBard so far .

igure 01

Starting Lync Server 2010 Deploy&ent

*n this article series we will e deploying the Standard !dition and as we discussed efore as this version has

everything that we need to start running $ync Server internally in a single o") *n this section we will cover the asics

to get the Lync Server 2010 : Deploy&ent ;i<ard up and running)

;efore running the Setup from $ync Server media, we need to install some prere>uisites such as. )<et Framework and

1ctive 4irectory Management ools (it is re>uired ecause we are going also to upgrade Schema, Forest and domain

from the $ync Server plus the additional perating System components re>uired to run $ync Server %&'&)

*n order to save some time let+s use a single cmdlet using #owerShell that will install all re>uirements in a single shot

(Figure &%) ;asically, logged as 1dministrator on your future $ync Server (#1-F! is the server name in our article

series, please open #owerShell and run I&port!=odule Server=anager and then afterwards let+s install the features

using this long cmdlet (*t+s a single and long line.

Add-WindowsFeature NET-Framework-Core, RSAT-ADDS,Web-Server, Web-Scriptin-Too!s, Web-Windows-Aut",

Web-Asp-Net, Web-#o-#ibraries, Web-$ttp-Tracin, Web-Stat-Compression,Web-De%au!t-Doc, Web-&SA'&-E(t, Web-

&SA'&-Fi!ter, Web-$ttp-Errors, Web-$ttp-#oin, Web-Net-E(t, Web-C!ient-Aut", Web-Fi!terin, Web-)mt-Conso!e



igure 02

1fter that let+s restart our server and we are good to install $ync Server %&'&) 6e can run the 1utorun of the media, or

go to the location where you have $ync installation files and go to*Setup*Amd+, and doule click on Setup%e>e% *n

order to start the 4eployment 6iBard one of the prere>uisites is to install /isual CKK %&&7, and that is the first>uestion that you will e asked in case you don+t have it) $et+s click on ?es and the component will e installed

automatically (Figure &:

igure 0/

1fter installing the /isual CKK %&&7, the setup will ask you aout the installation files location (Figure &9 (the default

path is C.L#rogram FilesLMicrosoft $ync Server %&'&, let+s accept the default values and let+s click on Install) 1

$icense 1greement window will pop-up, =ust 1ccept it and click on @ afterwards)

Note. *f you change the *nstallation $ocation, make sure that you rememer it if you are going to do the 1ctive

4irectory Schema e"tension using command line)

igure 0

kay we finally reached the $ync Server %&'& 4eployment 6iBard (Figure &D and from that screen we will e ale to

prepare our 1ctive 4irectory, install the 1dmin tools, install $ync Server and also prepare the Central Management

Store)



igure 0

Preparing ctive Directory#

*n order to prepare the 1ctive 4irectory environment to e ale to run $ync Server we have three preparations to

perform and they can e done either using command line or 4eployment 6iBard.

• Schema

• Forest

• 4omain

he process is straight forward and we will cover oth methods in this section) n the main page (Figure &8 of our

4eployment 6iBard, let+s click on Prepare Sche&a, and all steps re>uired to prepare and to check the results will e

listed in the proper order to e performed)



igure 04

Preparing the Sche&a

1ll preparation processes follow the same process from the 4eployment 6iBard perspective) *n order to avoid a unch

of similar screens we are going over the Schema preparation and the other two preparations (Forest and 4omain

won+t have any screenshots on their sections)

he Schema preparation process in a nutshell will load four $4F files that can e found on the *nstallation Folder to

your Schema) hese are the files that will e loaded into your Schema. !"ternalSchema)ldf which is responsile for

the interoperaility etween $ync Server and !"change ServerG ServerSchema)ldf which is $ync Server %&'& schema

changes re>uiredG ;ackCompatSchema)ldf which provides compatiility with previous versions and

/ersionSchema)ldf which only contains the Schema version update)

1 couple of points that must e checked efore preparing the schema.

• he logged account must have Schema 1dmins credentials, you can check that out running net user

Auserna&eB Cdo&ain the Sc"ema Admins must e listed) *f it is not you need to add the user and logoff and

log ack on again

• he server that holds the Schema Master FSM in 1ctive 4irectory must e running and accessile) o find

out which server holds the Schema Master you can run netdo& uery fs&oand the Schema Master is the first

line of the command output

• he Schema Master must have its 3emote 3egistry service enaled

• Make sure that your 1ctive 4irectory replication is working properly

$et+s click on 'un located on the Step . 'repare Sc"ema area (Figure &2)



igure 05

he first page of the Schema preparation we =ust need to click on Ne>t (Figure &7)

igure 06

*t+s that easy, the second screen (Figure &E has the cmdlet performed to upgrade the schema and the only option that

we have different than Finish the wiBard is to 3iew Log which gives us a nice 5M$ page with detailed information

aout the process)



igure 08

*f you think that the IU* interface is too easy, we can use the hard way using #owerShell, first open the Lync Server

=anage&ent Shell and type in Install!*sDServerSche&a)

Note9

he cmdlet will use the same location that was used during the initial deployment (*nstallation files to retrieve the

$4F information)

*f you want to doule check that the Schema was replicated properly to all your 4omain Controllers, you can use

14S*!dit)msc to check the Schema /ersion (Figure '&) You can open 1dsiedit)msc, right click on 14S* !dit on the

left side, and then click on *onnect to#, then select Sche&a on the Se!ect a we!!-known Namin Conte(t section, andchoose against which 4omain Controller you want to check) Finally, e"pand Schema, then

C<Schema,C<ConfigurationN, and right click on *NE&s!',*!SIP!Sche&a3ersion on the right side and in the

properties you must have the values ''&& for rangeUpper and '9 for range$ower)

igure 10

Preparing the orest

he forest preparation creates the gloal settings and all Universal Iroups used y $ync Server %&'&, also the groups

used y 3;1C (all groups with CS prefi" underneath Users)



o prepare the forest, =ust click on 'un located on the Step /. 'repare Current Forest area, and click <e"t on the

following page and accept the default values on the 0niversa! Group #ocation page (we have the option to define a

different domain to create the Universal Iroups, ut in a single domain scenario like this article series is not

applicale, click Ne>t and inish)

*f you want to do the same process using command-line you can use the following cmdlet.

Enab!e-CsADForest

1s part of the Forest preparation we can see all CSO group created y the process, as shown in Figure '')

igure 11

Note.

*t+s not common ut you can undo a forest preparation, if you have a good reason for that you can use 4isale-

Cs14Forest cmdlet) ;y the way, y default it does not run if you have a domain already prepared in the forest (in the

ne"t section we will cover how to undo a domain preparation as well) #lease, as we stated efore only use such

option if you have a really good reason)

o check the replication, validate if you Iloal Catalogs are replicating properly)

Preparing the Do&ain

he domain preparation will create additional permissions on the domain in three different places. Users, Computers,

domain and root folder container) ;ear in mind that the 4omain must e prepared only if it will host $ync enaled

users and0or $ync Servers)

*f you are going to use 4eployment 6iBard to prepare the domain, click on 'un located on the Step 1. 'repare

Current Domain area, click <e"t on the following page, and click on inish)

*n order to prepare using #owerShell, you can run the following cmdlet.

Enab!e-CsADDomain

Note.

4omain can also e reversed, in order to do that we can use the 4isale-Cs144omain cmdlet however it only works

if there is not a Front-!nd or 1/ Conferencing Server active in the domain)

;rapping up the ctive Directory preparation process#

1fter preparing Schema, Forest and 4omain, we can go ack to the main page and we will see a nice green check

eside the #repare 1ctive 4irectory section which informs us that this section is complete@ (Figure '%) he 1ctive

4irectory preparation is not a daily task and we are proaly going to run only one for each version of the product *n



some cases itPs necessary to rerun some of these tasks ut only do that if you are covered y a Microsoft Q; or a

Microsoft Support recommendation)

igure 12

ne last thing aout $ync Server Management Shell for this section is that we can also use it to check all three

components (Schema, Forest and 4omain using a couple of cmdlets, as shown in Figure ':)

igure 1/

1s soon as we finish preparing the 1ctive 4irectory the option Prepare first Standard "dition Server will eavailale)

*onclusion

In this article we went over the process to prepare the &ctive 'irectory to support Lync Server

200" In the next article we will be starting the deployment o! the product"

Deploying Lync Server 2010 (Part )

Introduction



1t this point we understand the differences etween Standard and !nterprise versions, and so far we prepared our

1ctive 4irectory to support $ync Server %&'&) <ow we need to create the Central Management Store and install, and

configure the opology of our environment) 6e are going to start this tutorial with the main page of the $ync Server

%&'& 4eployment 6iBard (Figure &')

he Central Management Store is a key component of the $ync Server %&'& and the introduction of this new concept

in the $ync architecture provides redundancy for remote locations and a single location for most of the settings) he

CMS (Central Management Store is a SA$ repository that replicates the configuration among other servers in a

master with multiple replicas format) 6here all updates are done at the master copy (the one that we are creating inthis article series and then, replicated to the other servers afterwards) he est practice is to deploy CMS on an

!nterprise pool ecause it has high availaility provided y the SA$ cluster, however, in smaller environments it can

e installed on a Standard !dition) hen the server itself will have two SA$ !"press instances (rtc which hosts the

CMS, and rtclocal which includes a replica of the information)

igure 01

Installing the *entral =anage&ent Store#

6e are going to create the topology in the ne"t section ut efore that we need to create the *entral =anage&entStore% his process has to e performed only if you have Standard !dition and =ust on the first server)

$et+s click on Prepare first Standard "dition server link on the main page, then in the 'repare sin!e Standard

Edition Server page, click Ne>t, as shown in Figure &%)



igure 02

Similar to the 1ctive 4irectory preparation we don+t have a lot of options, the process will start and SA$ %&&7

!"press !dition and its firewall rules e"ceptions will e added to the server (Figure &:) 6e can also check the log

files afterwards, and then click inish)

igure 0/

Defining the ,opology#



$et+s click on Install ,opology Fuilder on the main page of $ync Server %&'& 4eployment 6iBard) he opology

uilder installation is a straightforward process and as part of its installation a couple of tools will e installed, as

shown in Figure &9)

igure 0

*f we look ack to the 4eployment 6iBard we will notice that we knocked down : items already . (Figure &D)

igure 0

<ow, our ne"t step is to create the initial opology using opology ;uilder) $et+s start opening the Lync Server

,opology Fuilder, and on the initial screen, click on New ,opology (Figure &8 and hit @ ) 1 new dialog o" will

show up asking for the file name, select a folder to save our new opology and click on Save)



Note9

he file e"tension will e t"mlG you can always import the settings from $ync #lanning ool ut in this article series

we are going to start from scratch to demonstrate the entire process)

igure 04

n the De%ine t"e primar2 domain page, we can define the primary S*# domain for the organiBation, in our article

series it is going to e andersonpatricio)org, as shown in Figure &2)

igure 05

*f your company has more than one S*# domain to e configured, you can specify it here (Figure &7) Click Ne>t)



igure 06

$ync Server does not use 1ctive 4irectory sites in the opology ;uilder) *n the $ync Server world we can have two

types of sites. Central Site and ;ranch site) !ach Central Site re>uires at least one Front-!nd ServerG a ;ranch site was

designed to have some of these components. *#0#S< Iateway, Mediation Server role and0or Survivale ;ranch

1ppliance (asically it+s an appliance running 6indows Server %&&7 designed for small locations, up to '&&& users)

$et+s move on and define the first site, as shown in Figure &E) he ne"t page will e also related to the site

information, please fill out using the location information and click Ne>t)



igure 08

1fter creating the first site, the opology 6iBard will automatically enale the option to create a new front end wiBard,

so let+s leave the default settings and hit inish)

n the De%ine t"e New Front End 'oo! page, =ust click Ne>t)

n the De%ine t"e Front End 'oo! F3DN page, click on Standard "dition Server and the FA4< will e the FA4<

of our new server, as shown in Figure '&)



igure 10

n the Se!ect Features page (Figure '', *M and presence is enaled y default) 1t this stage we can define which

additional features we want to have installed in our environment) *f you are learning the product, * would recommend

to always go as simple as possile and then start adding features later on) *n our article series we will do that and have

=ust *onferencing enaled, click Ne>t)

Note.

*f you select additional features then the wiBard pages will e ased on your feature selection)



igure 11

n the Se!ect co!!ocated server ro!es page) 5ere is one of the new features of the product, where we have the aility to

collocate different roles on the same server) *n this article we are going to leave default settings and then

click Ne>t (Figure '%

igure 12



n the Associate server ro!es wit" t"is Front End poo! page (this section can e trickyG if we select the provided roles

then a new wiBard is re>uired to create each of our selections afterwards) 6e are starting our article series with =ust a

single server, so let+s leave all of them unchecked and then click Ne>t (Figure ':

igure 1/

n the De%ine t"e S3# store page, since we are not using the !nterprise edition, we don+t have an option to changeany settings related to the dataase) herefore, we =ust need to click on Ne>t)

n the De%ine t"e %i!e s"are page (Figure '9, we can define the information aout the new File Share) his process

does not create the Share itself and in this article series we are going to use the name of LyncShare)



igure 1

n the Speci%2 t"e Web Services 0R# page (Figure 'D, we can define the !"ternal ;ase U3$ that will differentiate

internal and e"ternal domains, in our tutorial we will e using weconf)andersonpatricio)org) he same U3$ will e

used y e"ternal clients when an !dge Server is used in the $ync Server environment)

igure 1



Finally, we are done with the initial topology) * e"panded all options on the left side and our Central Site #orto 1legre

is defined with its Front-!nd, 10/, SA$ Stores, File stores and so forth) ;ear in mind that all this information is =ust in

a t"ml file at this point and we need to pulish it to our Central Management Store (CMS, as shown in Figure '8)

igure 14

Final steps.

• n the $ync Server, let+s create a folder on the C.L drive and that folder will e called $yncShare)

• $et+s share this new folder with the same name and add the !veryone group with Full Control access at Share

level) he main reason is that Users y default has 3ead only at <FS level)

$oad the properties and configure the Simple U3$s, let+s use https.00admin)andersonpatricio)org as administrative

U3$ and make sure that the meet and dialin U3$s are also configured, as shown in Figure '2)



igure 15

*onclusion

In this article we went through the process to install a (anagement Store and how tocon#gure the initial Lync 'eployment using %opology )uilder"

Deploying Lync Server 2010 (Part )

Pu-lishing the ,opology#

his is the final step efore installing $ync Server, and since the planning phase was done properly, this section is

going to e a piece of cake) $et+s open the opology ;uilder and open our current file that we have created earlier on)

hen, let+s click on the Pu-lish ,opology item that is located in the oolo" 1ctions)

n the 'ub!is" t"e topo!o2 page, you will find a welcome page warning you aout some prere>uisites, such asShared folder and simple U3$s definition) $et+s click on Ne>t)

n the Se!ect )anaement Server page, the wiBard gives you the Front !nd information) $et+s select our first Front-

!nd and click on Ne>t (Figure &'



igure 01

n the 'ub!is"in wi4ard comp!ete page, we can check each step performed y the tool during the opology

pulishing (Figure &% and for each step we can see the log files associated with it) he <e"t Steps section has a link

to open a to-do list with the steps left to e done)

igure 02

1fter pulishing the topology we can already see some differences in the environment, the first one is a couple of

folders created in our $yncShare folder (Figure &: and some data eing populated in the 3C Service key inside of

the Configuration partition (Figure &9



igure 0/

igure 0

Deploying Lync Server#

*t+s time to really start installing $ync Server %&'&) $et+s click on Install or Update Lync Server System on the

4eployment 6iBard main page (Figure &D, and the result will e a list of all steps re>uired to deploy the $ync Server

ased on the opology that we have already defined previously in this article series)



igure 0

*n order to configure a local replica of the Configuration Store we have two possile options which are retrieve

directly from the Central Management Store or import from a file) he default option is the first one (Figure &8) 6e

are going to use a file only when the server that we are deploying is out of reach from local $ync Server (e". !dge

Server role) Click on Ne>t)

igure 04

$ike any other final screen in the $ync Server deployment we are going to see all cmdlets perform the install and we

have the option to see the log files) Click on inish)

Step ' is done, now it+s time to install the $ync Server components which are the real $ync Server its on the local

server) he installation is really easy ecause we have done all the hard work in the previous steps) *n order to install

the $ync Server its, let+s click on 3un located on the section Step 5. Setup or Remove #2nc Server Components, and

click on Ne>t and the inish)



Note.

*n some cases the setup installs components that may re>uire a restart and if that happens, te"t in red will e shown

and the ask Status will not show as successful (Figure &2) You may need to restart the server and run the same

procedure again)

igure 05

*t+s that easy to deploy $ync Server and the software its on the server)

Setting up certificates#%

Following the list of items to get done in the $ync Server %&'& 4eployment 6iBard, our ne"t stop is at the certificate

section) Click 'un and the Certificate 6iBard will guide us through the process to re>uest and assign a certificate) *nthe following steps we will e re>uesting and assigning a new certificate using our internal Certificate 1uthority, as

follows.

') he initial page of the Certificate 6iBard page shows the current status of the server, let+s start the 3e>uest

process y clicking on 'euest (Figure &7

igure 06

%) he Certificate 3e>uest 6iBard will start, on the initial page, =ust click Ne>t)



:) n the De!a2ed or &mmediate Re6uests page, we will use our internal Certificate 1uthority and click on Send

the reuest i&&ediately to an online certification authority and click Ne>t)

9) n the C"oose a Certi%ication Aut"orit2 7CA8 page, we can use the C1 detected y the wiBard on the first

option or we can specify one manually) Click Ne>t)

D) n the Certi%ication Aut"orit2 Account page, we can use a different set of credentials to re>uest the certificate)

Since we are running the Certificate 3e>uest wiBard as an administrator we can leave the default settings and

click Ne>t)

8) n the Speci%2 A!ternate Certi%icate Temp!ate page, the $ync Server y default uses the 6e Server certificate

template which is common on all Microsoft Certification 1uthorities, however if you want to choose a

different one you can specify it here) $et+s leave default settings and click Ne>t)

2) n the Name and Securit2 Settins page, we can define a Friendly <ame for the certificate and the it length)

*n this article series we are going to name this certificate as Front-End Anderson'atricio9or and then click

on =ar7 the certificateGs private 7ey as e>porta-le% his way we can move the certificate around in case

we need to) Click Ne>t)

7) n the rganiBation *nformation page, fill out your organiBation information and click Ne>t)

E) n the Ieographical *nformation page, fill out your information and click Ne>t)

'&) n the Sub:ect Name ; Sub:ect A!ternate Names page, we will have all names added automatically to the

re>uest and you may have noticed that all those names were defined during the opology ;uilder phase of this

article series (Figure &E) Click on Ne>t)

igure 08

'') n the S&' Domain settin on Sub:ect A!ternate Names 7SANs8 page (Figure '&, notice that if a deployment

re>uires automatic logon without using Service entries in 4<S or using $ync #hone !dition, then S*# should

e checked) *f you select the option then FA4< sip)Ryour-domain-FA4< will e added to the certificate)



igure 10

'%) n the page Configure 1dditional Su=ect 1lternate <ames, if you are planning any other names for that

specific Front-!nd you can use this page to add additional names to the certificate) Click Ne>t)

':) n the Certificate 3e>uest Summary page, a summary of all options chosen so far will e displayed, click

on Ne>t)

'9) n the E(ecutin Commands page, the results will e displayed and if the ask Status is completed we can

click on Ne>t)

;ecause we are using the internal C1, the Certificate 3e>uest will inform us that the certificate was added

locally (to the machine service account, and we have the option to move forward and start a new wiBard to

assign the certificate that was =ust installed (Figure '', however leave the default settings and click on inish)

igure 11

'D) n the new Certificate 1ssignment 6iBard page, click Ne>t twice and then inish) his wiBard doesn+t allow

us to change any settings) he result will e our new certificate assigned to the new Front-!nd Server, as

shown in Figure '%)



igure 12

Starting Lync Server 2010 services#

6e have already deployed $ync Server %&'& and configured its certificates, now we can start up the services) o do

that, =ust hit the 'un utton located in the section Step . Start Services) *n the initial page of the Start Services

6iBard click Ne>t and the following window will display all services started) *f the ask status. Completed is shown

(Figure ': we are good and we have a $ync Server %&'& up and running@

igure 1/

Using the $ync Server %&'& 4eployment 6iBard, we can click on Step D and open the services)msc) 1ll $ync Services

start with the word $ync and we can check and validate that all services started properly (Figure '9)



igure 1

ne last thing is to click on the last 'un utton of the page and select $se =icrosoft $pdate when I chec7 for

updates (reco&&ended)) his option will allow 6indows Updates to check for $ync updates during the regular

process, as shown in figure 'D)

igure 1

*onclusionFinally, we have Lync Server 200 deployed in our environment but we are not done yet, thereis a lot o! stu* remaining !or this article series" +e will be woring on some client side, usermanagement, server bacup and basic restore, utloo web &pp integration and more""" sostay tuned"

Date post:	29-Feb-2016
Category:	Documents
Upload:	josepedroche
View:	231 times
Download:	0 times

Deploying Lync Server 2010

Documents