The Microsoft Lync Server 2010\2013 Voice component diagnostics package for Windows Server 2008 R2 collects a comprehensive set of information for troubleshooting Lync Server 2010\2013 issues.
This article describes information that may be collected from a computer that is running Microsoft Office Communications Server 2007 R2, Microsoft Lync Server 2010, or Microsoft Lync Server 2013. The following information may be collected by the Lync Server 2010\2013 Voice component diagnostics package.
Note Output file names are prefixed by using the name of the item for which their output was generated. In ouput file names, the placeholder <prefix> represents the name of the item for which output is generated.
Lync Server event logs
Event log – Application – text, .csv, and .evt/.evtx formats
Event log – System – text, .csv, and .evt/.evtx formats
Event log – Lync Server – text, .csv, and .evt/evtx formats
Lync Server topology
Get-CsTopology -AsXML cmdlet output
Information about the operating system and whether the destination computer is a virtual machine
Reports virtualization status of target VM
Reports virtualization status of target VM
Basic IP networking configuration information, such as TCP/IP registry key, ipconfig, arp, netstat, nbtstat, and netsh output
Output from the netdiag.exe utility
Firewall information from netsh firewall
Netsh information for IPv4
Netsh information for IPv6
Netsh information for TCP global and chimney
Lync Server voice configuration
Lync Server user information
Lync Server service
Lync Server tracing file
ync Server DHCPUtil output
Installed updates and hotfixes
Server Role information
Copy of ServerManager.log from Windows\Logs folder
Process and threads information through pstat.exe
Fibre Channel information through FCInfo.exe utility
Volume Shadow Copy Service (VSS) information
Active Directory and policy information
Resultant Set of Policy (RSoP) information through gpresult.exe
Security templates that are currently cached on the system
Functional Level and Group Membership information
Checks that are performed by the Lync Server Core Component Pakcage
Check whether there is a newer CU.
Should check whether the latest CU is applied. The ideal kind of rule is the one that identifies a specific issue and can state definitely that a specific CU fixes the issue.
To reduce the risk of unauthorized exposure of sensitive information, Microsoft has released a nonsecurity update (KB 2661254) for all supported versions of Microsoft Windows. This update will block cryptographic keys that are less than 1024 bits long. This update does not apply to Windows 8 Release Preview or Windows Server 2012 Release Candidate because these operating systems already include the functionality to block the use of weakRSA keys that are less than 1024 bits long. For more information, go to the following Microsoft website:
External users can logon without entering credentials
External users can connect via the Edge Serve without entering credentials (username/password) when the external Edge Server certificate was a wildcard certificate. Or on the internal Edge Server interface customer was using a certificate with SAN.
The EncryptionLevel feature for Client Media Configuration is set to RequireEncryption but for media bypass to work in a voice environment with non-TLS GWs/PBX/SIP-Trunks this flag needs to be set to SupportEncryption. When set to RequireEncryption the media bypass fails and the media traffic will flow via Mediation Server IP.
2761579 Lync Server 2010 Media Bypass fails when CsMedia Encryption Level flag is set to RequireEncryption
Lync Certificate may expire in 21 days or less
Expired or soon to expire certificates in 21 Days will be detected
Lync Certificate may expire in 7 days or less
Expired or soon to expire certificates in 7 Days will be detected
Windows Server is missing KB975954 to prevent possible deadlocks in Lync
All the network interface IP addresses for the Mediation server are from the same subnets or there is only 1 NIC. Make sure that the server has two network interfaces that are configured with IP addresses from different subnets. See the following KB article for more information.
2758662 Lync Server 2010 Mediation Server single network adapter issues
Edge server network interfaces are not properly configured
All the network interface IP addresses for the edge server are from the same subnets or there is only 1 NIC. Make sure that the server has two network interfaces that are configured with IP addresses from different subnets. See the following KB article for more information.
2757916 Lync Server 2010 edge server network configuration issue
Lync Windows Store App cannot sign-in to Lync Server 2010 pool with CU7 or to Lync Server 2013 pool
Lync Windows Store App (aka Lync MX) cannot sign-in to Lync Server 2010 pool with CU7 (October 2012 Updates) or to Lync Server 2013 pool as internal user.
Same issue can be seen as an external user as well if the certificate assigned to Lync Access Edge service has been enrolled without a CDP which points to a HTTP location
Microsoft Lync Server 2013, Microsoft Lync Server 2010 Standard Edition, Microsoft Lync Server 2010 Enterprise Edition, Microsoft Office Communications Server 2007 R2 Standard Edition, Microsoft Office Communications Server 2007 R2 Enterprise Edition