This document is provided as-is.

Information and views expressed in this document,

including URL and other Internet e! site references, ma" change without notice.
#ome examples depicted herein are provided for illustration onl" and are fictitious. $o real
association or connection is intended or should !e inferred.
This document does not provide "ou with an" legal rights to an" intellectual propert" in an"
%icrosoft product. &ou ma" cop" and use this document for "our internal, reference
purposes.
'op"right ( )*++ %icrosoft 'orporation. ,ll rights reserved.
%icrosoft, ,ctive -irector", .xcel, L"nc, /utloo0, 1ower1oint, #2L #erver, 3isual '44,
indows, indows %edia, and indows 1ower#hell are trademar0s of the %icrosoft group
of companies. ,ll other trademar0s are propert" of their respective owners.
Microsoft Lync Server 2010 Resource Kit Archiving and Monitoring Page 2
This chapter is part of the %icrosoft L"nc #erver )*+* Resource 5it !oo0 that is currentl"
!eing developed. 'hapters will !e availa!le for download while this !oo0 is !eing completed.
To help us improve it, we need "our feed!ac0. &ou can contact us at
nexthop@microsoft.com. 1lease include the chapter name.
6or information a!out the continuing release of chapters, chec0 the -rRe7 !log at
http://go.microsoft.com/fwlink/?LinkId=2045!.
Microsoft Lync Server 2010 Resource Kit Archiving and Monitoring Page 3
Contributors
Project Manager: #usan #. 8radle"
Content Architect: Rui %aximo
Chapter Lead: 8"ron #purloc0
Writers: 5eith 9anna
Sidebar Contributor: 8"ron #purloc0
Technical Reviewers: :ang 1eng, ;effer" Reed, Lei 9ua, Thomas Lee, eiming #hen, <u
Liu
Lead Editor: ,lexandra Lise
Art Manager: ;im 8radle"
Production Editor: 5ell" 6uller 8lue
Microsoft Lync Server 2010 Resource Kit Archiving and Monitoring Page 4
Table of Contents
Contributors................................................................................................................................. 4
Contributors................................................................................................................................. 4
Introduction.................................................................................................................................. 7
Introduction.................................................................................................................................. 7
PART 1: ARCHVING................................................................................................................... 7
PART 1: ARCHVING................................................................................................................... 7
New Archiin! "e#tures............................................................................................................... 7
New Archiin! "e#tures............................................................................................................... 7
Archiin! In$r#structure ........................................................................................................... 7
Archiin! Po%ic&........................................................................................................................ '
Notes $ro( the "ie%d..................................................................................................................... '
Notes $ro( the "ie%d..................................................................................................................... '
Runnin! Archiin! )erer in Critic#% *ode...............................................................................'
Runnin! Archiin! )erer in Critic#% *ode...................................................................................'
Archiin! Co(+onents #nd ,e+endencies..................................................................................-
Archiin! Co(+onents #nd ,e+endencies..................................................................................-
I* #nd .eb Con$erencin! Archiin! Inte!r#tion........................................................................11
I* #nd .eb Con$erencin! Archiin! Inte!r#tion........................................................................11
.eb Con$erencin! Archiin! To+o%o!&..................................................................................12
)c#%in! #nd Per$or(#nce........................................................................................................... 14
)c#%in! #nd Per$or(#nce........................................................................................................... 14
Archiin! C(d%ets...................................................................................................................... 1/
Archiin! C(d%ets...................................................................................................................... 1/
Retriein! Records b& 0sin! the 12+ort3CsArchiin!,#t# C(d%et.........................................1/
PART 2: *4NIT4RING............................................................................................................. 17
PART 2: *4NIT4RING............................................................................................................. 17
New *onitorin! "e#tures........................................................................................................... 17
New *onitorin! "e#tures........................................................................................................... 17
Microsoft Lync Server 2010 Resource Kit Archiving and Monitoring Page /
1nd3to31nd )cen#rio #nd He#%th *onitorin! .........................................................................1'
C#%% Re%i#bi%it& *onitorin! ...................................................................................................... 1-
*edi# 5u#%it& *onitorin! ....................................................................................................... 1-
)erice He#%th *onitorin! ..................................................................................................... 26
C#%% 5u#%it&................................................................................................................................ 26
C#%% 5u#%it&................................................................................................................................ 26
7istenin! *4)........................................................................................................................ 21
)endin! *4)......................................................................................................................... 21
Networ8 *4)......................................................................................................................... 21
Coners#tion#% *4).............................................................................................................. 22
Inter+retin! *4) V#%ues........................................................................................................ 23
Troub%eshootin! *4) issues................................................................................................. 23
*onitorin! )erer Re+orts ........................................................................................................ 23
*onitorin! )erer Re+orts ........................................................................................................ 23
0ser Re!istr#tion Re+ort........................................................................................................ 29
C#%% Re%i#bi%it& )u((#r& Re+ort............................................................................................. 27
Re+ort Custo(i:#tion................................................................................................................ 32
Re+ort Custo(i:#tion................................................................................................................ 32
Hi!h37ee% Per$or(#nce Counters............................................................................................. 39
Hi!h37ee% Per$or(#nce Counters............................................................................................. 39
*onitorin! ,#t#b#se )i:in! ................................................................................................... 37
)u((#r&................................................................................................................................... 37
)u((#r&................................................................................................................................... 37
Addition#% Resources................................................................................................................. 3'
Addition#% Resources................................................................................................................. 3'
Microsoft Lync Server 2010 Resource Kit Archiving and Monitoring Page 9
Introduction
6or compliance purposes, man" organi7ations and most financial companies, pharmaceutical
companies, financial departments, and law departments re=uire instant messaging >I%?
archiving. #ome of these organi7ations also re=uire we! conferencing archiving. %icrosoft@
L"ncA #erver )*+* provides a wa" to archive information from I% conversations,
conferences, or !oth and to customi7e how information is archived, for example for which
users. This chapter descri!es archiving in L"nc #erver )*+*.
This chapter also descri!es monitoring in L"nc #erver. L"nc #erver provides new and
improved monitoring features and reports that "ou can use to monitor s"stem heath and
usage. Use these tools to discover hardware failures, networ0 segment outages, and other
s"stem pro!lems earl", which can help minimi7e their impact, and to collect data a!out
media =ualit", L"nc #erver wor0load use, and errorsBdata that can help with
trou!leshooting and planning "our training and capital investment.
PART 1: ARCHVING
New Archiving eatures
There are a few changes to the archiving infrastructure and the wa" archiving polic" wor0s
in L"nc #erver. In L"nc #erver, the archiving agent runs on the 6ront .nd pool on a server
running %icrosoft@ L"ncA #erver )*+*, #tandard .dition.
Archiving Infrastructure
If "our organi7ation has a mission-critical re=uirement, such as a compliance regulation,
that all instant messages are archived, "ou need a plan in case ,rchiving #erver !ecomes
unavaila!le. &our plan should !e to ena!le critical mode.
Note. Critical mode is not enabled by default.
In previous versions >%icrosoft@ /ffice 'ommunications #erver )**C R) and %icrosoft@
/ffice 'ommunications #erver )**C?, when critical mode is ena!led, the 6ront-.nd service
stops if ,rchiving #erver !ecame unavaila!le, which results in I% !eing unavaila!le for the
entire organi7ation. In addition, the Registrar shuts down, so voice calls are affected as well.
'ritical mode wor0s differentl" in L"nc #erver. In L"nc #erver, if, for an" reason, the
archiving data!ase is unavaila!le, the L"nc #erver 6ront-.nd service continues to run until
the message =ueue reaches capacit" >+ :8 !" default?. hen capacit" is reached, I% and
we! conferencing functionalit" !ecome unavaila!le >I% and we! conferencing are coupled in
L"nc #erver ,rchiving #erver? !ecause I% and we! conferencing content and details can no
longer !e archived. 9owever, other wor0loads, such as .nterprise 3oice, will continue to
operate as usual, so users can still do things li0e ma0e and receive calls.
Note. If a conference participant uploads a file, but the file cannot be copied to the archiving file store, web
conferencing functionality is blocked until the problem is resolved, but IM functionality is not blocked.
hen the L"nc #erver archiving agent fails to archive I% >that is =ueued in %essage
2ueuing, also 0nown as %#%2, or in the local data!ase?, it sends a #I1 error response. The
response includes a ms-diagnostics header that indicates the failure, so clients can respond
appropriatel".
Microsoft Lync Server 2010 Resource Kit Archiving and Monitoring Page 7
Archiving Polic!
%an" organi7ations find it useful to 0eep an archive of all I% conversations that their users
ta0e part inD other organi7ations are legall" re=uired to 0eep such an archive. In order to
archive I% conversations with L"nc #erver, "ou must perform two steps. 6irst, "ou need to
ena!le archiving at the glo!al scope, the site scope, or !oth !" using the Set
CsArchivingCon!iguration cmdlet. This gives "ou the a!ilit" to archive I% conversations.
It does not, however, automaticall" !egin archiving those conversations.
Instead, to actuall" save transcripts of "our I% conversations, "ou must complete a second
stepE create one or more I% archiving polic" that determines which users will have their I%
conversations recorded and which t"pe of I% conversations >internal, external, or !oth? will
!e archived. Internal I% conversations are sessions where all the participants are
authenticated users who have ,ctive -irector"@ -omain #ervices accounts in "our
organi7ationD external I% conversations are sessions where at least one participant is an
unauthenticated user who does not have an ,ctive -irector" account in "our organi7ation.
,s noted, archiving policies can !e assigned to the glo!al scope or to the site scope. In
addition, these policies can !e assigned to the per-user scope and then applied to a specific
user or a specific set of users. 6or example, suppose "our glo!al polic" archives onl"
internal I% conversations for all of "our users. In that case, "ou might create a second
polic", one that archives !oth internal and external conversations, and appl" that polic" to
onl" "our sales staff. 8ecause per-user policies ta0e precedence over glo!al and site
policies, mem!ers of the sales staff will have all their I% conversations archived. /ther
users >users who are not part of the sales department and are not affected !" the sales
polic"? will have onl" their internal I% conversations archived.
&ou can create new archiving policies >at either the site or the per-user scope? !" using the
"ewCsArchivingPolic# cmdlet. If "ou create a polic" at the site scope, it will
automaticall" !e applied to the site at the time the polic" is created. If "ou create a polic" at
the per-user scope, that polic" will not !e used until "ou explicitl" assign it to a user or set
of users !" using the $rantCsArchivingPolic# cmdlet. &ou cannot create a new polic" at
the glo!al scope.
Notes fro" the ield
Running Archiving Server in Critical Mode
#!ron $%urloc&
Founder and Principal Architect of uadrantechnologies
If "ou ena!le critical mode in L"nc #erver to ma0e sure no conversations or conferences go
unarchived when and if the L"nc #erver ,rchiving service or the archiving data!ase
!ecomes unavaila!le, the 6ront-.nd service will not come to a screeching halt, li0e it did in
previous versions. Instead, it will continue to run as usual until the =ueue that contains the
instant messages is not a!le to hold an" more messages. ,fter this occurs, !oth instant
messaging and we! conferencing functionalit" are !loc0ed until the issue has !een resolved.
>#imilarl", if a conference participant uploads content that cannot !e copied to the archiving
location, we! conferencing is !loc0ed for the organi7ation when "ouFre running in critical
mode.?
There is a =ueue on the 6ront .nd #erver that will hold all the instant messages that are
destined for the archiving data!ase =ueue and that has a default si7e of + :8, which "ou
Microsoft Lync Server 2010 Resource Kit Archiving and Monitoring Page '
can adGust. #o what happens when this =ueue reaches its capacit"H This is when users can
no longer send or receive instant messages or participate in conferences.
This isnFt cause for great alarm, !ecause unli0e in 'ommunications #erver )**C R), in L"nc
#erver, the !loc0ing of instant messaging and we! conferencing does not affect an" other
L"nc #erver features or functionalit"D things li0e voice will continue to operate as normal.
%e# Ta&eawa#: If critical mode is ena!led, increase the si7e of the %essage 2ueuing
storage location.
Archiving Co"%onents and 'e%endencies
8efore deplo"ing ,rchiving #erver, "ou must install the following softwareE
, indows@ operating s"stem and re=uired indows updates on supported hardware for
each server that "ou want to deplo" archiving components on, including the ,rchiving
#erver, archiving data!ase, and archiving file store. 6or details a!out the hardware and
software re=uirements for L"nc #erver and data!ase servers, see -etermining &our
#"stem Re=uirements at http://go.microsoft.com/fwlink/?LinkId=20""2.
#oftware prere=uisites for L"nc #erver, including %icrosoft@ .$.T 6ramewor0 I.J with
#ervice 1ac0 + >#1+?, the %icrosoft@ 3isual '44@ Redistri!uta!le, the %icrosoft@
3isual ;K Redistri!uta!le, the URL Rewrite %odule version ).* Redistri!uta!le, indows
%edia@ 6ormat Runtime, indows 1ower#hellA version ).*, and indows Installer
version L.J. 6or details a!out all prere=uisites, see ,dditional #oftware Re=uirements at
http://go.microsoft.com/fwlink/?LinkId=2".
%essage 2ueuing with ,ctive -irector" Integration ena!led on the ,rchiving #erver and on
each server running %icrosoft@ L"ncA #erver )*+*, 6ront .nd #erver or L"nc #erver
)*+* #tandard .dition that hosts users who will have I% archived. 6or details a!out
%essage 2ueuing re=uirements, see ,dditional #oftware Re=uirements at
http://go.microsoft.com/fwlink/?LinkId=2".
%icrosoft@ #2L #erver@ )**M or %icrosoft@ #2L #erver@ )**J with #ervice 1ac0 ) >#1)?
>re=uired? or the latest service pac0 >recommended? on the computer that will host the
archiving data!ase. 6or details a!out supported versions, see -ata!ase #oftware and
'lustering #upport at http://go.microsoft.com/fwlink/?LinkId=2"#.
Microsoft Lync Server 2010 Resource Kit Archiving and Monitoring Page -
The following diagram shows the dependencies of the L"nc #erver ,rchiving service and
other services and stores.

igure 1( Archiving co"%onents and de%endencies
The dependencies of the archiving components are as followsE
Note. !he "ync #erver Archiving service is not part of the Front $nd cluster in a consolidated topology.
The I% archiving agent runs on the User #ervices cluster, and the we! conferencing
archiving agent runs on the 'onferencing services cluster.
%ultiple User #ervices >I% archiving agents? can point to one L"nc #erver ,rchiving service.
%ultiple 'onferencing services >we! conferencing archiving agents? can point to one L"nc
#erver ,rchiving service.
The L"nc #erver ,rchiving service depends on !oth a %icrosoft@ #2L #erver@ data!ase
and a file store.
%ultiple archiving services can share a single archiving #2L #erver data!ase.
%ultiple archiving services can share a single archiving file store.
The following diagram loo0s more closel" at dependencies of the L"nc #erver ,rchiving
service.

Microsoft Lync Server 2010 Resource Kit Archiving and Monitoring Page 16
igure )( *!nc $erver Archiving service de%endencies
The dependencies for the L"nc #erver ,rchiving service are as followsE
The mandator" dependenc" !etween the ,rchiving #erver and L"nc #erver ,rchiving service
provides the !ac0end data!ase location.
%ultiple ,rchiving #ervers cannot share the same archiving data!ase.
The mandator" dependenc" !etween the ,rchiving #erver and the file store provides the
place where the file content is archived.
%ultiple ,rchiving #ervers can share the same file store.
I+ and ,eb Conferencing Archiving Integration
In L"nc #erver, li0e in previous versions, I% content and we! conferencing content is
archived separatel". I% content, along with conference metadata, such as participation
records, is archived in the archiving data!ase. 'onference content, along with metadata
a!out the content, such as the time stamp, is archived in a file store. The integration
!etween I% and we! conferencing happens as followsE
The same glo!al or per-user archiving polic" is enforced on !oth I% content archiving and
on we! conferencing content archiving.
The e! 'onferencing service has a !uilt-in archiving agent that interfaces with ,rchiving
#erver !" using %essage 2ueuing.
The e! 'onferencing service archiving agent writes we! conferencing content events
>metadata? into the archiving data!ase >!" using %essage 2ueuing?. 6or performance
optimi7ation, the e! 'onferencing service !atches data events and writes them ever"
< minutes so that onl" the last < minutes worth of content is lost if we! conferencing
fails.
The e! 'onferencing service writes uploaded content to a dis0.
,rchiving #erver creates a folder for a given we! conferencing instance and stores it in the
archiving data!ase.
,rchiving #erver enforces the purging and archiving logic. If purging is on, an archiving
record is deleted at the time of purging when one of the following conditions are metE
The record is mar0ed safe to delete. This could happen when a transcript export tool
has !een run.
The record is older than the num!er of da"s the archive is 0ept.
,rchiving #erver enforces the per-user polic". ,ll conferences are logged in the archive
when logging is on. hen we! conferencing archiving is ena!led, the ,rchiving #erver
reviews the records in the archive and 0eeps records onl" for conferences that meet the
following conditionsE
There are participants who need to !e archived for internal communications, and
more than one internal user is participating.
Microsoft Lync Server 2010 Resource Kit Archiving and Monitoring Page 11
There are participants who need to !e archived for external communication, and at
least one internal user is participating.
1urging records for per-user polic" enforcement happens regardless of whether
purging is ena!led and should occur more fre=uentl" than the default purging
process, which is N* da"s.
,eb Conferencing Archiving To%olog!
In L"nc #erver, the we!-conferencing archiving topolog" is integrated into the I% topolog".
The topolog" for we! conferencing archiving wor0s as followsE
The e! 'onferencing service writes the uploaded content to a networ0 file store that "ou
can configure.
The e! 'onferencing service writes events to %essage 2ueuing.
The L"nc #erver ,rchiving service reads the events from %essage 2ueuing to put them into
the archiving data!ase.
These components are shown in the following figure.
igure -( ,eb Conferencing service archiving co"%onents
The ,rchiving #erver is responsi!le for cleaning up the archiving data!ase.
The following diagram gives an overview of how data is stored in the archiving data!ase.
Microsoft Lync Server 2010 Resource Kit Archiving and Monitoring Page 12
igure .( 'ata storage in the archiving database
'onference activation wor0s as followsE
+. , user Goins a conference.
). The I% archive logs a conference Goin event.
I. If it is the first Goin event, the I% archive logs the exact location of the we!
conferencing archive for this conference, and the e! 'onferencing service creates
the archive folder for this conference.
L. The user adds a data modalit" to the conference.
6ile upload wor0s as followsE
+. , user uploads a file to the e! 'onferencing service.
). The e! 'onferencing service logs the file upload event in the ,rchiving #erver.
I. The e! 'onferencing service stores the uploaded file.
Microsoft Lync Server 2010 Resource Kit Archiving and Monitoring Page 13
$caling and Perfor"ance
hen deplo"ing ,rchiving #erver, "ou must associate it with the servers running L"nc
#erver )*+*, 6ront .nd #erver in a pool. ,rchiving #erver then collects I% content from
communications involving the users who are homed in the pool.
6or the !est scala!ilit", do not collocate the ,rchiving #erver with another server role.
9owever, "ou can host the archiving data!ases on the ,rchiving #erverD hosting the
archiving data!ases on a separate computer does not significantl" improve performance.
Note. %ne Archiving #erver can support up to &'',''' users. If you have multiple pools that support less
than &'',''' users total, we recommend that you associate all these pools with a single Archiving #erver
to simplify administration and data retrieval.
6or optimal performance, we recommend that "ou put each of the following items on a
separate ph"sical dis0E
#"stem file and %essage 2ueuing file
,rchiving data!ase data file
,rchiving data!ase log file
&ou can collocate the archiving data!ase with other data!ases, !ut we recommend carefull"
evaluating performance impact !efore "ou do. If "ou do collocate the archiving data!ases
with other data!ases on the same server, "ou should run the archiving data!ase in a
separate instance from other data!ases.
&ou can !ase "our performance evaluation on the following assumptions and example. The
example imagines an organi7ation with +**,*** I% and we! conferencing users. It assumes
that, for peer-to-peer I%E
.ach user has an average of two I% conversations per hour. This means that
for +**,*** users, there are +**,*** I% conversations per hour, or )C.M I%
conversations per second.
.ach I% conversation consists of an average of +* instant messages.
.ach instant message consists of a? an average of )** characters and !? metadata >details
such as who sent the instant message and when? that is, on average, +** characters.
This means that the transcript for each I% conversation contains I,*** characters on
average.
6or group I%, the example assumes thatE
There is a five percent concurrent conferencing user rate, that is, in ever" wor0 hour, for
+**,*** users, there are J,*** users participating in a group I% conversation or a
conference.
Thirt" percent >+,J** in our example? of concurrent conferencing users are part of a group
I% conference.
The average group I% conference si7e is three, which means there are J** group I%
conferences per hour in our example, or *.+L conferences per second.
.ach group I% conference consists of an average of +J instant messages.
Microsoft Lync Server 2010 Resource Kit Archiving and Monitoring Page 14
.ach instant message consists of a? an average of )** characters and !? metadata that is,
on average, +** characters. This means that the transcript for each group I% conference
contains L,J** characters on average. e will round down to L,*** for our example.
,nd for conferences, we assumed thatE
There is a five percent concurrent conferencing user rate for group I% and conferences
com!ined, that is, in ever" wor0 hour, for +**,*** users, there are J,*** users
participating in a group I% conversation or a conference.
Twent"-five percent >+,)J* in our example? of concurrent conferencing users are part of a
conference.
The average conference si7e is six, which means there are )*M.I conferences per hour in
our example, or *.*JM conferences per second.
The content si7e distri!ution for each conference is, on average, two +* %8 %icrosoft@
1ower1oint@ presentations and one J %8 handout. This means )J %8 of content per
conference per J,*** concurrent users.
#o for a +**,*** user deplo"ment, "ou could plan on there !eingE
)C.M 4 *.+L 4 *.*JM O ,pproximatel" )M transcripts per second
,ndE
>)C.M PI? 4 >*.+L PL? 4 >*.*JM PJ? O ML.)J 58 of metadata per second
,nd, if "ou are including we! conferencing data as part of the meeting transcriptE
>)C.M PI? 4 >*.+L PL? 4 >*.*JM PJ? 4 >)J P+*)L? O )JNML.)J 58 total data per
second
Note. If archiving is mission(critical for your organi)ation, you should enable critical mode in case archiving
fails. If you enable critical mode, it applies to only the failed workload. For e*ample, if the failure affects
only web conferencing, web conferencing is blocked until the problem is resolved, but other workloads,
such as $nterprise +oice, are not blocked. For details about critical mode, see the section ,Archiving
Infrastructure,- earlier in this chapter.
Archiving C"dlets
ith L"nc #erver ,rchiving #erver, "ou can use the various CsArchivingCon!iguration
cmdlets to ena!le and disa!le I% archiving and to manage "our archiving data!ase. &ou can
also suspend I% should archiving fail, which helps ensure that "ou 0eep a record of all "our
electronic communications. 6or details a!out the CsArchivingCon!iguration cmdlets, see
,rchiving and %onitoring 'mdlets at http://go.microsoft.com/fwlink/?LinkId=22"2$.
/ne useful CsArchivingCon!iguration cmdlet is E'portCsArchiving(ata. This cmdlet
extracts all the records or a selected su!set of records from the archiving data!ase and
saves them as a %icrosoft@ /utloo0@ .xpress .lectronic %ail >.%L? file so that "ou can
view them.
Retrieving Records b! /sing the 01%ort2CsArchiving'ata C"dlet
The E'portCsArchiving(ata cmdlet scans archiving data in a given archiving data!ase
and constructs per-conference transcripts for all conferences that happened in a specified
date range. Those transcripts are exported and saved in the specified output folder. -ata
Microsoft Lync Server 2010 Resource Kit Archiving and Monitoring Page 1/
records used in transcripts can optionall" !e mar0ed as exported or safe to purge. , period
of time, indicated !" a start time and an end time, is re=uired.
Note. .y default, only members of /!C0niversal#erverAdmins are authori)ed to run Export-
CsArchivingData locally.
The following ta!le descri!es the parameters for E'portCsArchiving(ata.
Table 1( 01%ort2CsArchiving'ata %ara"eters
Para"eter 'escri%tion T!%e
StartDate Start date (required) and time for
export. Inclusive. Local time.
MMDDYYYY [hh:mm:ss format.
Defaults to !":## $.M. if no time is
specified.
Date
%ndDate %nd date (required) and time for
export. %xclusive. Local time.
MMDDYYYY [hh:mm:ss format.
Defaults to the current date and
time if not specified.
Date
&ser&'I &ser (hose conference
involvement (ill )e exported.
&niform 'esource
Identifier (&'I)
D*Insatnce Data)ase instance of the archivin+
data)ase.
Strin+
%xclude,e)-onf$rchive ,e) conferencin+ archivin+ data
(ill )e excluded. if present.
*oolean
/utput0older 0older in (hich to output
transcripts (required).
12$
3ur+e 'ecord is safe to pur+e. if present. Strin+
,hatIf Description of (hat (ill happen if
4ou run this command.
*oolean
Example Exporting Commands
The following command exports all conferences that !egin !etween +)E** ,.%. on %arch +,
)*++ and the current date. The conference transcript includes we! conferencing data, and
all records used are mar0ed as safe to purge.
Export-CSArchiveData -StartDate 03012011 -DBInstance Server1\rtc
-OutputFoler \\Server1\export -!ur"e
The following command exports all conferences that happened during %arch )*++. The
conference transcript does not include we! conferencing data, and all records used will not
!e mar0ed as safe to purge.
Export-CSArchiveData -StartDate 03012011 -EnDate 0#012011 -DBInstance
\Server1\rtc -OutputFoler \\Server1\export -Exclue$e%Con&Archive
Export-CsArchivingData Output
hen the parameter hatIf is present, the output is the num!er of sessions that would !e
exported. /therwise, output from E'portCsArchiving(ata loo0s li0e thisE
Startin" to export transcripts
Session 'sessionI(i)e * SessionISe+, success&ull- exporte
Microsoft Lync Server 2010 Resource Kit Archiving and Monitoring Page 19
Session 'sessionI(i)e * SessionISe+, success&ull- exporte
..
Session export success&ul/ 000 total sessions exporte/
Trouleshooting Exporting !ssues
'auses for errors include the followingE
The user does not have readQwrite permission to the archiving data!ase.
The user does not have readQwrite permission to the archiving file store.
There is a dis0-write error.
The dis0 is full.
1urge is not allowed !ecause the parameter .xcludee!'onf,rchive is present.
The start is time not valid.
The end time is not valid.
The user URI is not valid.
PART ): +3NIT3RING
New +onitoring eatures
L"nc #erver introduces several new features that enhance %onitoring #erver, including
read"-made and customi7a!le call detail recording >'-R? and 2ualit" of .xperience >2o.?
reports. In L"nc #erver %onitoring #erver, "ou will findE
Rich reporting: %onitoring #erver ta0es advantage of #2L #erver Reporting
#ervices to provide read"-made reporting on s"stem usage, call relia!ilit", and
media =ualit" diagnostics. , custom dash!oard presents an aggregation of these
reports from a single location.
"ew )anage)ent !eatures: %onitoring #erver now uses L"nc #erver %anagement
#hell and L"nc #erver 'ontrol 1anel for all administration and management tas0s.
*)proved server diagnostics: 'lient and server components consistentl" report
diagnostics in failure responses to #I1 I$3IT. messagesBto explain wh" a call could
not !e esta!lishedBand in 8&. messages to I$3IT. dialogsBto explain wh" a call
was terminated. This ma0es trou!leshooting significantl" easier.
+pti)i,ed in!rastructure: The %onitoring #erver infrastructure has !een optimi7ed
to improve relia!ilit" and maintaina!ilit".
-oE i)prove)ents: , significant amount of time was invested in determining
thresholds at which different metrics !egin to cause noticea!le call =ualit"
degradationBmetrics including Gitter, pac0et loss, round-trip time, and loss
concealment.
Monitoring Server report readabilit#: %etrics that fail to meet accepta!le
thresholds are highlighted in %onitoring #erver reports as "ellow or red. This
Microsoft Lync Server 2010 Resource Kit Archiving and Monitoring Page 17
removes the need for administrators to evaluate each metric. In addition, "ou can
pause on the various metrics in the reports to open tooltips that provide details
a!out the 2o. metric.
.ser !acing diagnostics: If end users experience poor sound =ualit", new UI helps
explain the causeBfor example, the userFs device might not !e wor0ing correctl", the
volume might !e too low, the networ0 might !e intermittent, or their computer might
!e slow !ecause of heav" '1U consumption. These diagnostics are included with
%onitoring #erver reports and can help with trou!leshooting.
C(R: ,ll successful, failed, and dropped conference Goins are now recorded, whereas
previousl", onl" successful conference Goins were.
0nd2to20nd $cenario and Health +onitoring
L"nc #erver introduces a num!er of new concepts a!out the followingE
.nd-to-end scenario monitoring
'all relia!ilit" monitoring
%edia =ualit" monitoring
#ervice health monitoring
End-to-End Scenario Monitoring
%&nthetic tr'ns'ctions are indows 1ower#hell cmdlets that allow end-to-end tests to !e
carried out. The" provide a true end-to-end perspective on the environment and are an
integral part of the %icrosoft@ #"stem 'enter /perations %anager >formerl" %icrosoft@
/perations %anager? management pac0.
The following transactions are some of the most commonE
TestCsAddress/oo&Service: Tests the a!ilit" of a user to access the ,ddress
8oo0 #erver. 6or exampleE
(est-CsAressBoo1Service -(ar"etF+n atl-cs-001/contoso/co)
-2serCreential contoso\%o% -2serSipAress 3sip4%o%5contoso/co)3
TestCsA0Con!erence: Tests the a!ilit" of a pair of users to ta0e part in an
audioQvideo >,Q3? conference. 6or exampleE
(est-CsA6Con&erence -(ar"etF+n atl-cs-001/lit7areinc/co)
TestCsClientAuth: -etermines whether a user can log on to L"nc #erver !" using
a certificate download from the certificate provisioning service. 6or exampleE
8cre1 9 :et-Creential 3lit7areinc\1en)-er3
(est-CsClientAuth -(ar"etF+n atl-cs-001/lit7areinc/co) -2serSipAress
3sip41en)-er5lit7areinc/co)3 -2serCreential 8cre1
TestCsCo)puter: 3erifies the status of the L"nc #erver services running on the
local computer. This cmdlet also verifies that the appropriate L"nc #erver ,ctive
-irector" groups have !een added to the corresponding local groups on the
computer and that the necessar" computer firewall ports have !een opened. 6or
exampleE
(est-CsCo)puter -6er%ose
Microsoft Lync Server 2010 Resource Kit Archiving and Monitoring Page 1'
TestCs(ial*nCon!erencing: 'hec0s to see if a user can ta0e part in a dial-in
conferencing session. 6or exampleE
(est-CsDialInCon&erencin" -(ar"etF+n atl-cs-001/lit7areinc/co)
TestCs1ederatedPartner: 3erifies the a!ilit" to connect to a federated domain.
(est-CsFeerate!artner -(ar"etF+n accessprox-/lit7areinc/co) -Do)ain
&a%ri1a)/co)
TestCs$roup*M: Tests the a!ilit" of users to participate in a group I%
conversation. 6or exampleE
(est-Cs:roupI) -(ar"etF+n atl-cs-001/lit7areinc/co)
TestCs*M: Tests the a!ilit" of two users to exchange instant messages. 6or
exampleE
(est-CsI) -(ar"etF+n atl-cs-001/lit7areinc/co)
TestCsP2PA0: Tests the a!ilit" of a pair of users to conduct a peer-to-peer ,Q3
call. 6or exampleE
8cre1 9 :et-Creential 3lit7areinc\pilar3
8cre2 9 :et-Creential 3lit7areinc\1en)-er3
(est-Cs!2!A6 -(ar"etF+n atl-cs-001/lit7areinc/co) -SenerSipAress
3sip4pilar5lit7areinc/co)3 -SenerCreential 8cre1 -;eceiverSipAress
3sip41en)-er5lit7areinc/co)3 -;eceiverCreential 8cre2
TestCsPhone/ootstrap: 3erifies that a user can log on to L"nc #erver !" using a
device running %icrosoft@ L"ncA )*+* 1hone .dition. 6or exampleE
(est-Cs!honeBootstrap -!honeOrExt 3*1#2<<<<011=3 -!in 30>123
TestCsPresence: Tests the a!ilit" of a user to log on to L"nc #erver, pu!lish his or
her presence information, and then su!scri!e to another userFs presence information.
6or exampleE
(est-Cs!resence -(ar"etF+n atl-cs-001/lit7areinc/co)
TestCsRegistration: Tests the a!ilit" of a user to log on to L"nc #erver. 6or
exampleE
(est-Cs;e"istration -(ar"etF+n atl-cs-001/lit7areinc/co)
#ervice-impacting events and performance counters are categori7ed as either 5e" 9ealth
Indicators >59I? or non-59Is. 59Is result in medium priorit" alerts in #"stem 'enter
/perations %anager and are auto-resolved if the component returns to health. $on-59Is
generate information alerts in /perations %anager and re=uire manual resolution.
Call Reliabilit! +onitoring
'all relia!ilit" monitoring is stored as '-R data, and failures are classified as expected or
unexpected !ased on the ms-diagnostic header.
The /perations %anager management pac0 specifies that alerts will !e generated !ased on
higher than expected failure rates.
+edia 4ualit! +onitoring
%edia =ualit" monitoring 2o. data and calls are classified as good or poor =ualit" !ased
on the following metricsE
Microsoft Lync Server 2010 Resource Kit Archiving and Monitoring Page 1-
$etwor0 degradation
Round-trip time
1ac0et loss
;itter
9ealing
6or details, see the section 'onversational %/#, later in this chapter.
/perations %anager alerts are raised for server infrastructure components >such as
%ediation #ervers? and for networ0 lin0s and are generated !ased on higher than expected
poor =ualit" call rates.
$ervice Health +onitoring
#ervice health monitoring provides a holistic view of the end-to-end service, !ased on
automatic s"nthetic transactions that ensure that each component is operating and
reporting as it should.
$ew features in health monitoring, such as automatic discover", have ena!led more
capa!ilities for more ro!ust discover"B the /perations %anager management pac0 uses the
'entral %anagement #erver to determine what computers and services are running in the
topolog" that need to !e automaticall" monitored. This eliminates the need for
administrators to do a lot of manual configuration. The management pac0 has numerous
views on this data, including a glo!al site-level view, pool-level view, and server-level view
of service health.
#ervice-health alerts are now categori7ed into the following three alert t"pesE
3igh: $otifies "ou that a service outage has !een detected and a feature can no
longer !e used. 9igh alerts are verified exclusivel" !" s"nthetic transactions and
should !e resolved immediatel".
Mediu): $otifies "ou that either high availa!ilit" is at ris0 !ut features are still
availa!le, a high volume of users are experiencing issues !ut not all users, or a
component has detected that something is !ro0en. %edium alerts are verified !"
component alerts, call relia!ilit" alerts, and media =ualit" alerts and should !e
resolved !" the next !usiness da".
+ther: $otifies "ou a!out an issue that impacts a relativel" small set of users, for
example, RToo man" people are su!scri!ing to see the presence of a './R or RUser
moves failed for a few users. These alerts should !e resolved after high-alert and
medium-alert issues.
Call 4ualit!
The factors that determine call =ualit" are !ased on the following mean opinion score >%/#?
valuesE
Listening %/#
#ending %/#
$etwor0 %/#
Microsoft Lync Server 2010 Resource Kit Archiving and Monitoring Page 26
'onversational %/#
*istening +3$
Listening %/# is a prediction of the wide!and %/# Listening 2ualit" >%/#-L2? of the audio
stream that is pla"ed to the user. This value ta0es into consideration the audio fidelit",
audio distortion, and speech and noise levels. 6rom this data, it predicts how a large group
of users would rate the =ualit" of the audio.
Listening %/# varies depending on the following factorsE
The t"pe of codec >wide!and or narrow!and?
The characteristics of the microphone the spea0er is using
,n" transcoding or mixing that occurs
1ac0et loss and pac0et loss concealment
The speech level of and !ac0ground noise from the spea0er
-ue to the multiple factors that influence this value, it is most useful to view Listening %/#
statisticall" from a sampling of calls rather than for a single call.
$ending +3$
#ending %/# is a prediction of the wide!and %/#-L2 of the audio stream prior to !eing
encoded and sent to the networ0. This value ta0es into consideration the speech and noise
levels of the user along with an" distortions. 6rom this data, it predicts how a large group of
users would rate the audio =ualit" the" hear.
#ending %/# varies depending on the followingE
The microphone that the spea0er sending the audio is using
The speech level of and !ac0ground noise from the spea0er
-ue to there !eing more than one factor that influences this value, it is most useful to view
a report showing trending of #ending %/# from a sampling of calls rather than for a single
call.
Networ& +3$
Li0e Listening %/#, $etwor0 %/# is a prediction of the wide!and %/#-L2 score for the
audio stream that is pla"ed to the user. This value ta0es into consideration networ0 factors
such as the codec used, amount of pac0et loss, amount of pac0et reorder, amount of pac0et
errors, and amount of Gitter.
The difference !etween $etwor0 %/# and Listening %/# is that $etwor0 %/# considers
onl" the impact of the networ0 on the call =ualit", whereas Listening %/# also considers the
pa"load >for example, speech level and noise level?. This ma0es $etwor0 %/# useful for
identif"ing networ0 conditions that impact the audio =ualit".
6or each codec, there is a maximum possi!le $etwor0 %/# that represents the !est
possi!le %/#-L2 for a call scenario. The following ta!le shows the codec t"picall" used for
each scenario and the corresponding maximum $etwor0 %/#. 8" understanding the
maximum $etwor0 %/#, "ou can interpret the impact of degradation. 6or example, a
degradation of *.J will provide a significantl" different experience when using RT,udio
ide!and than when using RT,udio $arrow!and. >ith narrow!and, it is li0el" the call is
Microsoft Lync Server 2010 Resource Kit Archiving and Monitoring Page 21
extremel" difficult to understand. ith wide!and, there is li0el" to !e a noticea!le loss of
=ualit", !ut the call is li0el" to !e understanda!le?.
Table )( T!%ical Codecs and +a1i"u" Networ& +3$ for Call $cenarios
$cenario Codec +a1i"u" Networ& +3$
Microsoft5 L4nc6 "#!#7to7L4nc
"#!# call
'8$udio ,ide)and 9.!#
L4nc7to7L4nc call '8$udio 1arro()and ".:;
L4nc conference call <.="" >.="
L4nc7to7pu)lic s(itched telephone
net(or? (3S81) call
'8$udio 1arro()and ".:;
L4nc7to73S81 call or
L4nc7to7L4nc call ((ith media )4pass
ena)led)
<.=!! >.@!A
PThe maximum %/# value for the 1#T$ part of a call is ).SJ.
-ue to the differences !etween codecs, it is not possi!le to do a straight comparison
!etween $etwor0 %/# values, !ut it can !e interesting to loo0 at the average degradation
of $etwor0 %/# during the call. This allows "ou to compare calls !" showing the impact that
the networ0, devices, or !oth had on the call =ualit". The average degradation can !e
!ro0en down into how much degradation is due to networ0 Gitter and how much is due to
pac0et loss. 6or ver" small degradations, the cause of the degradation might not !e
availa!le.
Conversational +3$
'onversational %/# is a prediction of the narrow!and %/# 'onversational 2ualit" >%/#-
'2? of the audio stream that is pla"ed to the listener.
Note. Conversation M%# is narrowband. %ther M%# values are wideband.
This value ta0es into consideration the wider properties of a call, not Gust one aspect. It
includes values such as the =ualit" of the audio pla"ed and transmitted across the networ0,
the speech and noise levels for !oth audio streams >caller to callee and callee to caller?, and
echoes. It predicts how a large group of people would rate the =ualit" of the connection for
holding a conversation, in contrast to #ending %/# or Listening %/# values, which are
treated on a single-person !asis.
'onversational %/# varies depending on the same factors as Listening %/# and on the
followingE
.cho
$etwor0 dela"
-ela" due to Gitter !uffering
-ela" due to devices that carr" out encoding and decoding >such as handsets?
-ue to the multiple factors that influence this value, it is most useful to view 'onversational
%/# statisticall" from a sampling of calls rather than for a single call.
Microsoft Lync Server 2010 Resource Kit Archiving and Monitoring Page 22
Inter%reting +3$ Values
hen investigating individual reports of poor =ualit", it is important to understand that the
values reported as percentages t"picall" var" widel" !ased on the length of a call. 6or
example, a call that starts with poor =ualit" is more li0el" to cause a user to hang up and
tr" again. The effect of a user hanging up and tr"ing again is that the actual percentage
value of the issues displa"ed has a high impact. 6or example, if the call experiences five
seconds of issues in a L* second call, this e=uates to +).JT >five seconds poor =ualit"QL*
seconds total P+**?, and the user is li0el" to report this as a poor-=ualit" call. 9owever, a
call that lasts L** seconds and also has five seconds of issues, has a +.)JT rate, and the
user is less li0el" to remem!er >or even notice? the issue.
Note. 1either of these e*amples can be converted directly into M%# because M%# takes into account
many more variables.
6or this reason, extremel" short calls >calls that are less than one minute? and extremel"
long calls tend not to !e ver" revealing from a percentage perspective in terms of
highlighting issues. Long duration calls can !e useful for showing whether the issues
occurred at separate times or during one long, pro!lematic time.
6or $etwor0 %/# degradation to !e noticea!le to the end user, the value t"picall" has to !e
more than *.J >this is on a scale of + to J, not percentages?. 6or values less than *.J, it is
li0el" that the issue was a short transitor" issue that users will, in most cases, not notice.
Troubleshooting +3$ issues
To use a report to trou!leshoot %/# degradation, do the followingE
1or Listening M+S degradation: Loo0 at the values related to the device on the
receiving end and its characteristicsD for example, the transcoding value, the mixing
value, and whether there is echo.
1or Sending M+S degradation: Loo0 for causes such as !ac0ground noise from
the callee.
1or "etwor& M+S degradation: Loo0 at the values that var" !ased on the networ0
conditionsD for example, networ0 issues, pac0et loss, round-trip dela", and wireless
issues.
Note. !he Conversational M%# value analy)es end(to(end calls and is typically used for trending
rather than troubleshooting.
+onitoring $erver Re%orts
%onitoring #erver Reports can !e a resourceful measuring tool, providing the deplo"ment
team or help des0 with current, past, and future trends related to the various L"nc #erver
wor0loads. %onitoring #erver Reports includes more than L* reports, including a dash!oard
view that presents a recent trend report, either !" wee0 or !" month.
Microsoft Lync Server 2010 Resource Kit Archiving and Monitoring Page 23
6igure J is an example of a wee0l" report. ee0l" reports show six wee0s of s"stem usage
data, with more detailed diagnostics data from the past six da"s.
igure 5( 'ashboard wee&l! re%ort
Note. !he !otal failures value, in the Peer(to(peer group under Call 2iagnostics, contains data only if a
workload failed on this particular day.
In the dash!oard view, poor =ualit" areas are highlighted in "ellow and should !e
investigated. These thresholds can !e modified to "our li0ing.
The following report in figure N displa"s the total wor0loads across L"nc #erver during one
wee0. , report li0e this could help "ou interpret the total amount of peer-to-peer traffic in
"our organi7ation and the total num!er of audio and I% conversations, file transfers, and
program sharing sessions. This would !e helpful if "ou wanted to 0now how active the users
are in "our L"nc #erver deplo"ment.
Microsoft Lync Server 2010 Resource Kit Archiving and Monitoring Page 24
igure 6( Re%ort showing I+7 A8V7 %rogra" sharing7 and file transfer use
The dash!oard view includes read"-made reports ideall" suited for trending. 6or reports that
re=uire customi7ation >specific dates, sites, and so on?, a higher-level view is provided. This
view, called the %onitoring #erver Reports home page, is shown in figure C.
Microsoft Lync Server 2010 Resource Kit Archiving and Monitoring Page 2/
igure 9( +onitoring $erver Re%orts ho"e %age
Two important reports included on the %onitoring #erver Reports home page are the User
Registration Report and the 'all Relia!ilit" #ummar" Report.
/ser Registration Re%ort
The User Registration Report is a s"stem usage report that shows, !" default, the last eight
da"s and allows "ou to customi7e the date range and interval and to choose a specific pool,
if re=uired. This report is shown in figure M.
Microsoft Lync Server 2010 Resource Kit Archiving and Monitoring Page 29
igure :( /ser Registration Re%ort
Call Reliabilit! $u""ar! Re%ort
6rom the home page, "ou can access relia!ilit" and =ualit" st"le reports, including the 'all
Relia!ilit" #ummar" Report. This report provides a !rea0down of the failure rates per
modalit" and includes lin0s that allow "ou to 7oom in on individual causes.
Microsoft Lync Server 2010 Resource Kit Archiving and Monitoring Page 27
6igure S is a 'all Relia!ilit" #ummar" Report that shows that program >application? sharing
is the largest modalit" of failure in conferences !ut has the second lowest failure rate in
peer-to-peer conversations >sessions?.
igure ;( Call Reliabilit! $u""ar! Re%ort
The detailed report on the call from the preceding figure is shown in the following figure.
The data has !een !ro0en out into separate sectionsB'all Information, %edia Line, 'aller
-evice and #ignal %etrics, 'allee -evice and #ignal %etrics, 'aller .vent, 'allee .vent, and
,udio #treamBto allow a !etter !rea0down of the important data.
The 'all Information section, shown in figure +*, provides a detailed summar" of the
devices used at each endpoint of a call. /ne important value is the call durationBif the
duration is too short or too long, it can s0ew the percentages used in the calculations, as
explained previousl".
Microsoft Lync Server 2010 Resource Kit Archiving and Monitoring Page 2'
igure 1<( Call Infor"ation section
The %edia Line section is shown in figure++. It provides the location information associated
with each endpoint involved, along with the networ0 connection t"pe and lin0 speed. This
section includes an" polic" !andwidth limits applied to the call. Important values include the
connection t"pe >wired or wireless?, whether the user is inside the networ0, and whether
the user is using a virtual private networ0 >31$?.
igure 11( +edia *ine section
6igure +) shows the -evice and #ignal %etric sections. These sections provide device
characteristics for !oth the caller and callee devices, including detailed information such as
the individual driver >or firmware? versions !eing used. It is useful to compare the send
signal levels and the receive signal levels to determine how much noise is lost during the
transmission.
Microsoft Lync Server 2010 Resource Kit Archiving and Monitoring Page 2-
igure 1)( 'evice and $ignal +etrics sections
The 'lient .vent sections detail an" error feed!ac0 raised !" the device or the client. These
events allow "ou to see the t"pes of alerts that users saw in L"nc during the call,
information that can !e useful for help des0 or trou!leshooting.
6or example, help des0 can use these sections to determine if the client computer was low
on resources, such as '1UD if there was a device issue that caused an echoD or if there was
a high amount of glitching or networ0 issues that impacted call =ualit". ,n administrator
might use these sections to determine which other 2o. metrics might !e of interest.
Microsoft Lync Server 2010 Resource Kit Archiving and Monitoring Page 36
6igure +I shows the 'lient .vent section for a caller.
igure 1-( Caller Client 0vent section
The ,udio #tream sections provide details a!out the networ0. There is a section that
anal"ses the audio stream from the caller and another that details the stream from the
callee. 6igure +L shows a caller-to-callee audio stream.
The most important value in the ,udio #tream sections is the average $etwor0 %/#
degradation. This value =uantifies the impact of networ0 issues on the =ualit" of the callD
=ualit" issues include pac0et loss or Gitter. , value greater than * indicates some =ualit" loss
and re=uires further investigation to determine the nature of the issue.
Note. 2ue to rounding in the calculations, the sum of the values for Min. Net"or# MOS and Max.
Net"or# MOS degradation might not e3ual the e*pected 1etwork M%# value for the particular codec.
4For details about the e*pected 1etwork M%# values, see !able 5 in the section ,1etwork M%#,- earlier in
this chapter.6 !heir value might be off by '.'7, as shown in the following figure.
igure 1.( Audio $trea" section
Microsoft Lync Server 2010 Resource Kit Archiving and Monitoring Page 31
Re%ort Custo"i=ation
L"nc #erver supports customi7ed %onitoring #erver reports. &ou can create reports in
%icrosoft@ .xcel@ )*+* that lin0 directl" to the archiving, 2o., and '-R data!ases. &ou
can also use other tools to generate custom reports, including #2L #erver Report 8uilder,
which can create additional monitoring reports !" using #2L #erver Reporting #ervices. 6or
details a!out Report 8uilder, see :etting #tarted with Report 8uilder I.* at
http://go.microsoft.com/fwlink/?LinkId="4(5#.
To generate custo" re%orts b! using 01cel
+. /pen .xcel )*+*, and clic0 the (ata ta!.
'lic0 1ro) +ther Sources, and then clic0 1ro) S-L Server.
The -ata 'onnection i7ard opens. 'lic0 "e't.
/n the 'onnect to -ata!ase #erver page, in the Server na)e !ox, t"pe the
62-$Udata!aseVinstanceVname and appropriate authentication credentials.
Microsoft Lync Server 2010 Resource Kit Archiving and Monitoring Page 32
'lic0 "e't, and then select the data!ase "ou want to connect toE
6or '-R reporting, clic0 LcsC(R.
6or 2o. reporting, clic0 -oEMetrics.
6or archive reporting, clic0 LCSLog.
Note. !here might be additional databases listed, such as master and temp, but only the databases
listed in #tep & are specific to "ync #erver.
/n the #elect -ata!ase and Ta!le page, do one of the followingE
To connect to a single ta!le, select the Connect to a speci!ic table chec0 !ox.
To connect to multiple ta!les, clear the Connect to a speci!ic table chec0 !ox. 'lear this
chec0 !ox if data is re=uired from multiple ta!les.
Microsoft Lync Server 2010 Resource Kit Archiving and Monitoring Page 33
>/ptional? /n the #ave -ata 'onnection 6ile and 6inish page, to ensure that future updates
can !e captured after the spreadsheet report is finished and saved >!" clic0ing Refresh -ata
in .xcel?, select the Alwa#s atte)pt to use this !ile to re!resh data chec0 !ox.
'lic0 1inish.
In Select Table, select a ta!le to retrieve data from.
Microsoft Lync Server 2010 Resource Kit Archiving and Monitoring Page 34
In *)port (ata, specif" where to add the data from the ta!le in the spreadsheet.
Note. !he $roperties button provides more options for how often 4if at all6 data should be refreshed
and how the connection data should be used.
'lic0 +% to complete the wi7ard. The data from the data!ase ta!le is inserted into the
spreadsheet at the location specified, with filters ena!led for all the columns.
Using the preceding procedure, "ou can add additional ta!les from the -ata ta! !" clic0ing
.xisting 'onnections. 6igure +J shows "ou the options "ou will have.
Microsoft Lync Server 2010 Resource Kit Archiving and Monitoring Page 3/
igure 15( 01isting Connections dialog bo1
6rom the E'isting Connections dialog !ox, do one of the following.
To reproduce an" existing connections that have !een defined >which is essentiall" to
duplicate the ta!le?, clic0 Connections in this Wor&boo&.
To reproduce the connection file, which might !e to the data!ase >as in the preceding
figure, as indicated !" the data!ase icon? instead of directl" to a ta!le, clic0 Connection
!iles on this co)puter. This creates the option of a new ta!le to !e input.
8" com!ining multiple ta!les and potentiall" lin0ing to data exported from ,ctive -irector",
"ou can produce man" complex custom reports.
High2*evel Perfor"ance Counters
1erformance counters are useful for capacit" planning and trou!leshooting performance
issues. hen installing %onitor #erver, the following L"nc #erver performance counters are
added to the 1erformance %onitorE
LS:C(R Service 44 5 (ATA/ASEC(R: 'ontains the counters relevant to the '-R
data!ase performance, =ueue depth and latenc", and so on.
LS:C(R Service 46 Read: 'ontains the messages received !" the '-R service,
and provides information a!out the rate of receipt along with the num!er of lost
messages from the message =ueue.
LS:C(R Service 42 Write: 'ontains details a!out the rate of message writing to
the '-R data!ase and a!out an" failed writes.
LS:C(R Service 47 ReportError: 'ontains details a!out the num!ers of errors
that occur when tr"ing to generate '-R reports.
Microsoft Lync Server 2010 Resource Kit Archiving and Monitoring Page 39
LS:-MS 44 -oEMonitoringServer: 'ontains a summar" of the 2o. messages
!eing receivedBthe most important counters here are 2%#-**L and 2%#W**J,
which !oth relate to counts of failed messages.
LS:SipEps 44 Sip (ialogs: 'ontains information a!out actual #I1 dialogs,
specificall" around !ro0en and healed dialogs.
LS:SipEps 46 SipEps Transactions: 'ontains #I1 transaction information, such
as incoming, outgoing, active, and so on.
LS:SipEps 42 SipEps Connections: 'ontains generic connection information,
such as !"tes sent and received, and the num!er of successful and failed
connections.
LS:SipEps 47 SipEps *nco)ing Messages: 'ontains the !rea0down of
incoming messages !ased on #I1 t"pe >$/TI6&, #U8#'RI8., R.:I#T.R, and so on?,
summaries of response codes, and individual counts of response codes >for example,
response code )**?.
LS:SipEps 48 SipEps +utgoing Messages: 'ontains the !rea0down of
outgoing messages !ased on #I1 t"pe, summaries of response codes, and individual
counts of response codes.
+onitoring 'atabase $i=ing
hen "ou deplo" %onitoring #erver, "ou associate it with one or more 6ront .nd pool.
%onitoring #erver then collects data from the pool>s? "ou have associated it with.
hen "ou use the recommended hardware configuration and collocate the %onitoring
#erver and %onitoring data!ase on the same computer, a single %onitoring #erver can
serve up to )J*,*** users. If "ou have multiple pools that total less than )J*,*** users, we
recommend that "ou associate all of these pools with a single %onitoring #erver to simplif"
administration.
e also recommend having an understanding of how large the data!ase can grow. The
following example provides a formula that "ou can use to estimate the data!ase si7e. 8"
using the counters listed in L#E'-R #ervice - *+ - Read >specificall", average message si7e?
and L#E'-R #ervice - *) - rite >specificall", messages per second?, "ou can confirm
whether our estimates are accurate and then ma0e an" re=uired adGustments.
E'a)ple: 8ased on a standard user profile description, the 2o. data!ase will grow at
approximatel" +N.M 58 per user per da". To figure out how much storage "our 2o.
data!ase will need at a minimum, use the following formulaE
data!ase si7e O +N.M58 P >num!er of users? P >retention period da"s?
$u""ar!
The ,rchiving #erver and %onitoring #erver server roles support proactive trou!leshooting
!" providing detailed data capturing and reporting capa!ilities. In this chapter, we descri!ed
the wa"s that L"nc #erver improves these capa!ilities, providing "ou with the following
information a!out archivingE
,n overview of the archiving components and dependencies related to per=uisites for
configuration
Microsoft Lync Server 2010 Resource Kit Archiving and Monitoring Page 37
#caling and performance calculations to determine si7ing estimates
,n explanation of I% and we! conferencing integration
-etails a!out archiving cmdlets
,nd information a!out the following for monitoringE
#"nthetic transactions for testing and validating wor0loads
, discussion of a!out using Listening %/#, #ending %/#, $etwor0 %/#, and 'onversational
%/# to measure call =ualit"
,n overview of %onitoring #erver Reports
Additional Resources
6or more details, see the followingE
1lanning for ,rchiving at http://go.microsoft.com/fwlink/?LinkId=20(0(5
%icrosoft L"nc #erver )*+* ,rchiving -eplo"ment :uide at http://go.microsoft.com/fwlink/?
LinkId=22"2(0
1lanning for %onitoring at http://go.microsoft.com/fwlink/?LinkId=20$5#
%icrosoft L"nc #erver )*+* %onitoring -eplo"ment :uide at
http://go.microsoft.com/fwlink/?LinkId= 22"2("
Microsoft Lync Server 2010 Resource Kit Archiving and Monitoring Page 3'