SDP [a957734a-7d4f-41c4-85f4-5c78dd7c636b]Description of the Lync Server 2010\2013 Instant Messaging and Presence component diagnostics package

Article translations Article translations
Article ID: 2778271 - View products that this article applies to.
Expand all | Collapse all

Summary

The Lync Server 2010\2013Instant Messaging and Presence Component Diagnostics Package for Windows Server 2008 R2 is used to collect a comprehensive set of information for troubleshooting Lync Server 2010\2013 issues. 

Note Output file names are prefixed by using the name of the item for which their output was generated. In output file names, the placeholder <prefix> represents the name of the item for which output is generated.

More information

This article describes information that may be collected from a computer that is running either Office Communications Server 2007 R2, Lync Server 2010, or Lync Server 2013. The following information may be collected by the Lync Server 2010\2013 Instant Messaging and Presence Component Diagnostics Package for Windows Server 2008 R2.  

Information collected

Lync Server event logs
Collapse this tableExpand this table
DescriptionFile name
Event log – Application – text, .csv, and .evt/.evtx formats <prefix>_evt_Application.*
Event log – System – text, .csv, and .evt/.evtx formats<prefix>_evt_System.*
Event log – Lync Server – text, .csv, and .evt/.evtx formats<prefix>_evt_LyncServer.*
Lync Server topology
Collapse this tableExpand this table
DescriptionFile name
Get-CsTopology -AsXML cmdlet output<prefix>_lync_topology.xml
Lync Server DHCPUtil output
Collapse this tableExpand this table
DescriptionFile name
DHCPUtil -EmulateClient<prefix>_DHCPUtil_EmulateClient.txt
Lync Server tracing file
Collapse this tableExpand this table
DescriptionFile name
Tracing files{prefix}_{tracing filename}_.etl

Information about the operating system and whether the destination computer is a virtual machine (VM)
Collapse this tableExpand this table
DescriptionFile name
Reports virtualization status of target VM<prefix>_Virtualization.htm
Reports virtualization status of target VM<prefix>_Virtualization.TXT
Networking information
Collapse this tableExpand this table
DescriptionFile name
Basic IP networking configuration information, such as TCP/IP registry key,
ipconfig, arp, netstat, nbtstat, and netsh output
<prefix>_TcpIp-Info.txt
Output from the netdiag.exe utility<prefix>_netdiag.txt
Firewall information from netsh firewall<prefix>_FirewallConfig.txt
Netsh information for IPv4<prefix>_TCPIP-Netsh-IPv4.txt
Netsh information for IPv6<prefix>_TCPIP-Netsh-IPv6.txt
Netsh information for TCP global and chimney<prefix>_TCPIP-Netsh-TCP.txt
Other
Collapse this tableExpand this table
DescriptionFile name
Installed updates and hotfixes<prefix>_Hotfixes.*
System information<prefix>_sym_*.*
Server Role information<prefix>_ServerManagerCmdQuery.*
Copy of ServerManager.log from Windows\Logs folder<prefix>_ServerManager.log
Process and threads information through pstat.exe<prefix>_PSTAT.txt
Storage/disk information
Collapse this tableExpand this table
DescriptionFile name
Fibre Channel Information through FCInfo.exe utility<prefix>_FCInfo.txt
Volume Shadow Copy Service (VSS) information<prefix>_VSSAdmin.txt
Active Directory and policy information
Collapse this tableExpand this table
DescriptionFile name
Resultant Setof Policy (RSoP) information through gpresult.exe<prefix>_GPResult.*
Security templates currently cached on the system<prefix>_AppliedSecTempl.txt
Functional Level and Group Membership information<prefix>_DSMisc.txt
Checks that are performed by the Lync Server Core Component Diagnostics Package
Collapse this tableExpand this table
NameDescription
Check whether there is a newer CU.Should check whether the latest CU is applied. The ideal kind of rule identifies a specific issue and can state definitely that a particular CU resolves the issue. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2493736 Updates for Lync Server 2010
Check weak RSA key certificatesTo reduce the risk of unauthorized exposure of sensitive information, Microsoft released a nonsecurity update (KB 2661254) for all supported versions of Microsoft Windows. This update blocks cryptographic keys that are less than 1,024 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 weak RSA keys that are less than 1,024 bits long. For more information, go to the following Microsoft website:
Microsoft Security Advisory (2661254)
External users can logon without entering credentialsExternal 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.
Wildcard Certificate Support
ProxyFqdn for CS Allowed Domain is not correctly set up for Lync Mobility push notificationsThe ProxyFqdn flag is not set correctly. Because this flag is not set to sipfed.online.lync.com, there may be routing issues for push notification delivery. Verify that there is an entry for push.lync.com for the Get-CsAllowedDomain cmdlet, and then verify that Proxy FQDN for push.lync.com is set to sipfed.online.lync.com. See the KB article for more information.
2743802 Lync Server 2010 Mobility Allowed Domain value causes push notifications to fail
ProxyFqdn for CS Hosting Provider is not configured correctly for successful Lync Mobility The ProxyFQDN flag is not set correctly. Because of this, the Edge server won't be able to send the push notification to Lync Online on its way to the Push Notification Clearing House (PNCH). Verify that this setting is correctly configured. If no entry is found, there may be an R2 edge server in the environment; in that case, no CS Hosting Provider is required. See the KB article for more information.

2743783 Lync Server 2010 Mobility hosting provider ProxyFqdn value causes push notifications to fail
EnableMicrosoftPushNotificationService is not enabled for Lync Mobility Push NotificationsThe Lync Server 2010 configuration for EnableMicrosoftPushNotificationService is set to False. Because of this, Windows Phone devices won't be able to receive Push Notifications. If you have mobility configured in the Lync environment and your enterprise has Windows Phone users, then this flag has to be set to True.

2757132 Lync 2010 mobile client for Windows phone cannot receive push notification
EnableApplePushNotificationService is not enabled for Lync Mobility Push NotificationsThe Lync Server 2010 configuration for EnableApplePushNotificationService is set to False. Because of this, iOS devices won't be able to receive the Push Notifications. If you have configured mobility in the Lync environment and the enterprise has iOS users, then this flag has to be set to True.

2757125 Lync 2010 mobile client for iOS devices cannot receive push notification
PushNotificationProxyUri is not correctly set up for Lync Mobility push notificationsThe PushNotificationProxyUri flag value for Get-csmcxconfiguration is not configured to "sip:push@push.lync.com". Because the URI is not correct, push notifications will be rejected by the Push Notification Clearing House (PNCH). If mobility is set up in the Lync environment, change the PushNotificationProxyUri to sip:push@push.lync.com

2760645 Lync Server 2010 Mobility PushNotificationProxyUri value causes push notifications to fail
Kerberos account is out of syncThe Kerberos Account is out of sync. This may cause authentication prompts for users.
Create a Kerberos Authentication Account
Lync certificate may expire in 21 days or lessExpired or soon to expire certificates in 21 Days will be detected
Lync Certificate may expire in 7 days or lessExpired or soon to expire certificates in 7 Days will be detected
Windows Server is missing KB975954 to prevent possible deadlocks in LyncYou are missing Windows Update KB975954. This .NET Framework update addresses a known issue that leads to poor performance on Lync Servers. When this issue occurs you may see an Access Violation in several Lync processes or you may see a hang in some Lync processes. Apply the .NET Framework hotfix from KB975954. See the Knowledge Base article for more information on how to address this issue.

975954 FIX: When you run a .NET Framework 2.0-based application, a System.AccessViolationException exception occurs, or a dead-lock occurs on two threads in an application domain
Mediation server network interfaces are not properly configuredAll 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 configuredAll 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 poolLync 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

Properties

Article ID: 2778271 - Last Review: January 22, 2013 - Revision: 2.3
Applies to
  • Microsoft Lync Server 2013
  • Microsoft Lync Server 2010 Enterprise Edition
  • Microsoft Lync Server 2010 Standard Edition
  • Microsoft Office Communications Server 2007 R2 Enterprise Edition
  • Microsoft Office Communications Server 2007 R2 Standard Edition
Keywords: 
kbsurveynew KB2778271

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com