You are on page 1of 50

Lrror! Unknown document property name.

Þage 1
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0


Þlannlng a Lync Server 2013 ueploymenL on
vlrLual Servers

lebruary 18, 2014
verslon 1.0
!"#$%"#& ()
Iames nornby
Senlor ConsulLanL
[ames.hornby[mlcrosofL.com

ConLrlbuLors
Agus kachman, Cedr|c Depaepe, 8randon 8ern|er, Andrew Sn|derman, Seth McC|ure, Campbe|| Gunn,
kamon Infante

1hanks Lo ChrlsLlan LavlsLa and Lhe MlcrosofL 1echnology CenLer, new ?ork

!"#$ &'()'( *+,-
!"#$%&'"(&$")*

Lrror! Unknown document property name.

MlC8CSCl1 MAkLS nC WA88An1lLS, LxÞ8LSS C8 lMÞLlLu, ln 1PlS uCCuMLn1.
Complylng wlLh all appllcable copyrlghL laws ls Lhe responslblllLy of Lhe user. WlLhouL llmlLlng Lhe rlghLs under copyrlghL, no
parL of Lhls documenL may be reproduced, sLored ln or lnLroduced lnLo a reLrleval sysLem, or LransmlLLed ln any form or by any
means (elecLronlc, mechanlcal, phoLocopylng, recordlng, or oLherwlse), or for any purpose, wlLhouL Lhe express wrlLLen
permlsslon of MlcrosofL CorporaLlon.
MlcrosofL may have paLenLs, paLenL appllcaLlons, Lrademarks, copyrlghLs, or oLher lnLellecLual properLy rlghLs coverlng sub[ecL
maLLer ln Lhls documenL. LxcepL as expressly provlded ln any wrlLLen llcense agreemenL from MlcrosofL, our provlslon of Lhls
documenL does noL glve you any llcense Lo Lhese paLenLs, Lrademarks, copyrlghLs, or oLher lnLellecLual properLy.
1he descrlpLlons of oLher companles' producLs ln Lhls documenL, lf any, are provlded only as a convenlence Lo you. Any such
references should noL be consldered an endorsemenL or supporL by MlcrosofL. MlcrosofL cannoL guaranLee Lhelr accuracy, and
Lhe producLs may change over Llme. Also, Lhe descrlpLlons are lnLended as brlef hlghllghLs Lo ald undersLandlng, raLher Lhan as
Lhorough coverage. lor auLhorlLaLlve descrlpLlons of Lhese producLs, please consulL Lhelr respecLlve manufacLurers.
© 2014 MlcrosofL CorporaLlon. All rlghLs reserved. Any use or dlsLrlbuLlon of Lhese maLerlals wlLhouL express auLhorlsaLlon of
MlcrosofL Corp. ls sLrlcLly prohlblLed.
MlcrosofL and Wlndows are elLher reglsLered Lrademarks or Lrademarks of MlcrosofL CorporaLlon ln Lhe unlLed SLaLes and/or
oLher counLrles.
1he names of acLual companles and producLs menLloned hereln may be Lhe Lrademarks of Lhelr respecLlve owners.
ll
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0




Lrror! Unknown document property name.

Þage 3
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0


AcknowledgmenLs
Name Þos|t|on
ChrlsLlan LavlsLa ulrecLor, MlcrosofL 1echnology CenLer, new ?ork
lablan LabaL M1C Servlce Lnglneer (ALos)
1lm Myers Senlor Servlce Lnglneer
!oel ?oker MCS uS Pyper-v ArchlLecL
Chrls uraglch Senlor ConLenL ueveloper
laclllLles MlcrosofL 1echnology CenLer, new ?ork
Lrror! Unknown document property name.

Þage 4
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0



1able of ConLenLs
Lync Server 2013 vlrLuallzaLlon ...................................................................................................................................... l
LxecuLlve Summary ....................................................................................................................................................... 6
1 lnLroducLlon .......................................................................................................................................................... 7
1.1 WhaL ls vlrLuallzaLlon? ......................................................................................................................................... 7
1.2 Why vlrLuallze? ..................................................................................................................................................... 7
1.3 Server vlrLuallzaLlon ln Lync Server 2013 ............................................................................................................. 8
1.4 Lync Server Þerformance on a vlrLuallzed ÞlaLform ............................................................................................. 9
2 Summary ConslderaLlons for vlrLuallzaLlon of Lync Server 2013 ....................................................................... 10
2.1 Call CuallLy .......................................................................................................................................................... 10
2.2 ConflguraLlon ...................................................................................................................................................... 10
3 Lync ArchlLecLure Cvervlew ................................................................................................................................ 12
3.1 lronL Lnd Servers ............................................................................................................................................... 12
3.2 8ack Lnd Servers ................................................................................................................................................. 13
3.3 ArchlLecLure Changes ln Lync Server 2013 ......................................................................................................... 14
4 Lync Server SLress and Þerformance 1ool (LSS) .................................................................................................. 13
3 key PealLh lndlcaLors - Cood Þass ..................................................................................................................... 16
6 Lync vlrLuallzaLlon Scenarlo SeLup ..................................................................................................................... 18
6.1 Pardware SpeclflcaLlon and vlrLual Machlne ÞlacemenL ................................................................................... 18
7 Lync vlrLuallzaLlon CbservaLlons ........................................................................................................................ 22
7.1 LSS 8amp up ....................................................................................................................................................... 22
7.2 SCL Server Lxpress ............................................................................................................................................. 23
8 Lync Server vlrLuallzaLlon 8ecommendaLlons .................................................................................................... 23
8.1 Pypervlsors ......................................................................................................................................................... 23
8.2 PosL 8equlremenLs ............................................................................................................................................. 28
8.3 CuesL 8equlremenLs ........................................................................................................................................... 30
8.4 CapablllLles SupporL ............................................................................................................................................ 32
8.3 Lync Server CapaclLy Þlannlng ............................................................................................................................ 33
8.6 Plgh AvallablllLy/ulsasLer 8ecovery SLraLegy ...................................................................................................... 33
9 Appendlx A: SLress and Þerformance 1ool ConflguraLlon ueLalls ....................................................................... 34
9.1 user Þrovlslonlng 1ool ........................................................................................................................................ 34
9.2 Common ConflguraLlon ...................................................................................................................................... 36
9.3 lnsLanL Messaglng ............................................................................................................................................... 37
9.4 Audlo Conferenclng ............................................................................................................................................ 39
9.3 AppllcaLlon Sharlng ............................................................................................................................................. 40
9.6 uaLa CollaboraLlon .............................................................................................................................................. 41
9.7 ulsLrlbuLlon LlsL Lxpanslon ................................................................................................................................. 42
9.8 Address 8ook Cuery ........................................................................................................................................... 43
9.9 8esponse Croup Servlce ..................................................................................................................................... 44
9.10 LocaLlon lnformaLlon Servlces ............................................................................................................................ 44
9.11 volÞ ..................................................................................................................................................................... 43
9.12 uC ÞS1n CaLeway ............................................................................................................................................... 46
9.13 Conferenclng ALLendanL ..................................................................................................................................... 46
9.14 Call Þark Servlce .................................................................................................................................................. 46
9.13 MedlaLlon Server and ÞS1n ................................................................................................................................ 47
Lrror! Unknown document property name.

Þage 3
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0



9.16 8each - Ceneral 8each SeLLlngs ......................................................................................................................... 47
9.17 8each AppllcaLlon Sharlng .................................................................................................................................. 48
9.18 8each uaLa CollaboraLlon ................................................................................................................................... 48
9.19 8each lnsLanL Messaglng .................................................................................................................................... 49
9.20 8each volce Conferenclng .................................................................................................................................. 49
9.21 MoblllLy (uCWA) - Ceneral MoblllLy SeLLlngs .................................................................................................... 30
9.22 MoblllLy Þresence and Þ2Þ lnsLanL Messaglng/Audlo ........................................................................................ 30

Lrror! Unknown document property name.

Þage 6
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0



Lxecut|ve Summary
MlcrosofLº Lyncº Server 2013 supporLs vlrLuallzaLlon for all workloads. Powever, because Lync Server ls
a real-Llme communlcaLlons appllcaLlon, lL ls more senslLlve Lo resource consLralnLs Lhan oLher
appllcaLlons. ln Lync Server, an lssue wlLh Lhe avallablllLy of compuLe resources can cause a negaLlve
user experlence lncludlng dropped calls, dropped audlo, choppy audlo, or lnablllLy Lo [oln a conference.
A slmllar resource lssue wlLh a non-real-Llme appllcaLlon would noL be noLlceable Lo Lhe user.
WlLh our LesLlng, we found LhaL a 10,000-user pool spread across Lhree vlrLuallzed lronL Lnd Servers
produced a resource uLlllzaLlon LhaL was wlLhln Lhe crlLlcal key healLh lndlcaLor (kPl) llmlLs. ?our resulLs
may vary based on your hardware and user model, Lhus we recommend you perform capaclLy LesLlng ln
your envlronmenL, before you deploy fully. lor guldance ln your LesLlng, you can use Lhe accompanylng
MlcrosofL paper, Lync Server 2013 SLress 1esLlng Culde.
ln addlLlon Lo performlng sLress LesLlng before you deploy, we recommend you Lake several sLeps ln Lhe
deslgn and conflguraLlon of your hosL server and guesL server Lopology. Lxamples of Lhls are dlsabllng
hyperLhreadlng, uslng a 1:1 raLlo of vlrLual CÞus Lo physlcal CÞus, dlsabllng memory overcommlLmenL,
and several oLhers as deLalled ln Lhls paper.
Lrror! Unknown document property name.

Þage 7
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0



1 Introduct|on
vlrLuallzlng a Lync Server deploymenL can be consldered for all slzes of deploymenL, from small slngle-
slLe deploymenLs Lo large mulLl-slLe enLerprlse lmplemenLaLlons.
1he purpose of Lhls whlLe paper ls Lo provlde you wlLh Lechnlcal guldance for deslgnlng and deploylng a
vlrLuallzed Lync Server 2013 deploymenL, lncludlng Lhe followlng:
• PosL server hardware and sofLware besL pracLlces.
• CuesL server requlremenLs recommendaLlons.
• CuesL server placemenL on Lhe dlfferenL hosL servers.
• 8ecommended pracLlces for deploylng Lync Server, speclflc Lo deploymenL on vlrLual servers.
• Culdellnes for key healLh lndlcaLors Lo waLch when runnlng Lync Server on vlrLual servers,
speclflc Lo each server role.
AddlLlonally, Lhls documenL descrlbes Lhe parameLers used ln Lhe Lync Server SLress 1ool conflguraLlon
Lo maLch Lhe user model used for Lync Server 2013 capaclLy plannlng. lor more lnformaLlon abouL Lhls
user model, see Lync Server 2013 user Models. lor more lnformaLlon abouL capaclLy plannlng for
physlcal servers ln Lync Server 2013, see CapaclLy Þlannlng.
ueLalls abouL Lhe meLhodology used Lo perform Lhe LesLs are descrlbed ln a separaLe whlLe paper, Lync
Server 2013 SLress 1esLlng Culde. ?ou can use Lhls paper for guldance Lo perform sLress LesLlng of your
own deploymenL deslgn before fully lmplemenLlng Lhe deploymenL.
1hls documenL does noL cover cllenL vlrLuallzaLlon scenarlos such as appllcaLlon vlrLuallzaLlon or Lync
cllenL deploymenL wlLh vlrLual ueskLop lnfrasLrucLure (vul).
1hls documenL does noL provlde prescrlpLlve guldance abouL Lhe lnsLallaLlon and conflguraLlon of Lync
Server 2013 and supporLlng sofLware componenLs. lor guldance abouL Lhe lnsLallaLlon and conflguraLlon
of Lync Server 2013, see Lync Server producL documenLaLlon.

1.1 What |s V|rtua||zat|on?
vlrLuallzaLlon, ln lLs slmplesL form, provldes a layer of absLracLlon beLween Lhe hardware and operaLlng
sysLem. Server vlrLuallzaLlon allows mulLlple operaLlng sysLems (or "vlrLual machlnes") and Lhelr
appllcable workloads Lo share Lhe resources of a slngle server. 1he maln beneflLs of vlrLuallzaLlon are
lmproved resource uLlllzaLlon (Lyplcally reduclng Lhe number of physlcal servers needed) and Lhe ablllLy
Lo relocaLe vlrLual machlnes Lo dlfferenL hosLs.
1.2 Why V|rtua||ze?
ln Loday's compeLlLlve envlronmenL, organlzaLlons wanL Lo:
Lrror! Unknown document property name.

Þage 8
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0



• 8educe lnfrasLrucLure cosLs whlle accuraLely forecasLlng operaLlonal expendlLure.
• CreaLe more value by provldlng fasLer buL lower-cosL servlces.
• lncrease operaLlonal efflclency.
Server vlrLuallzaLlon capablllLles may help companles achleve Lhese goals by:
8educlng Lhe 1oLal CosL of Cwnershlp
• Leveraglng exlsLlng resources wlLh server consolldaLlon.
• lncreaslng space uLlllzaLlon wlLh fewer physlcal servers.
• uecreaslng hardware malnLenance and Lralnlng cosLs.
• Þrovldlng an absLracLlon of operaLlng sysLem and workloads from acLual physlcal hardware.
• 8educlng Llme Lo deploy.
• Mlnlmlzlng servlce dlsrupLlon and lncreaslng servlce levels.
• Þrovldlng capaclLy on demand ln response Lo changlng buslness needs.
• Speedlng up server deploymenL by dupllcaLlng a sLandard vlrLual server.
lncreaslng operaLlonal efflclency
• lmprovlng buslness conLlnulLy wlLh hlgh avallablllLy of hardware and appllcaLlons.
• lncreaslng operaLlonal flexlblllLy wlLh dynamlc resource managemenL and server
provlslonlng.
• lmprovlng Lhe server Lo admlnlsLraLor raLlo.
As always, one slze does noL flL all and whlle vlrLuallzaLlon makes sense for some companles and
workloads, lL wlll noL make sense for oLhers.
1.3 Server V|rtua||zat|on |n Lync Server 2013
MlcrosofL has made slgnlflcanL lnvesLmenLs ln vlrLuallzaLlon supporL for Lync Server whlle provldlng a
fully dlsLrlbuLed Lopology. 1o vlrLuallze Lync Server, you can use Pyper-vº Wlndows Serverº 2012 82,
Pyper-vº Wlndows Serverº 2012, or a Lhlrd-parLy vlrLuallzaLlon soluLlon LhaL has passed Server
vlrLuallzaLlon valldaLlon Þrogram (SvvÞ) LesLlng. lor more deLalls, see Lhe Wlndows Server
vlrLuallzaLlon valldaLlon Þrogram. Cn a vlrLual server, you can run all Lync Server workloads.
• lnsLanL messaglng (lM)
• lM conferenclng
• Þresence
• LnLerprlse volce (ÞS1n)
• Audlo conferenclng
• vldeo conferenclng
• Web conferenclng
• AppllcaLlon sharlng
• 8emoLe access, federaLlon (Ldge Server)
• 8esponse Croup Servlce
Lrror! Unknown document property name.

Þage 9
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0



• ÞerslsLenL chaL
• 8ack-end daLabase
• Archlvlng/monlLorlng daLabases

1.4 Lync Server Þerformance on a V|rtua||zed Þ|atform
vlrLuallzlng Lync can reduce Lhe physlcal server counL by comblnlng hlgh-resource servers wlLh low-
resource servers on a hlgh-powered hosL server. 1hls can be an effecLlve sLraLegy Lo reduclng physlcal
server fooLprlnL ln Lhe daLa cenLer.
vlrLuallzaLlon ls meanL Lo leverage a shared lnfrasLrucLure across many appllcaLlons. Lach of Lhe four
fundamenLal compuLe resources-CÞu, Memory, neLwork, and ulsk-are absLracLed or shared ln a
vlrLuallzed envlronmenL. Lync Server, as a real-Llme medla appllcaLlon, performs dlfferenLly Lhan oLher
appllcaLlons and requlres speclal conslderaLlon.
lor example, ln a web appllcaLlon, resource consLralnLs may resulL ln a web page loadlng a llLLle blL
slower-Lyplcally lmpercepLlble Lo a user. WlLh Lync Server, slmllar resource consLralnLs may resulL ln
dropped audlo or choppy vldeo-Lhls ls a ma[or lmpacL and can resulL ln a negaLlve user experlence.
Lync Server ls deslgned Lo consume Lhe full capablllLles of a physlcal server and wlll perform poorly lf Lhe
requlred compuLe resources are noL avallable when needed. 1o help Lhe vlrLuallzaLlon of Lync Server
2013 Lo be successful for your organlzaLlon, follow Lhe guldellnes provlded ln Lhls whlLe paper.
An addlLlonal beneflL of vlrLuallzaLlon ls ensurlng conslsLency ln slmllar servers ln your organlzaLlon by
uslng vlrLuallzaLlon LemplaLes. ConslsLency drlves down operaLlonal cosL and complexlLy, and lmproves
servlce levels.
Lrror! Unknown document property name.

Þage 10
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0



2 Summary Cons|derat|ons for V|rtua||zat|on of Lync Server
2013
1o provlde a greaL communlcaLlons experlence ln Lync Server 2013 and enable a successful deploymenL,
vlrLuallzlng Lync requlres a focused deslgn and LesL efforL Lo valldaLe Lhe vlrLuallzaLlon plaLform can
meeL requlred capaclLy, quallLy, and operaLlonal LargeLs.
ln addlLlon Lo Laklng lnLo accounL Lhe oLher recommendaLlons llsLed ln Lhls paper, you should revlew Lhe
followlng summary conslderaLlons Lo make and valldaLe Lhe declslon Lo vlrLuallze.
2.1 Ca|| Çua||ty
Call quallLy ls a key componenL of Lync Server performance on boLh physlcal servers and vlrLual servers.
Call quallLy depends on ready CÞu resources for medla Lranscodlng as well as a hlgh-performlng neLwork
Lo supporL medla sLreams. AdopLlon of vldeo wlll slgnlflcanLly lncrease demands on boLh CÞu and
neLwork. 1he hypervlsor lnherenLly lncurs a CÞu penalLy as overhead, and vlrLual CÞus ofLen have very
dlfferenL performance characLerlsLlcs from physlcal ones. ln a non-real-Llme appllcaLlon llke a web
servlce, Lhese lmpacLs may be unnoLlceable buL Lhey can be very apparenL ln Lync. A splke of daLabase
acLlvlLy can lmpacL neLwork performance, conLrlbuLlng Lo laLency, packeL drops, or [lLLer-all of whlch
wlll degrade audlo quallLy and Lhe user experlence. SLress LesLlng before you deploy Lo make sure your
planned hardware and vlrLual machlnes are slzed approprlaLely can help mlnlmlze bad user experlences.
2.2 Conf|gurat|on
ueslgnlng and operaLlng an enLerprlse-grade Lync Server lnfrasLrucLure requlres lnvolvemenL from
several Leams. Addlng vlrLuallzaLlon provldes a new dlmenslon of complexlLy and rellance on anoLher
Leam for supporL.
vlrLuallzaLlon also lnLroduces a new layer of conflguraLlon and opLlmlzaLlon Lechnlques for each guesL
LhaL musL be deLermlned and LesLed for Lync Server. Many vlrLuallzaLlon Lechnlques LhaL can lead Lo
consolldaLlon and opLlmlzaLlon for oLher appllcaLlons cannoL be used wlLh Lync Server. Shared resource
Lechnlques, lncludlng processor oversubscrlpLlon, memory overcommlLmenL, and l/C vlrLuallzaLlon,
cannoL be used because of Lhelr negaLlve lmpacL on Lync scale and call quallLy.
vlrLual machlne porLablllLy-Lhe capablllLy Lo move a vlrLual machlne guesL server from one physlcal
hosL Lo anoLher-breaks Lhe lnherenL avallablllLy funcLlonallLy ln Lync Server pools. Movlng a guesL
server whlle operaLlng ls noL supporLed ln Lync Server 2013. Lync Server 2013 has a rlch seL of
appllcaLlon-speclflc fallover Lechnlques, lncludlng daLa repllcaLlon wlLhln a pool and beLween pools.
vlrLual machlne-based fallover Lechnlques break Lhese appllcaLlon-speclflc fallover capablllLles.
Lrror! Unknown document property name.

Þage 11
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0



1he LesLlng we compleLed revealed some speclflc conflguraLlon lLems LhaL we recommend when you run
Lync Server on a vlrLuallzaLlon plaLform:
Þrocessor
• ?ou should dlsable hyperLhreadlng on all hosLs.
• uo noL use processor oversubscrlpLlon, malnLaln a 1:1 raLlo of vlrLual CÞu Lo physlcal CÞu.
• Make sure your hosL servers supporL nesLed page Lables (nÞ1) and exLended page Lables (LÞ1).
• ulsable non-unlform memory access (nuMA) spannlng on Lhe hypervlsor, as Lhls can reduce
guesL performance.

Memory
• uo noL conflgure dynamlc memory or memory overcommlLmenL on hosL servers.

neLwork
• use vlrLual Machlne Cueue (vMC) Lo opLlmlze synLheLlc nlC performance.
• use physlcal nlC segregaLlon for hosL versus guesL communlcaLlons.
• Slngle-rooL l/C vlrLuallzaLlon (S8-lCv) ls recommended. 1he speclflc conflguraLlon you should
use depends on Lhe hosL chlpseL and neLwork adapLer/drlver.

SLorage
• use flxed or pass-Lhrough dlsks raLher Lhan dynamlc dlsks.

Pypervlsor
• vlrLual machlne porLablllLy or fallover Lechnlques such as llve mlgraLlon are noL supporLed.

Lrror! Unknown document property name.

Þage 12
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0



3 Lync Arch|tecture Cverv|ew
Lach server runnlng Lync Server runs one or more server roles. A server role ls a deflned seL of Lync
Server funcLlonallLles provlded by LhaL server. Cnly Lhose server roles requlred for Lhe funcLlonallLy of
Lhe sysLem are requlred.
1hls secLlon brlefly dlscusses Lwo prlmary roles ln Lync Server, Lhe lronL Lnd Server and 8ack Lnd Server.
lL also dlscusses some changes Lo Lhe Lync Server archlLecLure ln Lync Server 2013 LhaL affecL how Lhese
roles relaLe Lo each oLher.
3.1 Iront Lnd Servers
ln Lync Server 2013, Lhe lronL Lnd Server ls Lhe core server role, and runs many baslc Lync Server
funcLlons. 1he lronL Lnd Server, along wlLh Lhe 8ack Lnd Server, are Lhe only server roles requlred Lo be
ln any Lync Server 2013 LnLerprlse LdlLlon deploymenL.
A lronL Lnd pool ls a seL of lronL Lnd Servers, conflgured ldenLlcally, LhaL work LogeLher Lo provlde
servlces for a common group of users. A pool of mulLlple servers runnlng Lhe same role provldes
scalablllLy and fallover capablllLy.
1he lronL Lnd Server provldes Lhe followlng servlces:
• user auLhenLlcaLlon and reglsLraLlon.
• Þresence lnformaLlon and conLacL card exchange.
• Address book servlces and dlsLrlbuLlon llsL expanslon.
• lnsLanL messaglng funcLlonallLy, lncludlng mulLlparLy lnsLanL messaglng conferences.
• Web conferenclng, ÞS1n dlal-ln conferenclng, and audlo/vldeo (A/v) conferenclng.
• Web componenLs Lo supporL web-based Lasks such as web scheduler and [oln launcher.
• AppllcaLlon hosLlng for boLh appllcaLlons lncluded wlLh Lync Server (for example, conferenclng
aLLendanL and response group appllcaLlon) and Lhlrd-parLy appllcaLlons.
• MonlLorlng Lo collecL usage lnformaLlon ln Lhe form of call deLall records and call error records.
1hls lnformaLlon provldes meLrlcs abouL Lhe quallLy of Lhe medla (audlo and vldeo) Lraverslng
Lhe neLwork for boLh enLerprlse volce calls and audlo/vldeo conferences.
• Archlvlng Lo archlve lnsLanL messaglng communlcaLlons and meeLlng conLenL for compllance
reasons.
lronL Lnd pools are also Lhe prlmary sLore for user and conference daLa. lnformaLlon abouL each user ls
repllcaLed among Lhe lronL Lnd Servers ln Lhe pool. 1hls ls performed by uslng Lhe Lync SLorage Servlce
as deplcLed ln Lhe followlng flgure.
Lrror! Unknown document property name.

Þage 13
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0




llgure 1 - Lync Server 2013 ArchlLecLure


new for Lync Server 2013, an organlzaLlon can palr lronL Lnd pools ln Lwo geographlcally dlspersed slLes
for dlsasLer recovery purposes. Lach slLe conLalns a lronL Lnd pool LhaL ls palred wlLh a correspondlng
lronL Lnd pool ln Lhe oLher slLe. 8oLh slLes are acLlve, and Lhe Lync Server 8ackup Servlce provldes real-
Llme daLa repllcaLlon Lo keep Lhe pools synchronlzed.
lf Lhe pool ln one slLe falls, an admlnlsLraLor can fallover Lhe users from Lhe falled pool Lo Lhe pool ln Lhe
oLher slLe, whlch Lhen provldes servlces Lo all Lhe users. lor capaclLy plannlng, each pool should be
deslgned Lo handle Lhe workloads of all users ln boLh pools ln Lhe evenL of a dlsasLer.
3.2 8ack Lnd Servers
8ack Lnd Servers are daLabase servers runnlng MlcrosofL SCL Server LhaL provlde Lhe daLabase servlces
for Lhe lronL Lnd pool. 1he 8ack Lnd Servers serve as backup sLores for Lhe pool's user and conference
daLa, and are Lhe prlmary sLores for oLher daLabases such as Lhe response group daLabase. 1here can be
a slngle 8ack Lnd Server, buL a hlghly avallable soluLlon LhaL uses SCL Server mlrrorlng ls recommended
for fallover, and an SCL wlLness server auLomaLes Lhls process. 8ack Lnd Servers do noL run any Lync
Server sofLware.
AddlLlonally, one lronL Lnd pool ln Lhe deploymenL also hosLs Lhe CenLral ManagemenL Server daLabase
on lLs 8ack Lnd Servers, whlch manages and deploys baslc conflguraLlon daLa Lo all servers runnlng Lync
Server 2013.

Lrror! Unknown document property name.

Þage 14
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0



3.3 Arch|tecture Changes |n Lync Server 2013
ln Lync Server 2013 LnLerprlse LdlLlon, Lhe archlLecLure of Lhe lronL Lnd pools has been changed when
compared Lo Lync Server 2010.
ln Lhe Lync Server 2013 archlLecLure, Lhe back-end daLabase ls no longer Lhe real-Llme daLa sLore ln Lhe
Lync pool. MosL Lync daLa (lncludlng presence lnformaLlon, permlsslons, and user conLacLs) now are
sLored prlmarlly on Lhe lronL Lnd Servers Lo lmprove Lhe performance and scalablllLy of Lhe overall
archlLecLure, and Lo ellmlnaLe Lhe slngle polnL of fallure of Lhe 8ack Lnd Server compared Lo Lync Server
2010.
now LransacLlons for users regardlng presence, conLacLs, and conferenclng lnformaLlon are handled on
Lhe lronL Lnd Server wlLh Lhe 8ack Lnd Server provldlng Lhe overall perslsLenL blob sLorage of Lhls daLa.
1hls means LhaL Lhe lronL Lnd Servers have more of Lhe resource and compuLe burden Lhan Lhey dld ln
prevlous verslons of Lync Server.
1he A/v Conferenclng Server role ls also now parL of Lhe lronL Lnd Server role. ln addlLlon Lo Lhls maln
archlLecLural change, Lhere are no longer separaLe MonlLorlng Server or Archlvlng Server roles, wlLh
Lhese now runnlng as servlces on Lhe lronL Lnd Server.
A flnal change ln uslng Lhe lndusLry sLandard P264 codec for vldeo requlres addlLlonal compuLaLlonal
resources on Lhe lronL Lnd Server when runnlng vldeo conferenclng.
Lrror! Unknown document property name.

Þage 13
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0



4 Lync Server Stress and Þerformance 1oo| (LSS)
Lync Server 2013 SLress and Þerformance 1ool (LSS) ls a LoolseL LhaL enables organlzaLlons plannlng Lo
deploy Lync Server 2013 Lo perform sLress LesLlng of a LargeL deploymenL lnfrasLrucLure based on Lhelr
speclflc usage paLLern. 1hls lnfrasLrucLure lncludes server, sLorage, and neLwork.
LSS can slmulaLe lndlvldual workloads, such as lnsLanL messaglng and presence, appllcaLlon sharlng,
audlo conferenclng, and so on. 1hls enables you Lo assess Lhe capaclLy plannlng requlremenLs of a Lync
Server 2013 deploymenL Lo handle Lhe enLlre supporLed workloads rlghL from Lhe beglnnlng, or Lo
gradually scale up and/or scale ouL Lhe Lync Server 2013 deploymenL as a new workload ls lnLroduced-
such as ln Lhe case of sLarLlng wlLh lM and presence and conferenclng, and laLer addlng Lhe LnLerprlse
volce workload.
A sLress LesLlng exerclse uslng LSS musL be performed agalnsL Lhe same LargeL deploymenL
lnfrasLrucLure lnLended Lo be used for producLlon lmplemenLaLlon, and musL be performed ln an
lsolaLed lab envlronmenL.
8ecause LSS only provldes Lhe Lools Lo provlslon users and slmulaLe user loads, your sLress LesLlng musL
also lnvolve a proper deslgn and deploymenL of Lync Server 2013 wlLh lLs supporLlng lnfrasLrucLure (such
as AcLlve ulrecLory, CerLlflcaLe Servlces, Cfflce Web Apps Server, load balancer, and reverse proxy).
A sLress LesLlng exerclse uslng Lync Server 2013 LSS ls Lyplcally performed rlghL afLer Lhe compleLlon of
Lhe Lechnlcal deslgn and before Laklng Lhe deslgn lnLo plloL. 1he deslgn, wlLh lLs supporLlng
lnfrasLrucLure, should be deployed ln Lhe lab envlronmenL for funcLlonal/nonfuncLlonal LesLlng flrsL, and
Lhen leveraged Lo perform sLress LesLlng for Lhe purpose of capaclLy plannlng valldaLlon.
ueLalls abouL Lhe meLhodology used Lo perform sLress LesLs uslng LSS ls descrlbed ln a separaLe whlLe
paper, Lhe Lync Server 2013 SLress 1esLlng Culde.
lor deLalls abouL Lhe parameLers we used for LSS Lo maLch Lhe Lync 2013 user Models, see Appendlx A:
SLress and Þerformance 1ool ConflguraLlon ueLalls.
Lrror! Unknown document property name.

Þage 16
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0



S key nea|th Ind|cators - Good Þass
Many key healLh lndlcaLors (kPls) have been ldenLlfled for Lync Server 2013. Powever, Lo ease Lhe efforL
lnvolved ln checklng all Lhe lndlcaLors for each LesL run conducLed by uslng LSS, we have deflned Lhe 10
mosL slgnlflcanL for a good pass and llsLed Lhem ln Lhe followlng Lable. lf you're LesLlng reveals no lssues
ln meeLlng Lhese 10 prlmary kPls, you could furLher analyze Lhe full kPl seL.
1he full kPl seL for Lync Server 2013 ls lncluded ln Lhe neLwork Þlannlng, MonlLorlng, and
1roubleshooLlng wlLh Lync Server documenLaLlon download.
Table 1. Key health indicators – good pass
Counter Descr|pt|on nea|thy range
\Þrocessor lnformaLlon(*)\ ° Þrocessor
1lme
CÞu uLlllzaLlon <80° (hlghesL core)
\Memory\Avallable MbyLes ulsplays Lhe amounL of physlcal
memory, ln byLes, avallable Lo processes
runnlng on Lhe compuLer.
>20° LoLal sysLem memory
\Þhyslcalulsk\Avg. ulsk Sec/8ead 8epresenLs Lhe average Llme, ln
mllllseconds, of each dlsk read laLency.
<10 ms Creen
<10-23 ms ?ellow
>23 ms 8ed
\Þhyslcalulsk\Avg. ulsk sec/WrlLe 8epresenLs Lhe average Llme, ln
mllllseconds, of dlsk read laLency.
<10 ms Creen
<10-23 ms ?ellow
>23 ms 8ed
LS:usrv - u8SLore\usrv - Cueue LaLency
(msec)
Cueue laLency ls Lhe amounL of Llme (ln
mllllseconds) LhaL lL Lakes for a requesL
Lo leave Lhe lronL Lnd Server's queue
Loward Lhe back-end daLabase.
lf Lhls value by lLself ls hlgh, you may be
encounLerlng a neLwork problem
beLween Lhe lronL Lnd Server and Lhe
SCL Server.
lf Lhls value ls hlgh and sproc laLency ls
hlgh, lL ls mosL commonly a boLLleneck
wlLh Lhe 8ack Lnd Server.
<100ms susLalned
LS:uSrv - u8SLore\usrv - Sproc LaLency
(msec)
A sproc laLency ls Lhe amounL of Llme (ln
mllllseconds) LhaL lL Lakes for Lhe SCL
Server daLabase Lo process Lhe requesL.
1hls performance value ls collecLed from
Lhe Llme Lhe requesL leaves Lhe lronL
Lnd Server queue unLll LhaL requesL
reLurns.
lf Lhls value by lLself ls hlgh, lL ls llkely a
boLLleneck wlLh Lhe 8ack Lnd Server.
<100ms susLalned
Lrror! Unknown document property name.

Þage 17
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0



Counter Descr|pt|on nea|thy range
\MSSCL$lnS1AnCL:8uffer
Manager\Þage llfe expecLancy
Pow many seconds SCL Server expecLs a
daLa page Lo sLay ln cache.
>300
\MSSCL$lnS1AnCL:Memory
Manager\Memory CranLs Þendlng(k8)
1oLal number of processes per second
walLlng for a workspace memory granL.
<80° of physlcal memory
\ASÞ.nL1 Apps v2.0.30727(*)\8equesLs
8e[ecLed
<80°

\ASÞ.nL1 Apps v.4.0.30319(*)\8equesLs
8e[ecLed
<80°



Lrror! Unknown document property name.

Þage 18
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0



6 Lync V|rtua||zat|on Scenar|o Setup
We conducLed our Lync Server 2013 LesLlng wlLh a purpose-bullL lab envlronmenL LhaL LesLed Lync
Server 2013 LnLerprlse LdlLlon wlLh Lhree lronL Lnd Servers agalnsL Lhe deflned user model. lor
lnformaLlon abouL Lhe Lync 2013 user models, see Lhe CapaclLy Þlannlng uslng Lhe user Models and
Lync 2013 user Models arLlcles.
6.1 nardware Spec|f|cat|on and V|rtua| Mach|ne Þ|acement
1he lab lncluded elghL PÞuL360 CeneraLlon 8 chassls wlLh four lnLel L3-4630 processors and 128 C8 of
memory. 1he followlng Lable descrlbes Lhe hardware componenLs and loglcal conflguraLlons for Lhe
LesLlng.
1able 1 - PosL Pardware SpeclflcaLlon
Çuant|ty Manufacture part number Descr|pt|on
8 686792-821 PÞ uL360 Cen8 C1C Server
8 686843-L21 PÞ L3-4630 uL360 Cen8 llC klL
24 686843-821 PÞ L3-4630 uL360 Cen8 klL
64 672631-821 PÞ 16C8 28x4 ÞC3-128008-11 klL
32 632611-821 PÞ 300C8 6C SAS 13k 2.3ln SC Ln1 Puu
8 631667-821 PÞ SmarL Array Þ222/312Ml8 l8WC CLrlr
8 631674-821 PÞ SmarL Array Þ421/2Cl8 l8WC ConLroller
8 A!764A PÞ 82C 8Cb uual ÞorL ÞCl-e lC P8A
8 684208-821 PÞ 1CbL 4-porL 331lL8 AdapLer llC klL
8 631679-821 PÞ 1C8 l8WC for Þ-Serles SmarL Array
8 A!940A PÞ SLorageWorks u2600 ulsk Lnclosure
96 316828-821 PÞ 600C8 6C SAS 13k 3.3ln uÞ Ln1 Puu

Lrror! Unknown document property name.

Þage 19
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0




llgure 2 - Loglcal PosL ConflguraLlon


1able 3 - PosL SLorage ConflguraLlon
Storage |ocat|on Interna| Lxterna|
ulsks ulsks 0-3 ulsks 0-3 ulsks 4-7 ulsks 8-11
Array Array 0 (8Alu 10) Array 1 (8Alu 10) Array 2 (8Alu 10) Array 3 (8Alu 10)
CapaclLy 600 C8 1.2 18 1.2 18 1.2 18
lCÞS (100° 8ead °) 700 lCÞS 700 lCÞS 700 lCÞS 700 lCÞS
lCÞS (100° WrlLe °) 330 lCÞS 330 lCÞS 330 lCÞS 330 lCÞS


Lrror! Unknown document property name.

Þage 20
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0




Lach vlrLual server had 12 cores and 32 C8 of memory allocaLed followlng Lhe recommendaLlons for
physlcal servers as deLalled ln Lhe Server Pardware ÞlaLforms arLlcle.
We creaLed Lhe followlng Lopology for our LesLlng.

llgure 1 - Lync Server 1opology


CuesL vlrLual machlnes were spread across hosLs ln order Lo LesL performance. CollocaLlon of speclflc
server roles was noL LesLed. lnsLead, we used a loglcal separaLlon of roles. lor example, we dld noL place
mulLlple lronL Lnd Servers LogeLher on Lhe same hosL. (noLe LhaL placlng servers of a llke role on Lhe
same hosL server ls supporLed. Powever, keeplng vlrLual servers ln Lhe same pool on dlfferenL hosL
servers lmproves reslllence ln Lhe case of a hardware fallure.)
Lrror! Unknown document property name.

Þage 21
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0




1able 4 - vlrLual Machlne ÞlacemenL
Log|ca|
proc
nost01 nost02 nost03 nost04 nost0S nost06 nost07 nost08
00-03 lL01 lL02 lL03 8L01 8L02 Ldge01 Ldge02 S103
04-07
08-11 uC01 uC02 S106
12-13
16-19 CWAS01 8L03
(WlLness)
CWAS02 S107
20-23
24-27 S101 S102 S103 S104 S108
28-31 8eserved 8eserved 8eserved 8eserved 8eserved 8eserved 8eserved 8eserved



Lrror! Unknown document property name.

Þage 22
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0



7 Lync V|rtua||zat|on Cbservat|ons
We ran mulLlple LesL runs. WlLh Lhe hardware we used, we found an opLlmal soluLlon of a 10,000-user
pool wlLh Lhree lronL Lnd Servers. 1hls soluLlon produced a hlgh-resource uLlllzaLlon LhaL was wlLhln Lhe
crlLlcal kPl llmlLs. ?our resulLs may vary based on your hardware and user model, Lhus we recommend
you do some LesLlng ln your envlronmenL before you deploy fully.
1hls secLlon lncludes oLher observaLlons we made durlng LesLlng.
7.1 LSS kamp Up
1hroughouL Lhe LesLlng process, we observed a ramp-up perlod of abouL 30 mlnuLes when uslng LSS.
1he ramp-up perlod durlng your LesLlng may be longer or shorLer, dependlng on how many LSS
conflguraLlon flles you are loadlng. ?ou musL lgnore Lhe LesL resulLs from Lhls perlod and noL accounL for
Lhem ln your LesL analysls. uurlng Lhls ramp-up Llme, LSS conflguraLlon flles are loaded, users are logged
ln, and Lync compleLes some background Lasks.
1he ramp-up Llme can be seen ln Lhe followlng flgure. lL shows Lhe amounL of processor (CÞu) Llme used
over a perlod of Llme, and Lhe splkes of CÞu uLlllzaLlon from slmulaLed user workloads.

llgure 4: Þerformance MonlLor - ÞercenL of Þrocessor 1lme - 1esL 8un - 10,000 users

Lrror! Unknown document property name.

Þage 23
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0



7.2 SÇL Server Lxpress
lour processors remalned ln hlgh uLlllzaLlon over Llme. 1hose processors are assoclaLed wlLh Lhe
81CLCCAL SCL Server Lxpress LdlLlon lnsLance. SCL Server Lxpress LdlLlon can use only four loglcal
processors (see CompuLe CapaclLy LlmlLs by LdlLlon of SCL Server for more lnformaLlon). When Lhese
processors approach >90 percenL uLlllzaLlon, lL lndlcaLes LhaL Lhe LnLerprlse LdlLlon pool wlLh Lhree
lronL Lnd Servers ls already aL full capaclLy from a SCL Server Lxpress vlewpolnL. 1o accommodaLe more
users, you wlll need Lo add lronL Lnd Servers.
ln flgure 3 we can see Lhe asslgned cores for Lhe 81CLCCAL SCL lnsLance as lnsLance 0.0, 0.1, 0.2, and
0.3. We can see LhaL Lhese four processors are hlghly uLlllzed durlng LesLlng.
When analyslng resulLs from Lhe LSS, CÞu uLlllzaLlon across all cores allocaLed ln Lhe guesL should be
lnspecLed and noL Lhe LoLal average.
lL ls lmporLanL Lo noLe LhaL Lync Server ls opLlmlzed Lo uLlllze Lhe four cores asslgned for SCL Server
Lxpress compuLe. We also Lrled an unsupporLed scenarlo uslng SCL Server LnLerprlse LdlLlon. 1hls was
found Lo noL lmprove Lhe performance of a lronL Lnd Server overall, ln facL, compuLe was spread across
CÞu Llme, causlng hlgher uLlllzaLlon across all CÞu.
Whlle under load and above 90 percenL CÞu uLlllzaLlon, we lnvesLlgaLed addlLlonal kPl values speclflcally
relaLlng Lo SCL Server Lxpress.
llgure 3 shows Lhe same loadlng characLerlsLlcs as we expecL durlng ramp up. 8uL as Lhe LSS lnsLances
sLarL Lo slmulaLe workloads, we see a more normallsed paLLern where splkes slgnlfy user load on Lhe
sysLem.
Cueue laLency ls Lhe amounL of Llme (ln mllllseconds) LhaL lL Lakes for a requesL Lo leave Lhe lronL Lnd
Server's queue Loward Lhe back-end daLabase and sproc laLency ls Lhe amounL of Llme (ln mllllseconds)
LhaL lL Lakes for Lhe MlcrosofLº SCL Serverº daLa managemenL sofLware daLabase Lo process Lhe
requesL. 1hls performance value ls collecLed from Lhe Llme Lhe requesL leaves Lhe lronL Lnd Server
queue unLll LhaL Lhe requesL reLurns. 1ogeLher Lhese Lwo values show us LhaL Lhe CÞu uLlllzaLlon ls noL
affecLlng performance of Lhe underlylng SCL daLabases, and Lhus poLenLlally Lhe envlronmenL ls sLlll
capable of handllng Lhe user loads.
Lrror! Unknown document property name.

Þage 24
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0




llgure 3: Þerformance MonlLor - LSusrv - Cueue and sproc laLencles - 1esL 8un - 10,000 users



Lrror! Unknown document property name.

Þage 23
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0



8 Lync Server V|rtua||zat|on kecommendat|ons
1hls secLlon conLalns recommendaLlons we found from Lhe vlrLuallzaLlon LesLlng of Lync Server 2013.
8.1 nyperv|sors
We LesLed Lync Server 2013 based on Lhe same requlremenLs as physlcal whlle also allowlng for
hypervlsor overhead for vlrLual envlronmenLs. Lync Server 2013 can be deployed on Wlndows Server
2012 Pyper-v and laLer Lechnology, or any Lhlrd-parLy hypervlsor LhaL has been valldaLed under Lhe
SvvÞ.
8.1.1 Va||dated nyperv|sors
• Wlndows Serverº 2012 Pyper-vº
• Pyper-vº Wlndows Server 2012
8.1.2 Cther nyperv|sors
• Wlndows Server 2012 82 Pyper-v
• Pyper-v Wlndows Server 2012 82
Wlndows 2008 82 hypervlsors are supporLed, buL noL recommended because guesLs are llmlLed Lo four
cores, maklng Lhls unsulLable for all Lync Server roles.
• Pyper-vº ln Wlndows Serverº 2008 82
• Wlndows Pyper-v Server 2008 82
Wlndows 2008 82-based hypervlsors should have Lhe hoLflx descrlbed ln MlcrosofL knowledge 8ase
arLlcle 981836 deployed. lor more lnformaLlon, see MlcrosofL knowledge 8ase arLlcle 981836, neLwork
connecLlon ls losL on a Wlndows Server 2003-based Pyper-v vM.
8.1.3 Unsupported nyperv|sors
AlLhough Pyper-v was avallable as a role ln Wlndows Server 2008, LhaL release ls noL supporLed. A
number of enhancemenLs LhaL are crlLlcal for runnlng vlrLuallzed Lync Server medla workloads were
lmplemenLed wlLh Wlndows Server 2008 82 Lo address neLwork packeL loss.
8.1.4 nyperv|sor Cverhead
Pypervlsors requlre an amounL of overhead (Lyplcally 6 percenL Lo 10 percenL) above and beyond whaL
Lhe vlrLual guesL requlres. 1hls overhead can lnvolve boLh CÞu and memory. ln Lhe case of advanced
workloads whlch are able Lo fully use Lhe hardware resources, vlrLuallzlng Lhe workload can resulL ln a
neL lncrease of physlcal servers due Lo Lhe overhead of Lhe vlrLuallzaLlon layer.
Lrror! Unknown document property name.

Þage 26
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0



Pypervlsor overhead musL be Laken lnLo accounL on Lop of Lhe physlcal server requlremenLs for Lync
Server vlrLuallzaLlon and conLlnuous monlLorlng ls essenLlal Lo malnLaln Lhe correcL performance for
normal Lync Server operaLlons on a vlrLual envlronmenL ln regards Lo Lhe CÞu and memory of Lhe vlrLual
machlnes.
8.1.S V|rtua| Mach|ne Image 1emp|ates
?ou cannoL run Sysprep Lo creaLe machlne lmage LemplaLes afLer Lync Server 2013 ls lnsLalled. We
recommend you use cusLom operaLlng sysLem LemplaLes wlLh appllcable operaLlng sysLem prerequlslLes
lnsLalled dependlng on Lhe LargeLed workload. lor example, you could use an operaLlng sysLem
LemplaLe for lronL Lnd Servers conLalnlng lnLerneL lnformaLlon Servlces (llS) and Wlndows Medla
lormaL 8unLlme. lor more lnformaLlon, see Lhe Sysprep secLlon of Lhe Lync Server 2013 8esource klL
1ools uocumenLaLlon.
AfLer conflgurlng Lhe guesL operaLlng sysLems uslng Lhese LemplaLes, you can Lhen deploy Lync Server
on each vlrLual server.
8.1.6 L|ve M|grat|on and Çu|ck M|grat|on
Llve mlgraLlon ls a process where runnlng workloads can be moved from a source server Lo a desLlnaLlon
server wlLhouL lmpacLlng Lhe avallablllLy of runnlng buslness appllcaLlons or crlLlcal daLa. Whlle
mlgraLlng llve vlrLual machlnes, Lhere are Lwo ma[or concerns: ouLage of appllcaLlons or daLa and
prevenLlon of daLa loss.
Lync Server 2013 does noL supporL llve mlgraLlon and/or qulck mlgraLlon capablllLles of a hosL
hypervlsor soluLlon. Þlannlng for hlgh avallablllLy requlres Lhe use of naLlve Lync Server 2013
capablllLles, whlch exceeds LhaL of hypervlsor based soluLlons. 1here are Lechnlcal challenges wlLh
redlrecLlng real-Llme medla Lrafflc wlLhouL an lnLerrupLlon LhaL can be deLecLed by users.
AlLhough you can move a vlrLual machlne runnlng Lync Server beLween hosLs, lL musL be shuL down
prlor Lo dolng so. 1hls ouLage wlll be observed by a porLlon of Lhe cllenL base hosLed on Lhe server and
any acLlve conferences wlll be ended.
8.1.7 Dynam|c Memory
MlcrosofL does noL supporL uynamlc Memory for vlrLual machlnes LhaL run any of Lhe Lync Server 2013
roles. lf Lync Server 2013 does noL have full conLrol of Lhe memory allocaLed Lo Lhe physlcal or vlrLual
machlnes on whlch lL ls runnlng, degraded sysLem performance and a poor cllenL experlence can resulL.
CLher hypervlsors have dynamlc memory capablllLles. Memory musL noL be overprovlsloned aL Lhe
hypervlsor layer as currenL hypervlsors do noL have Lhe capablllLy Lo provlde dedlcaLed resource
segmenLaLlon/resource lsolaLlon for all four physlcal componenLs: processor, memory, sLorage l/C, and
neLwork l/C. As a resulL a guesL on a hypervlsor plaLform may consume resources LhaL would Lhen be
unavallable or llmlL avallablllLy for oLher guesLs on Lhe same physlcal hosL, and degrade Lhe user
experlence as a resulL.
Lrror! Unknown document property name.

Þage 27
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0



8.1.8 V|rtua| D|sks
llxed-slze vlrLual dlsks use Lhe full amounL of space speclfled durlng vlrLual hard dlsk creaLlon. llxed-slze
.vhdx dellvers near naLlve-Lo-physlcal performance and sllghLly hlgher performance Lhan dynamlcally
expandlng .vhdx flles.
uynamlcally expandlng dlsks only consume physlcal space based on Lhelr acLual conLenLs. 1haL ls Lhe
acLual physlcal slze of Lhe dlsk flle may only be a few megabyLe aL creaLlon, buL as flles are added Lo Lhe
guesL operaLlng sysLem, Lhe slze of Lhe dlsk flle on Lhe physlcal sLorage grows accordlngly. 1he guesL
operaLlng sysLem always sees Lhe maxlmum slze LhaL Lhe admlnlsLraLor chose upon creaLlon.
uslng dlfferenclng dlsks and dynamlcally expandlng dlsks ls noL supporLed ln a vlrLuallzed Lync Server
2013 envlronmenL. 1he Lhln-provlsloned naLure of Lhe dynamlcally expandlng dlsk flles means LhaL Lhe
underlylng sLorage can become overcommlLLed. As each dynamlcally expandlng dlsk flle grows ln slze
Loward lLs conflgured maxlmum, Lhe underlylng sLorage could run ouL of space lf noL carefully
monlLored. lnsLead, flxed-slze vlrLual dlsks can be used Lo allocaLe a sLaLlc amounL of space on Lhe
underlylng physlcal sLorage upfronL, Lhereby ensurlng LhaL Lhere wlll be enough sLorage space.
1o reduce dlsk conLenLlon, do noL sLore sysLem flles on hard drlves dedlcaLed Lo sLorlng vlrLual
machlnes.
uo noL use checkpolnLs for Lhe vlrLual machlnes ln a Lync Server 2013 producLlon envlronmenL. When
you creaLe a checkpolnL, Pyper-v creaLes a new secondary drlve for Lhe vlrLual machlnes. WrlLe
operaLlons occur on Lhe new drlve, and read operaLlons occur on boLh drlves, resulLlng ln reduced
performance.
8e aware of underlylng dlsk read/wrlLe conLenLlon beLween dlfferenL vlrLual machlnes and Lhelr vlrLual
hard dlsks.
8.1.9 V|rtua| IDL and SCSI
vlrLual machlnes can be conflgured Lo use vlrLual luL devlce conLrollers or vlrLual SCSl devlce conLrollers
Lo connecL vlrLual sLorage. When a vlrLual machlne sLarLs, Lhe vlrLual luL conLroller ls used wlLh a booL
.vhdx flle because Lhe vlrLual SCSl dlsk requlres a drlver Lo be presenL durlng sLarLup. 1hls drlver ls only
presenL when booLed lnLo Lhe operaLlng sysLem. luL ls llmlLed Lo Lhree connecLed dlsks. (Cne porL ls
reLalned for Lhe uvu drlve, whlch ls requlred for updaLlng Lhe lnLegraLlon componenLs.) vlrLual SCSl, on
Lhe oLher hand, can have 64 connecLed dlsks per conLroller and 4 conLrollers per vlrLual machlne, glvlng
a LoLal of 236 vlrLual SCSl dlsks per vlrLual machlne. vlrLual SCSl also supporLs hoL-add/removal of dlsks,
whereas vlrLual luL dlsks do noL.
1he vlrLual luL conLroller musL be used for sLarLlng Lhe vlrLual machlne, however, all oLher drlves should
be aLLached Lo Lhe vlrLual SCSl conLroller. 1hls ensures opLlmal performance, as well as Lhe greaLesL
flexlblllLy. Lach vlrLual machlne has a slngle vlrLual SCSl conLroller by defaulL, buL Lhree more can be
added whlle Lhe vlrLual machlne ls offllne.
Lrror! Unknown document property name.

Þage 28
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0



vlrLuallzed Lync Server 2013 deploymenLs can also use llbre Channel sLorage soluLlons.
8.1.10 Guest Storage
ln addlLlon Lo presenLlng vlrLual dlsk flles Lo Lync Server 2013 vlrLual machlnes, admlnlsLraLors can
choose Lo connecL Lhe guesL operaLlng sysLem of a Lync vlrLual machlne dlrecLly Lo exlsLlng sLorage
lnvesLmenLs. Pyper-v offers a number of dlfferenL ways Lo expose a drlve Lo a vlrLual machlne guesL
operaLlng sysLem. 1he approprlaLe meLhod depends on a number of facLors, such as lf Lhe sLorage ls
locally aLLached, or on a SAn, and Lhere are no speclflc preferences from a Lync Server vlsuallzaLlon
perspecLlve. 1wo meLhods provlded ln Pyper-v are ln-guesL lnLerneL SCSl (lSCSl) and vlrLual llbre
Channel.
Common besL pracLlces:
• 1he vlrLual machlne's guesL operaLlng sysLem booL drlve musL be mapped as a vlrLual luL drlve.
SCL Server workloads use a vlrLual luL drlve for Lhe operaLlng sysLem, and SCL Server blnarles,
and vlrLual SCSl conLrollers Lo map SCL Server log and SCL Server daLa drlves.
• lSCSl LargeLs LhaL are dlrecLly exposed Lo Lhe guesL server are Lyplcally lmplemenLed lf guesL
servers need Lo be moved beLween hosLs. Pere, Lhe guesL operaLlng sysLem drlve on Lhe SAn
and Lhe guesL-speclflc daLa drlves wlll auLomaLlcally be accesslble Lo Lhe guesL afLer Lhe move. lf
guesL servers are moved, lL ls requlred LhaL guesL sLorage ls locaLed on a shared sLorage
aLLached uslng elLher lSCSl or vlrLual llbre Channel.
8.1.11 kesource Cver-A||ocat|on
Lync Server 2013 guesLs should noL be provlsloned on hypervlsor hosLs whlch are conflgured for CÞu
over allocaLlon. lor example, lf Lhe physlcal hosL has 24 cores, no more Lhan 24 cores LoLal should be
allocaLed Lo all of Lhe guesLs on Lhe sysLem.
Lync Server lncludes several real-Llme workloads (such as audlo/vldeo and conferenclng) LhaL requlre
real-Llme access Lo componenLs such as processor, memory, neLwork, and sLorage. lf Lhese componenLs
are shared among oLher guesLs and Lync does noL have access Lo Lhese as requlred, Lhe resulL can be a
negaLlve user experlence lncludlng dropped calls, dropped audlo, choppy audlo, lnablllLy Lo [oln a
conference, paused vldeo, and oLher user-noLlceable resulLs. 1hese can be dlfflculL Lo LroubleshooL, as
an analysls of Lhe physlcal servers and vlrLual guesLs aL a laLer polnL ln Llme may show all ls flne, wlLh Lhe
lssues surfaclng only durlng perlods of hlgh uLlllzaLlon from oLher guesLs.
8.2 nost kequ|rements
1hls secLlon conLalns requlremenLs and recommendaLlons regardlng Lhe hosL servers you use for a
vlrLuallzed Lync Server 2013 deploymenL.
Lrror! Unknown document property name.

Þage 29
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0



8.2.1 M|x|ng Þhys|ca| and V|rtua||zed Infrastructure
Mlxlng physlcal and vlrLual servers ln Lhe same pool ls noL a supporLed conflguraLlon. A pool of Lync
Server roles musL be deployed as a homogenous seL of servers (elLher physlcal or vlrLual) whlch provlde
roughly Lhe same performance and have Lhe same amounL of resources. lor vlrLuallzed deploymenLs,
you should make sure LhaL Lhe vlrLual machlnes are hosLed ln a way LhaL equal resources are avallable Lo
each guesL ln Lhe pool. noLe LhaL a vlrLual lronL Lnd Server pool and a physlcal SCL Server 8ack Lnd
Server are expllclLly supporLed.
AddlLlonally, lronL Lnd pools LhaL are palred LogeLher for dlsasLer recovery purposes need Lo boLh be
physlcal pools or boLh be vlrLual pools.
Lync Server 2013 does noL provlde load-based load balanclng. Load-based load balanclng ls Lhe ablllLy Lo
dlrecL users Lo servers LhaL have dlfferenL processor, memory, sLorage, or neLwork capaclLy. 1hls means
LhaL Lhe vlrLual lnsLances are expecLed Lo have equal performance capablllLles, or else Lhe user
experlence wlll be degraded.
8.2.2 Þhys|ca| to V|rtua| CÞU kat|o
1he raLlo of physlcal Lo vlrLual CÞus should noL be oversubscrlbed, speclflcally:
• CversubscrlpLlon of CÞu cores on Lhe hosL runnlng vlrLuallzed Lync Server medla workloads ls
noL supporLed.
• CversubscrlpLlon of CÞu cores on Lhe hosL ls noL recommended when runnlng oLher non-medla
vlrLuallzed Lync Server workloads (such as ulrecLor), or supporLlng vlrLuallzed sLorage workloads
(SCL Server or flle server).
vlrLual machlne reserved allocaLlons are noL expllclLly necessary. lf CÞu oversubscrlpLlon ls
lmplemenLed, conslder allocaLlng vlrLual machlne reserves for crlLlcal workloads such as Lhe SCL Server
lronL Lnd Server.
8.2.3 nost kedundancy
PosL servers wlLhln Lhe envlronmenL should be fully redundanL and slmllar Lync roles (such as lronL Lnd
Servers or 8ack Lnd Servers) should be spread across mulLlple physlcal plaLforms. Pardware such as
blade servers musL have redundanL neLwork, SAn, power, and managemenL. ?ou should ensure Lhere
are noL any slngle polnLs of fallure ln elLher Lhe backplane/chassls LhaL hold Lhe servers or ln
componenLs such as Lhe shared neLwork swlLch beLween all of Lhe blades. A loss of Lhe
backplane/chassls or shared swlLch ln a soluLlon such as a blade envlronmenL musL noL lead Lo an
ouLage of all guesLs runnlng ln Lhe chassls, and Lhus cause a fallure large enough Lo shuL down all Lhe
servlces.
LssenLlally, vlrLuallzaLlon can lnLroduce addlLlonal fallure domalns LhaL you musL accounL for Lo ensure
LhaL Lhe loss of one of Lhese componenLs does noL negaLlvely lmpacL Lhe avallablllLy of Lhe Lync servlces
for users.
Lrror! Unknown document property name.

Þage 30
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0



8.2.4 nost Network|ng Cons|derat|ons
lL ls very lmporLanL Lo conslder LhaL Lync Server medla workloads, such as A/v and appllcaLlon sharlng,
requlre more bandwldLh LhaL oLher Lyplcal server workloads (such as emall or a SCL Server daLabase).
1hese Lync medla workloads are also more vulnerable Lo hlgh laLency and packeL loss problems.
When deslgnlng a vlrLuallzed Lync deploymenL, lL lmporLanL Lo Lake neLworklng conLenLlon lnLo accounL.
neLworklng conslderaLlons:
• Lach hosL musL have aL leasL one dedlcaLed neLwork adapLer for Lhe Lync Server workload.
Shared usage of an adapLer beLween Lhe guesL server and Lhe hosL, speclflcally wlLh SAn access,
ls noL recommended.
• A Lync Server Medla workload (prlmarlly lronL Lnd Servers) can reach a peak neLwork uLlllzaLlon
of more Lhan 300 Mbps (0.3 Cbps).
• lf you use a speclflc hosL server Lo hosL mulLlple guesL vlrLual machlnes runnlng Lync medla
workloads, ensure LhaL Lhe hosL neLwork adapLer ls slzed accordlngly. 1o mlLlgaLe boLLlenecks,
conslder hlgher speed neLwork adapLers (such as 10 ClgablL LLherneL (CbL)), or mulLlple
neLwork adapLers uslng llnk aggregaLlon (neLwork adapLer lLLL 802.3ad), for example, a 3 x 1
CbL neLwork adapLer ln a neLwork adapLer Leamed seLup. lor deLalls, see MlcrosofL knowledge
8ase arLlcle 968703, MlcrosofL SupporL Þollcy for nlC 1eamlng wlLh Pyper-v.
• lmplemenL MÞlC (MulLlpaLh l/C) Lo your sLorage 8ack Lnd Server.
8.2.S nost App||cat|ons and Ant|v|rus
When runnlng Lync Server 2013 ln a server vlrLuallzed scenarlo, we recommend LhaL you do noL deploy
appllcaLlons oLher Lhan anLlvlrus aL Lhe vlrLual machlne hosL rooL operaLlng sysLem parLlLlon.
lf you deploy anLlvlrus sofLware, ensure LhaL Lhe necessary scannlng excepLlons-such as flles, folders,
process-are lmplemenLed.
8.3 Guest kequ|rements
1hls secLlon conLalns requlremenLs and recommendaLlons regardlng Lhe guesL servers you use for a
vlrLuallzed Lync Server 2013 deploymenL.
8.3.1 Guest Core kequ|rements
CuesL core counL llmlLaLlons for Lync Server 2013 lnsLances runnlng as vlrLuallzed guesLs on Lhlrd-parLy
hypervlsors may be llmlLed Lo elghL cores (some vendors supporL elghL, buL recommend a maxlmum of
slx for performance reasons). Lync Server 2013 lnsLances runnlng on Pyper-v ln Wlndows Server 2012
do noL have Lhese llmlLaLlons, nelLher do Lync Server 2013 lnsLances runnlng on physlcal hardware.
Lrror! Unknown document property name.

Þage 31
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0



8.3.2 Guest Cperat|ng System
Wlndows Server 2012 82, Wlndows Server 2012, or Wlndows Server 2008 82 ls requlred as Lhe guesL
operaLlng sysLem.
Wlndows Server 2008 SÞ2 ls noL supporLed as a guesL operaLlng sysLem.
8.3.3 Legacy vs. Synthet|c V|rtua| Network Adapter
neLworklng and neLwork access are crlLlcal Lo Lhe success of a Lync deploymenL. Wlndows Server 2012
Pyper-v provldes a number of capablllLles, Lechnologles, and feaLures LhaL an admlnlsLraLor can use Lo
drlve Lhe hlghesL levels of neLworklng performance for Lhe vlrLuallzed Lync Server lnfrasLrucLure.
When creaLlng a vlrLual machlne, Lhe admlnlsLraLor has Lwo cholces for vlrLual neLwork adapLers (or
vlrLual nlCs): legacy or synLheLlc. A legacy adapLer emulaLes an lnLel 21140-based ÞCl lasL LLherneL
AdapLer, whlch resulLs ln a lower daLa Lransfer Lhan Lhe physlcal neLwork adapLer (usually 1Cbps or
fasLer).
SynLheLlc adapLers are Lhe preferred opLlon for mosL vlrLual machlne conflguraLlons because Lhey use a
dedlcaLed vM8us Lo communlcaLe beLween Lhe vlrLual nlC and Lhe physlcal nlC. 1hls resulLs ln reduced
CÞu cycles, as well as much lower hypervlsor/guesL LranslLlons per operaLlon. 1he drlver for Lhe
synLheLlc adapLer ls lncluded wlLh Lhe lnLegraLlon Servlces LhaL are lnsLalled wlLh Lhe Wlndows Server
2012 guesL operaLlng sysLem.
lrom a Lync Server 2013 perspecLlve, Lhere ls no reason Lo use a legacy vlrLual nlC. AL a mlnlmum,
cusLomers should use Lhe defaulL synLheLlc vlrLual nlC Lo drlve hlgher levels of performance. ln addlLlon,
should Lhe physlcal neLwork card supporL Lhem, Lhe admlnlsLraLor should Lake advanLage of a number of
Lhe nlC offloads LhaL can furLher lncrease performance.
8.3.4 S|ng|e koot I]C V|rtua||zat|on
1he slngle rooL l/C vlrLuallzaLlon (S8-lCv) sLandard was lnLroduced by Lhe ÞCl-SlC, Lhe speclal lnLeresL
group LhaL owns and manages ÞCl speclflcaLlons as open lndusLry sLandards. S8-lCv helps Lo vlrLuallze
demandlng workloads llke Lync Server 2013 LhaL requlre hlgher neLwork and l/C performance. lL does so
by enabllng vlrLual machlnes Lo perform l/C dlrecLly Lo Lhe physlcal neLwork adapLer by bypasslng Lhe
rooL parLlLlon. ln Wlndows Server 2012, S8-lCv can be deployed ln con[uncLlon wlLh key capablllLles
such as llve mlgraLlon Lo enable hlgh neLwork performance wlLh avallablllLy.
S8-lCv provldes exLenslons Lo ÞCl Lxpress (ÞCle) devlces llke neLwork adapLers Lo separaLe access Lo lLs
resources among varlous ÞCle hardware funcLlons. 1wo of Lhese funcLlons are ÞCle Þhyslcal luncLlon
(Þl) and ÞCle vlrLual luncLlons (vls):
• ÞCle Þhyslcal luncLlon ls Lhe prlmary funcLlon of Lhe devlce and adverLlses lLs S8-lCv
capablllLles. 1he Þl ls assoclaLed wlLh Lhe Pyper-v parenL parLlLlon ln a vlrLuallzed envlronmenL.
• ÞCle vlrLual luncLlons are assoclaLed wlLh Lhe Þl of Lhe devlce. A vl shares one or more physlcal
resources, such as memory and neLwork porLs, wlLh Lhe Þl and oLher vls on Lhe devlce. Lach vl
ls assoclaLed wlLh a Pyper-v chlld parLlLlon ln a vlrLuallzed envlronmenL.
Lrror! Unknown document property name.

Þage 32
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0



uslng Pyper-v Manager, you can enable S8-lCv ln Wlndows Server 2012 when you creaLe a vlrLual
swlLch. Always use Lhe synLheLlc vlrLual machlne neLwork adapLer ln Lhe guesL operaLlng sysLem. 1he
use of Lhe legacy neLwork adapLer ls noL supporLed for a guesL operaLlng sysLem runnlng a Lync Server
medla workload.
noLe LhaL S8-lCv was noL LesLed as parL of Lhls LesLlng.
8.3.S IÞv6 and IÞv4
We do noL recommend LhaL you use boLh lÞv4 and lÞv6 on Lhe same nlC as Lhls can cause performance
lssues.
8.3.6 D|sab|e V|rtua| DVD]CD Dr|ves |n Guest
lf vlrLual uvu/Cu drlves are noL requlred ln Lhe guesL operaLlng sysLem, dlsable Lhese drlves Lo prevenL
resources belng allocaLed for Lhelr funcLlon.
8.4 Capab|||t|es Support
1he followlng guldance addresses Lhe areas of concern llsLed above and covers Lhe followlng Loplcs:
• Pypervlsor CapablllLles
• unsupporLed leaLures
• 8ole ÞlacemenL
• Slzlng
8.4.1 nyperv|sor Capab|||t|es
• lor your hypervlsor, you musL use Wlndows Server 2012 82 Pyper-v, Wlndows Server 2012
Pyper-, or a hypervlsor llsLed on Lhe Server vlrLuallzaLlon valldaLlon Þrogram (SvvÞ).
• Wlndows 2008 82 hypervlsors are supporLed buL noL recommended, as Lhey are llmlLed Lo
guesLs wlLh four cores.
• SLorage musL be flxed or pass-Lhrough dlsks (cannoL be dynamlcally expandlng).
• 1he vCÞu Lo pCÞu raLlo musL be 1:1 for medla workload guesLs and may be 1:2 for non-medla
workload guesLs.
• PyperLhreadlng musL be dlsabled.
• Pypervlsors and hardware plaLforms musL supporL vlrLual Machlne Cueulng (vMC).
• non unlform Memory Access (nuMA) spannlng should be dlsabled.
8.4.2 Unsupported Ieatures
• uynamlc memory
• Llve mlgraLlon, qulck mlgraLlon, or equlvalenL feaLures ln oLher hypervlsors
Lrror! Unknown document property name.

Þage 33
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0



8.4.3 ko|e Þ|acement
• lallure domalns or faulL domalns musL be consldered for role placemenL.
• Þool servers (such as lronL Lnd Servers, Ldge Servers, and MedlaLlon Servers) ln Lhe same pool
should be on separaLe physlcal hosL servers Lo lmprove reslllency.
• vlrLuallzaLlon musL be conslsLenL lnslde of a pool. lf one server ln a pool ls vlrLuallzed, all servers
ln LhaL pool musL be vlrLuallzed.
• Þalred pools requlre each pool Lo be Lhe same deploymenL model (physlcal/vlrLual).
8.S Lync Server Capac|ty Þ|ann|ng
MlcrosofL publlshes a capaclLy plannlng calculaLor Lo asslsL ln Lhe plannlng for hardware requlremenLs
for Lync Server 2013. 1he capaclLy plannlng calculaLor ls deslgned Lo asslsL ln deLermlnlng server
requlremenLs based on numbers of users and communlcaLlon modallLles LhaL are enabled for an
organlzaLlon. AddlLlonal overhead should be Laken lnLo accounL for Lhe purposes of plannlng when uslng
a vlrLuallsed lnfrasLrucLure. Powever, we recommend you perform acLual load slmulaLlon LesLlng Lo
ensure LhaL your Lync Server 2013 deploymenL wlll be adequaLely provlsloned. 1o perform sLress LesLlng
under a slmulaLed load, Lhe Lync Server 2013 LSS should be used and a process such as LhaL descrlbed ln
Lhe Lync Server 2013 SLress 1esLlng Culde.
8.S.1 Lync Server Supportab|||ty
Lync Server supporLablllLy does requlre Lhe deflned hardware server speclflcaLlons Lo be fully
supporLable. uslng a lower speclflcaLlon of server should be done wlLh cauLlon and lL ls hlghly
recommended Lo use SLress and Þerformance Lools Lo verlfy Lhe flnal soluLlon.
uurlng a supporL lssue, lf Lhe lssue ls one LhaL would be dlrecLly affecLed by uslng hardware of a lower
speclflcaLlon Lhan LhaL recommended, Lhen Lo galn furLher supporL, Lhe supporLed hardware
requlremenLs musL be meL. 1hls could lead Lo a longer Llme Lo resoluLlon ln Lhls lnsLance.
8.6 n|gh Ava||ab|||ty]D|saster kecovery Strategy
Lync has lLs own archlLecLures for hlgh avallablllLy and dlsasLer recovery. Lync cannoL Lake advanLage of
Lhe hlgh avallablllLy and dlsasLer recovery capablllLles from Lhe hypervlsor buL musL be properly
deslgned for Lhose capablllLles as explalned ln Lhe 1echneL arLlcle Þlannlng for Plgh AvallablllLy and
ulsasLer 8ecovery.
Lrror! Unknown document property name.

Þage 34
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0



9 Append|x A: Stress and Þerformance 1oo| Conf|gurat|on
Deta||s
1he followlng Lables show Lhe values used for many Lync Server parameLers durlng Lhe LesLlng,
compared Lo Lhe defaulLs for Lhese values. We used a CusLom proflle lnLended Lo be as close as posslble
Lo Lhe user proflle as deflned ln Lhe Lync Server 2013 plannlng documenLaLlon. lor more lnformaLlon,
see Lync Server 2013 user Models.
1he followlng Lable ls an example for Lhe cusLom conflguraLlon for a 10,000-user run on an LnLerprlse
LdlLlon pool wlLh Lhree lronL Lnd Servers.
9.1 User Þrov|s|on|ng 1oo|
ÞarameLer uefaulL value 1esL value - 10k LL flnal CommenL
User Creat|on
lronL-Lnd Þool lCun pool1.conLoso.neL ee-pool01.conLoso.com
user name Þreflx LesLuser ee-pool01-user
Þassword Þ[ssw0rd pass[word1
SlÞ uomaln conLoso.neL conLoso.com
AccounL uomaln conLoso.neL conLoso.com
CrganlzaLlonal unlL 1esLusersCrgunlL ee-pool01 users
Þhone Area Code +1423 +1423
1o be adapLed wlLh your
local area code (only works
wlLh uS area codes)
volce Lnabled Lnabled Lnabled
number of users 1000 10000
1hls represenLs 70° of Lhe
LoLal Au users (14283 users
ln Au). AdapL Lo Lhe user
counL you need Lo LesL
SLarL lndex 0 0
Contacts Creat|on
Average ConLacLs per user 30 30
Lync user model speclfy an
average of 30 conLacLs
Lrror! Unknown document property name.

Þage 33
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0



ÞarameLer uefaulL value 1esL value - 10k LL flnal CommenL
llxed Lnabled ulsabled
Make lL random Lo be closer
Lo reallLy
Average ConLacL Croups
per user
3 3
lederaLed / Cross Þool
ConLacLs ÞercenLage
0 0
lederaLed / Cross Þool
user Þreflx
federaLeduser ee-pool01-user
lederaLed / Cross Þool
user SlÞ uomaln
fabrlkam.com fabrlkam.com
D|str|but|on L|st Creat|on
number of ulsLrlbuLlon
LlsLs
100 30000
70° of (Lhree Llmes Lhe
LoLal number of AcLlve
ulrecLory users)
ulsLrlbuLlon LlsL Þreflx LesLuL ee-pool01-uL
Mlnlmum Members ln a
ulsL. LlsL
1 2
8ased on Lhe user model,
mlnlmum number of
members ln a dlsLrlbuLlon
llsL ls 2
Maxlmum Members ln a
ulsL. LlsL
10 300
8ased on Lhe user model,
maxlmum number of
members ln a dlsLrlbuLlon
llsL ls 300
Locat|on Informat|on Serv|ce Conf|g
number of Addresses 100 100
Cfflces Þer Address 100 100
number of WA ÞolnLs 100 100
number of SubneLs 100 100
number of SwlLches 100 100
number of ÞorLs 100 100
C|v|c Address Deta||s
Company name ConLoso CorporaLlon
SLreeL name 163rd
SLreeL name Sufflx Ave
Lrror! Unknown document property name.

Þage 36
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0



ÞarameLer uefaulL value 1esL value - 10k LL flnal CommenL
ÞosL ulrecLlonal nL
ClLy 8ellevue
SLaLe WA
Zlp Code 99234
CounLry uS
1able 2 - SLress and Þerformance ConflguraLlon - user Þrovlslonlng 1ool
9.2 Common Conf|gurat|on
ÞarameLer uefaulL value 1esL value Comment
C||ent Mach|ne Sett|ngs
number of Avallable
Machlnes
3 14
AdapL Lhls accordlng Lo Lhe
number of LesL users
needed. CounL one per 1230
users plus one for large
meeLlngs and one for ÞS1n
LesLlng.
User Sett|ngs
Þreflx for user names myuser ee-pool01-user
Þassword for all users pass[word1
user SLarL lndex 0 0
number of users 40000 10000
AdapL Lhls Lo Lhe user counL
you need Lo LesL
user uomaln conLoso.com conLoso.com
AccounL uomaln conLoso.com conLoso.com
MulLlple ÞolnLs of
Þresence (MÞCÞ)
ÞercenLage
10 90
1:1.9 MÞCÞ raLlo based on
user model wlLh MoblllLy
Slgn ln Þer Second (per
lnsLance)
1 1
Interna| Network Server Sett|ngs
Access Þroxy or Þool
lCun
myServer.conLoso.com ee-pool01.conLoso.com
ÞorL 3061 3061
Lrror! Unknown document property name.

Þage 37
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0



ÞarameLer uefaulL value 1esL value Comment
Lxterna| Network Server Sett|ngs
Access Þroxy or Þool
lCun
myServer.conLoso.com ee-edgepool01-ap.conLoso.com
ÞorL 443 443
1able 3 - SLress and Þerformance ConflguraLlon - Common ConflguraLlon
9.3 Instant Messag|ng
ÞarameLer uefaulL value 1esL value CommenL
IM Advanced Cpt|ons
1woÞarLyConversaLlonÞercenLage 100 100
ConversaLlonÞerPour 1 0.73
Slx peer-Lo-peer lM sesslons per
day. Assumlng 8-hour work day,
Lhen 0.73 lM conversaLlons per
hour.
lnvlLeuserslnConLacLLlsL lALSL 18uL
ConversaLlonLengLhlnSec 600 600
lMMessagesSenLÞerMlnuLe 0.3 1
As a sesslon lasLs for 10 mlnuLes
wlLh 10 messages per sesslon.
ÞarLlclpanL!oln1lmelnSeconds 300 300
LnableCeLÞresence 18uL 18uL
LnableSubscrlpLlonlorAllConLacLs 18uL 18uL
CeLÞresenceCallsÞerPour 60 60
ChangeÞresenceÞerPour 4 4
ChangeÞresenceuserSLaLeÞercenLage 13 100
no reference, we assumed 100
percenL
CeLÞresence1argeLLow 4 4
CeLÞresence1argeLPlgh 8 8
CeLÞresence1argeLCacheSlze 30 30
CeLÞresence1argeL8aLchSlze 1000 1000
LnableChangeÞresence 18uL 18uL
Lrror! Unknown document property name.

Þage 38
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0



ÞarameLer uefaulL value 1esL value CommenL
ChangeCalendarSLaLeÞeruserÞeruay 6 6
ÞubllshCalendaruaLaÞeruserÞeruay 3 3
LnableShorLSubscrlpLlons 18uL 18uL
ShorLSubscrlpLlonsÞerPourÞeruser 4 6
We assume 6 shorL
subscrlpLlons per user per hour
ShorLSubscrlpLlons1argeLLow 1 4
no reference, seL Lo maLch
CeLÞresence1argeLLow
ShorLSubscrlpLlons1argeLPlgh 3 8
no reference, seL Lo maLch
CeLÞresence1argeLPlgh
ShorLSubscrlpLlonsAverage1lmelnSeconds 330 399
Where each subscrlpLlon lasLs
10 mlnuLes. 1he Lool does noL
accepL 600 seconds, and
Lherefore lL's seL Lo 399
AddueleLeConLacLÞeruserÞeruay 0 1 AssumpLlon
IMLxterna| Advanced Cpt|ons
1woÞarLyConversaLlonÞercenLage 90 90
IMConferenc|ng Advanced Cpt|ons
SLaLlcConferenceÞercenLage 80 60
60° scheduled meeLlngs from
conferenclng user model
LobbyConferenceÞercenLage 0 30
lrom Lhe conference lobby user
model.
Lobby1lmeouLlnSec 300 300
LobbyÞarLlclpanL1oAdmlLÞercenLage 80 100
ConversaLlonLengLhlnSec 3600 3600
AdPocConversaLlonCreaLlon 18uL 18uL
SmallConferenceSlze 3 4
lrom Lhe conferenclng user
model.
MedlumConferenceSlze 3 6
lrom Lhe conferenclng user
model.
LargeConferenceSlze 9 11
lrom Lhe conferenclng user
model.
SmallConferenceÞercenLage 83 83
MedlumConferenceÞercenLage 10 10
Lrror! Unknown document property name.

Þage 39
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0



ÞarameLer uefaulL value 1esL value CommenL
LargeConferenceÞercenLage 3 3
IMLarge Advanced Cpt|ons
SLaLlcConferenceÞercenLage 0 0
ÞarLlclpanL!oln1lmelnSeconds 600 600
LargesLConferenceSlze 230 230
1able 4 - SLress and Þerformance ConflguraLlon - lnsLanL Messaglng
9.4 Aud|o Conferenc|ng
ÞarameLer uefaulL value 1esL value CommenLs
AV Advanced Cpt|ons
PardMuLe8yCrganlzer lALSL lALSL
SLaLlcConferenceÞercenLage 80 60
60° of meeLlngs are scheduled, as
speclfled ln Lhe conferenclng user
model.
LnableMuLeunmuLe lALSL lALSL
MuLeAll8yÞresencelnSec 60 60
LobbyConferenceÞercenLage 23 30
lrom Lhe conference lobby user
model.
Lobby1lmeouLlnSec 300 300
LobbyÞarLlclpanL1oAdmlLÞercenLage 80 100 All lobby parLlclpanLs are admlLLed.
ConversaLlonsÞerPour 1 0.23
Assumes 2 conferences per day ln an
8 hour work day.
ConversaLlonLengLhlnSec 3600 3600
AdPocConversaLlonCreaLlon 18uL 18uL
ÞarLlclpanL!oln1lmelnSeconds 300 300
SmallConferenceSlze 3 4 lrom Lhe conferenclng user model.
MulLlvlew lALSL 18uL
AudloSLreamulrecLlon sendrecv sendrecv
vldeoSLreamulrecLlon sendrecv sendrecv
Lrror! Unknown document property name.

Þage 40
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0



ÞarameLer uefaulL value 1esL value CommenLs
ÞanoSLreamulrecLlon lnacLlve lnacLlve
numberCfvldeoChannels 3 3 Medla mlx for conferences.
MedlumConferenceSlze 3 6 lrom Lhe conferenclng user model.
LargeConferenceSlze 9 11 lrom Lhe conferenclng user model.
SmallConferenceÞercenLage 83 83
MedlumConferenceÞercenLage 10 10
LargeConferenceÞercenLage 3 3
AVLarge Advanced Cpt|ons
SLaLlcConferenceÞercenLage 0 0
ÞarLlclpanL!oln1lmelnSeconds 600 600
LargesLConferenceSlze 230 230
1able 3 - SLress and Þerformance ConflguraLlon - Audlo Conferenclng
9.S App||cat|on Shar|ng
ÞarameLer uefaulL value 1esL value CommenL
ASSharer Advanced Cpt|ons
ulsableAppSharlnguecodlnglorvlewers 18uL 18uL
SLaLlcConferenceÞercenLage 80 60
60° of meeLlngs are scheduled, as
assumed ln Lhe conferenclng user
model.
LobbyConferenceÞercenLage 23 30
lrom Lhe conference lobby user
model.
Lobby1lmeouLlnSec 300 300
LobbyÞarLlclpanL1oAdmlLÞercenLage 80 100 All lobby parLlclpanLs are admlLLed
ConversaLlonsÞerPour 1 0.23
Assumes 2 conferences per day ln an
8-hour work day.
ulsplayAppSharlngvlew lALSL lALSL
ConversaLlonLengLhlnSec 3600 3600
AdPocConversaLlonCreaLlon 18uL 18uL
Lrror! Unknown document property name.

Þage 41
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0



ÞarameLer uefaulL value 1esL value CommenL
ÞarLlclpanL!oln1lmelnSeconds 300 300
SmallConferenceSlze 3 4 lrom Lhe conferenclng user model.
MedlumConferenceSlze 3 6 lrom Lhe conferenclng user model.
LargeConferenceSlze 9 11 lrom Lhe conferenclng user model.
SmallConferenceÞercenLage 83 83
MedlumConferenceÞercenLage 10 10
LargeConferenceÞercenLage 3 3
ASV|ewer Advanced Cpt|ons
ulsableAppSharlnguecodlnglorvlewers 18uL 18uL
ulsableAppSharlngvlew lALSL lALSL
AVLarge Advanced Cpt|ons
SLaLlcConferenceÞercenLage 0 0
ÞarLlclpanL!oln1lmelnSeconds 600 600
LargesLConferenceSlze 230 230
1able 6 - SLress and Þerformance ConflguraLlon -AppllcaLlon Sharlng
9.6 Data Co||aborat|on
ÞarameLer uefaulL value 1esL value CommenL
DataCo||ab Advanced Cpt|ons
LnableW13WACSesslon 18uL 18uL
lnLervallornexLuploadlnMlnuLes 3 3
numberCf1lmesÞackages1o8euploaded 1 1
ueleLeCollabConLenLALLndCfConference 18uL 18uL
ShowWhlLeboardlnLverySec 120 120
AnnoLaLlonsÞerMlnuLe 3 3
ÞowerÞolnLÞercenLage 100 20 Medla mlx for conferences
WhlLe8oardÞercenLage 0 20 Medla mlx for conferences
Lrror! Unknown document property name.

Þage 42
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0



ÞarameLer uefaulL value 1esL value CommenL
SLaLlcConferenceÞercenLage 80 60
60° of meeLlngs are scheduled, as
assumed ln Lhe conferenclng user
model.
LobbyConferenceÞercenLage 23 30
lrom Lhe conference lobby user
model.
Lobby1lmeouLlnSec 300 300
LobbyÞarLlclpanL1oAdmlLÞercenLage 80 100 All lobby parLlclpanLs are admlLLed.
lllp8aLelnSec 60 60
ConversaLlonsÞerPour 1 0.23
Assumes 2 conferences per day ln an
8-hour work day.
ConversaLlonLengLhlnSec 3600 3600
AdPocConversaLlonCreaLlon 18uL 18uL
ÞarLlclpanL!oln1lmelnSeconds 300 300
SmallConferenceSlze 3 4 lrom Lhe conferenclng user model.
MedlumConferenceSlze 3 6 lrom Lhe conferenclng user model.
LargeConferenceSlze 9 11 lrom Lhe conferenclng user model.
SmallConferenceÞercenLage 83 83
MedlumConferenceÞercenLage 10 10
LargeConferenceÞercenLage 3 3
DataCo||abLarge Advanced Cpt|ons
SLaLlcConferenceÞercenLage 0 0
ÞarLlclpanL!oln1lmelnSeconds 600 600
LargesLConferenceSlze 230 230
1able 7 - SLress and Þerformance ConflguraLlon -uaLa CollaboraLlon
9.7 D|str|but|on L|st Lxpans|on
ÞarameLer uefaulL value 1esL value CommenL
D|str|but|on L|st Lxpans|on
Þreflx of Lhe ulsLrlbuLlon LlsL's name. 1esLuL se-se01-uL
Lrror! Unknown document property name.

Þage 43
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0



ÞarameLer uefaulL value 1esL value CommenL
uomaln name of Lhe ulsLrlbuLlon LlsL. L.g.
ConLoso.com ls Lhe domaln name for
'ocsdl100[conLoso.com'
vdomaln.com conLoso.com
SLarLlng lndex of Lhe range of ulsLrlbuLlon LlsLs 0 0
Lndlng lndex of Lhe range of ulsLrlbuLlon LlsLs 100 30000
70° of (3 Llmes Lhe LoLal number
of AcLlve ulrecLory users)
(nC1L: 1hls number wlll only be used lf CusLom ls
selecLed from Lhe drop down menu.) number of
ulsLrlbuLlon LlsL Lxpanslon calls Þer user Þer Pour.
0.3 0.3
1able 8 - SLress and Þerformance ConflguraLlon - ulsLrlbuLlon LlsL Lxpanslon
9.8 Address 8ook Çuery
ÞarameLer uefaulL value 1esL value CommenL
A8WÇ Advanced Cpt|ons
A8SCuerlesÞerPour 11 64
lour preflx querles plus 60 exacL search
querles per user per day.
Max8esulLnumber 30 30
SearchALLrlbuLeLlsL
glvenname,
dlsplayname,
Lelephonenumb
er, homeÞhone,
oLherPomeÞhon
e, moblle,
oLherMoblle,oLh
er1elephone,
lpÞhone
glvenname,
dlsplayname,
Lelephonenumb
er, homeÞhone,
oLherPomeÞhon
e, moblle,
oLherMoblle,oLh
er1elephone,
lpÞhone

8eLurnALLrlbuLeLlsL
glvenname,
dlsplayname,
mall
glvenname,
dlsplayname,
mall

8equesL1lmeouL 100 100
CuerylromulalÞadÞercenLage 3 4
CuerySufflxSLarLnumber 0 0
CuerySufflxLndnumber 80000 9999 = user LesL number
Cuery8yÞreflxÞercenLage 90 7
4 preflx querles ouL of 64 LoLal querles ls
6.23. 8ounded up Lo 7.
noLlound8esulLsCueryÞercenLage 0 0
LegacyLndpolnLsÞercenLage 0 0
Lrror! Unknown document property name.

Þage 44
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0



ÞarameLer uefaulL value 1esL value CommenL
ChangeSearchÞercenLage 27 27
ChangeSearch8aLchSlze 23 20
CldLnLryÞercenLage 23 23
ÞhoLoSearchÞercenLage 27 40
23 phoLo querles ouL of 64 querles, rounded
Lo 40°.
CrganlzaLlonSearchÞercenLage 3 2
1 org Lree query ouL of 64 querles, rounded
Lo 2°.
8enewWeb1lckeLÞercenLage 100 100
LnableA8Suownload lALSL lALSL
1able 9 - SLress and Þerformance ConflguraLlon - A8WC Advanced CpLlons
9.9 kesponse Group Serv|ce
ÞarameLer uefaulL value 1esL value CommenL
kGSCa||er Advanced Cpt|ons
LocaLlonÞroflle 8edmond 8eglonalCfflce01
8CSurl slp:my8gsCroup[maln.com
slp:se-se01-
8CS[conLoso.com

8CSurlSufflxSLarLlndex 0 0
8CSurlSufflxLndlndex 600 73 0.13° ouL of 10k users
numberCf8CSCallsÞerPour 3120 390
lf 3120 per hour ls for
80k users, Lhen lL's 390
calls per hour for 10k
users
AverageCallLengLhlnSeconds 180 180
Lnable8ecordlng lALSL lALSL
8ecordlnLerval1lmelnSeconds 60 60
ÞercenLageAnonymousCallsWlLhlM 30 30
1able 10 - SLress and Þerformance ConflguraLlon - 8CS Advanced CpLlons
9.10 Locat|on Informat|on Serv|ces
ÞarameLer uefaulL value 1esL value CommenL
Lrror! Unknown document property name.

Þage 43
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0



ÞarameLer uefaulL value 1esL value CommenL
LIS Advanced Cpt|ons
LnableMa[orLmergencles lALSL ulsabled
LnableÞersonalLmergencles 18uL ulsabled
MlnSeconds8eLweenMa[orLmergency 3600 ulsabled
MaxSeconds8eLweenMa[orLmergency 10800 ulsabled
MlnCalluuraLlonSeconds 120 ulsabled
MaxCalluuraLlonSeconds 300 ulsabled
MlnSeconds8eLweenÞersonalLmergencles 600 ulsabled
MaxSeconds8eLweenÞersonalLmergencles 1800 ulsabled
MlnÞercenLCallerslnMa[orLmergency 3 ulsabled
MaxÞercenLCalleslnMa[orLmergency 20 ulsabled
Lls8equerylrequencySeconds 900 ulsabled
ÞercenLLlsCuerleslromunknownLocaLlon 0 ulsabled
ÞercenLLlsCuerles8yMacAddress 20 ulsabled
LnableSnmpSlmulaLor lALSL ulsabled
SnmpSlmulaLorÞorL 9990 ulsabled
SnmpAverage8esponse1lmelnMs 0 ulsabled
Snmp8ad8esponseÞercenLage 0 ulsabled
Snmpno8esponseÞercenLage 0 ulsabled
1able 11 - SLress and Þerformance ConflguraLlon - LlS Advanced CpLlons
9.11 VoIÞ
ÞarameLer uefaulL value 1esL value
Vo|pUCUC Advanced Cpt|ons
ConversaLlonsÞerPour 1 4
lour peer-Lo-peer calls durlng Lhe busy
hour.
LocaLlonÞroflle 8edmond 8eglonalCfflce01
ÞhoneAreaCode 206 423
1o be adapLed wlLh your local area code
(only works wlLh uS area codes).
Lrror! Unknown document property name.

Þage 46
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0



1able 12 - SLress and Þerformance ConflguraLlon - volÞ Advanced CpLlons
9.12 UC ÞS1N Gateway
ÞarameLer uefaulL value 1esL value CommenL
(nC1L: 1hls number wlll
only be used lf CusLom
ls selecLed from Lhe
drop down menu.) 1he
LoLal number of ÞS1n Lo
uC calls made Lo all
users per hour.
60 2743

1he 96 mlnuLes/user/day comes from Lhe user model LhaL
sLaLes Lhe 8P1 ls 4 ÞS1n calls each wlLh a duraLlon of 3 mlnuLes
1able 13 - SLress and Þerformance ConflguraLlon - uC ÞS1n CaLeway
9.13 Conferenc|ng Attendant
ÞarameLer uefaulL value 1esL value CommenL
CAA Advanced Cpt|ons
1opCfPourConversaLlon lALSL lALSL
LobbyConferenceÞercenLage 30 30 lrom Lhe conference lobby user model.
Lobby1lmeouLlnSec 600 600
LobbyÞarLlclpanL1oAdmlLÞercenLage 100 100
ConversaLlonLengLhlnSec 700 600 Assumes 3 mlnuLes of walL Llme.
AdPocConversaLlonCreaLlon 18uL 18uL
LocaLlonÞroflle 8edmond 8eglonalCfflce01
numberCfCAACallsÞerPour 1393 200
lf 1393 ls for 80k users, Lhen 200 for
10k users
Lnable8ecordlng lALSL lALSL
8ecordlnLerval1lmelnSeconds 60 60
1able 14 - SLress and Þerformance ConflguraLlon - Conferenclng ALLendanL
9.14 Ca|| Þark Serv|ce
ÞarameLer uefaulL value 1esL value CommenL
CÞS Advanced Cpt|ons
Lrror! Unknown document property name.

Þage 47
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0



ÞarameLer uefaulL value 1esL value CommenL
ConversaLlonsÞerPour 1 1
ConversaLlonLengLhlnSec 123 123
ÞhoneAreaCode 206 423
1o be adapLed wlLh your local area code (only
works wlLh uS area codes).
Calls1oÞarkÞercenLage 100 1
user model sLaLes LhaL 0.02 ° of users have
parked calls.
Calls1ounparkÞercenLage 100 100
CalluuraLlonunLllÞarklnSeconds 3 3
AverageÞarkuuraLlonlnSeconds 60 60
1able 13 - SLress and Þerformance ConflguraLlon - Call Þark Servlce
9.1S Med|at|on Server and ÞS1N
ÞarameLer uefaulL value 1esL value CommenL
Informat|on for ÞS1N & Med|at|on Server
MedlaLlon Server lCun myMedlaLlonServer.conLoso.com se-sL02.conLoso.com
MedlaLlon Server ÞorL 3067 3068 8eflecLs seLup.
ÞS1n Area Code (302)
(423)
1o be adapLed wlLh
your local area code
(only works wlLh uS
area codes)
ÞS1n SlmulaLor ÞorL 3067 3068 8eflecLs seLup.
1able 16 - SLress and Þerformance ConflguraLlon - MedlaLlon Server and ÞS1n
9.16 keach - Genera| keach Sett|ngs
ÞarameLer uefaulL value 1esL value CommenL
keach Advanced Cpt|ons
SlpAuLhMeLhod kerberos n1LM
use n1LM lf you have exLernal
access LesLlng.
8each1argeLServerurl se-se01-webexL.conLoso.com
AuLoulscoveryLnabled lALSL 18uL
1able 17 - SLress and Þerformance ConflguraLlon - 8each
Lrror! Unknown document property name.

Þage 48
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0



9.17 keach App||cat|on Shar|ng
ÞarameLer uefaulLv 1esL value CommenL
keachAS Advanced Cpt|ons
ulsableAppSharlnguecodlnglorvlewers 18uL 18uL
LobbyConferenceÞercenLage 0 30 lrom Lhe conference lobby user model.
Lobby1lmeouLlnSec 300 300
LobbyÞarLlclpanL1oAdmlLÞercenLage 80 100 All lobby parLlclpanLs are admlLLed.
ConversaLlonsÞerPour 1 0.23
Assumes 2 conferences per day ln an 8-
hour work day.
ulsplayAppSharlngvlew lALSL lALSL
ConversaLlonLengLhlnSec 3600 3600
ÞarLlclpanL!oln1lmelnSeconds 300 300
1able 18 - SLress and Þerformance ConflguraLlon - 8each AppllcaLlon Sharlng
9.18 keach Data Co||aborat|on
ÞarameLer uefaulL value 1esL value CommenL
keachDataCo||ab Advanced Cpt|ons
LnableW13WACSesslon 18uL 18uL
lnLervallornexLuploadlnMlnuLes 3 3
numberCf1lmesÞackages1o8euploaded 1 1
ueleLeCollabConLenLALLndCfConference 18uL 18uL
ShowWhlLeboardlnLverySec 120 120
AnnoLaLlonsÞerMlnuLe 3 3
ÞowerÞolnLÞercenLage 100 20 Medla mlx for conferences
WhlLe8oardÞercenLage 0 20 Medla mlx for conferences
LobbyConferenceÞercenLage 0 30
lrom Lhe conference lobby user
model.
Lobby1lmeouLlnSec 300 300
LobbyÞarLlclpanL1oAdmlLÞercenLage 80 100 All lobby parLlclpanLs are admlLLed.
Lrror! Unknown document property name.

Þage 49
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0



ÞarameLer uefaulL value 1esL value CommenL
lllp8aLelnSec 60 60
ConversaLlonsÞerPour 1 0.23
Assumes 2 conferences per day ln
an 8-hour work day.
ConversaLlonLengLhlnSec 3600 3600
ÞarLlclpanL!oln1lmelnSeconds 300 300
1able 19 - SLress and Þerformance ConflguraLlon - 8each uaLa CollaboraLlon
9.19 keach Instant Messag|ng
ÞarameLer uefaulL value 1esL value CommenL
keachIM Advanced Cpt|ons
LobbyConferenceÞercenLage 0 30 lrom Lhe conference lobby user model.
Lobby1lmeouLlnSec 300 300
LobbyÞarLlclpanL1oAdmlLÞercenLage 80 100 All lobby parLlclpanLs are admlLLed.
ConversaLlonsÞerPour 1 0.23
Assumes 2 conferences per day ln an 8-hour
work day.
ConversaLlonLengLhlnSec 3600 3600
ÞarLlclpanL!oln1lmelnSeconds 300 300
1able 20 - SLress and Þerformance ConflguraLlon - 8each lnsLanL Messaglng
9.20 keach Vo|ce Conferenc|ng
ÞarameLer uefaulL value 1esL value CommenL
keachAV Advanced Cpt|ons
LobbyConferenceÞercenLage 0 30 lrom Lhe conference lobby user model.
Lobby1lmeouLlnSec 300 300
LobbyÞarLlclpanL1oAdmlLÞercenLage 80 100 All lobby parLlclpanLs are admlLLed.
ConversaLlonLengLhlnSec 3600 3600
1able 21 - SLress and Þerformance ConflguraLlon - 8each Conference volce
Lrror! Unknown document property name.

Þage 30
Lync Server 2013 vlrLuallzaLlon WhlLe Þaper, verslon 1.0



9.21 Mob|||ty (UCWA) - Genera| Mob|||ty Sett|ngs
ÞarameLer uefaulL value 1esL value CommenL
Mob|||ty Advanced Cpt|ons
ucwa1argeLServerurl se-se01-webexL.conLoso.com
ucwa1argeLServerÞorL 443
WorkuayuuraLlon 10 8
Assume sLandard
worklng hours.
numberCfConLacLvlewsÞeruay 9 9
numberCfConLacLLlsLvlewsÞeruay 3 3
numberCfSelfÞresenceChangesÞeruay 1 1
Cnllne1olnacLlveuserAcLlvlLylnLervalMlnuLes 3 3
LnableÞhoLoleLchlng lALSL 18uL ÞhoLo Lnabled
AuLoulscoveryLnabled lALSL 18uL
SearchLnabled 18uL 18uL
SearchlnLervalSeconds 6000 6000
CommaSeparaLedSearchSLrlng se-se01-user
Þnchuser8anges 0-3999 40° of LoLal users
Search8eLurnLlmlL 23 23
CuLgolnglMSesslonsÞeruserÞeruay 8 8
CuLgolngAvSesslonsÞeruserÞeruay 24 24
1able 22 - SLress and Þerformance ConflguraLlon - Moblle (uCWA)
9.22 Mob|||ty Þresence and Þ2Þ Instant Messag|ng]Aud|o
ÞarameLer uefaulL value 1esL value CommenL
Mob|||tyÞresence Advanced Cpt|ons
ConversaLlonsÞerPour 0.373 0.373
ConversaLlonLengLhlnSec 360 360
1able 23 - SLress and Þerformance ConflguraLlon - MoblllLy Þresence and lM