You need to identify the cause of the issue

You administer a Microsoft Lync Server 2010 Standard Edition server in your network environment.
You deploy a Microsoft Lync Server 2013 Standard Edition server. You want to migrate users from
Lync Server 2010 to Lync Server 2013. You migrate a test account from Lync Server 2010 to Lync
Server 2013. You start the Lync 2013 client on one of your test computers and start testing various
modalities. During testing, you decide to test the Meet Now functionality in Lync 2013 client. Meet
Now starts a conference and fails to connect. You start Clslogging.exe. You generate a log that
includes the following information:

You need to identify the cause of the issue. What should you do first?

You administer a Microsoft Lync Server 2010 Standard Edition server in your network environment.
You deploy a Microsoft Lync Server 2013 Standard Edition server. You want to migrate users from
Lync Server 2010 to Lync Server 2013. You migrate a test account from Lync Server 2010 to Lync
Server 2013. You start the Lync 2013 client on one of your test computers and start testing various
modalities. During testing, you decide to test the Meet Now functionality in Lync 2013 client. Meet
Now starts a conference and fails to connect. You start Clslogging.exe. You generate a log that
includes the following information:

You need to identify the cause of the issue. What should you do first?

A.
Open another log file from the Lync client in Snooper.

B.
Right-click the error message and select Go to nearest entry in trace viewer.

C.
Start WireShark and perform the Meet Now test again.

D.
Click Show Call Flow Window.

Explanation:



Leave a Reply 0

Your email address will not be published. Required fields are marked *