###BeginCaseStudy###
Testlet 5
Contoso Ltd. Case B
Overview
General Overview
Contoso, Ltd. is an international manufacturing company that has 30,000 users.
Contoso has the following departments: sales, research, marketing, human resources, executive, manufacturing, and legal. The sales department has 2,000 users.
All of the users in the sales department are located in the United States. The research department has 3,000 users. All of the users in the research department are
located in Europe.
Physical Locations
Existing Environment
Lync Server Infrastructure
Contoso has a Lync Server 2010 infrastructure that only uses internal instant messaging (IM) and presence, The infrastructure contains a single Enterprise Edition
Front End pool that services all of the users.
Contoso uses a SIP domain of contoso.com for all of the users.
Client computers have either Microsoft Office Communicator 2007 R2 installed or Microsoft Lync 2010 installed.
Before deploying Lync Server 2013 and migrating the users to Lync Server 2013, you implement a small pilot project to test the functionality of Lync Server 2013.
Problem Statements
The users in the pilot report that occasionally, they cannot sign in to Lync 2013.
Requirements
Business Goals
Contoso plans to upgrade to Lync Server 2013 during the next six months. Contoso must deploy all of the Lync Server conferencing and edge services. Contoso
must also configure federation with its parent company, which is named Proseware, Inc. Proseware is located in Europe and has an Office Communication Server
2007 R2 infrastructure.
Contoso must minimize hardware and software purchasing costs, while guaranteeing performance levels for all Lync Server 2013 workloads.
Planned Changes
Contoso plans to implement the following workloads in the Lync Server 2013 deployment:
Federation
Dial-in conferencing
External user access

Audio, video, and web conferencing
The ability to host Lync meetings that have external participants
The FQDNs of the edge services will be configured as shown in the following table.

Technical Requirements
Contoso identifies the following technical requirements for the planned deployment:
Only federation to Proseware must be allowed.
All of the edge services must use default ports.
WAN traffic and Internet traffic must be minimized.
All of the user contacts stored in Lync Server 2013 must be backed up. The sales department must have a dedicated dial-in conferencing number.
All other users in both the United States and Europe must use a pool of regional dial-in conferencing numbers.
If a single component fails, all Lync services must remain available without the need for manual intervention.
Performance degradation is acceptable during a component failure state.
The conversations of all the sales department users must be archived for 30 days.
The conversations of all the research department users must be archived for 90 days.
No other conversations must be archived. After the migration to Lync Server 2013, all client computers will have three months to upgrade to Lync 2013. After
three months, legacy clients must be blocked from accessing the Lync Server 2013 infrastructure.
Security Requirements
Contoso identifies the following security requirements for the planned deployment:
All Lync Server conferences must use a unique URL.
Each Internet-facing service must have one or more dedicated public IP addresses.
Only the users in the human resources department must be prevented from connecting to Lync Server remotely.

###EndCaseStudy###

You need to identify the cause of the authentication issue for the pilot users.
Which four actions should you perform in sequence?
(To answer, move the appropriate four actions from the list of actions to the answer area and arrange them in the correct order.)
Select and Place:

Answer:

Explanation:
Box 1: Update-CsClsLogging
Box 2: Run Start-CsClsLogging
Box 3: Run Stop-CsClsLogging
Box 4: Open the log file by running snooper.exe.
Note:
* From scenario:
/ Before deploying Lync Server 2013 and migrating the users to Lync Server 2013, you
implement a small pilot project to test the functionality of Lync Server 2013.
/ Problem Statements
The users in the pilot report that occasionally, they cannot sign in to Lync 2013.

* Start-CsClsLogging
Starts the specified scenario centralized logging service scenario. Centralized logging provides a way for
administrators to simultaneously enable or disable Lync Server 2013 tracing on multiple computers.
* set-CsClsRegion
Modifies an existing centralized logging configuration region. Centralized logging provides a way for
administrators to simultaneously enable or disable event tracing on multiple computers.
* Update-CsClsLogging
Updates the duration time for all active centralized logging scenarios.
* (incorrect) Search-CsClsLogging
Provides a command-line option for searching the centralized logging service log files.
* The centralized logging service (which replaces the OCSLogger and OCSTracer tools used in Microsoft
Lync Server 2010) provides a way for administrators to manage logging and tracing for all computers and
pools running Lync Server 2013. Centralized logging enables administrators to stop, start, and configure
logging for one or more pools and computers by using a single command;