SDP [71eeb57a-b16d-4b6b-bb3d-5c03e7cfec7d]Description of the Lync Server 2010\2013 Core component diagnostics package

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

On This Page

Summary

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

More information

This article describes information that the Lync Serve 2010\2013 Core component diagnostics package may collect from a computer that is running Microsoft Office Communications Server 2007 R2, Lync Server 2010, or Lync Server 2013. 

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.

Information that is 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 configuration
Collapse this tableExpand this table
DescriptionFile name
Get-CsConfiguarion<prefix>_LyncServer_CsConfiguration.zip
Lync Server tracing file
Collapse this tableExpand this table
DescriptionFile name
Tracing files{prefix}_{tracing filename}_.etl
Lync Server Response Group information
Collapse this tableExpand this table
DescriptionFile name
Response Group information{prefix}_ LyncServer_RGS _.txt
Information about user rights assignments on the destination computer
Collapse this tableExpand this table
DescriptionFile name
Local User Rights Assignments<prefix>_UserRights.txt
Information about the operating system and whether the destination computer is a virtual machine
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
Autorun information

Note For more information about the Autorun utility, go to the following TechNet website:
http://technet.microsoft.com/en-us/sysinternals/bb963902.aspx
Collapse this tableExpand this table
DescriptionFile name
Autorun information in .htm format<prefix>_Autoruns.htm
Autorun information in .xml format<prefix>_Autoruns.xml

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 Set of 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
Detection of and warning about network adapter teaming on a server.This warning indicates that network adapter teaming is enabled on the Lync server that is being analyzed. Although network adapter teaming is generally not an issue, you should make sure that teaming is configured correctly with the most recent network adapter teaming drivers available. For more information, click the following article number to view the article in the Microsoft Knowledge Base:  
278431  Using teaming adapters with network load balancing may cause network problems  
Check whether there is a newer CU.This should check whether the latest CU is applied. The ideal 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 certificates.To 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 will block 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)
Start the service if the Detect Lync Server service is not running.Services that are required for the Lync server are not running on the computer. Use the Start-Service cmdlet to start the services that are needed and are not started on this computer. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2747217 Administer Lync Server 2010 services from a remote Windows-based computer 
Check the Lync Server Evaluation version.The Evaluation version of Lync is installed on this server. Lync services will no longer start after the evaluation period ends. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2468019 Lync Server 2010 evaluation period has expired
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
Lync user move issueThe problem can occur when you have 2 (or more) FE Server configured with a HLB and the registry value
HKEY_LOCAL_MACHINE\ SOFTWARE\Policies\ Microsoft\Windows NT\RPC
RestrictRemoteClients is set to '2'
To solve the issue change the value for RestrictRemoteClients
RestrictRemoteClients
CMS replication fails when firewall is disabledThe problem happens because the Windows Firewall Service is stopped/disabled but the filter drivers are still active. It is recommended to have firewall service running on all the Lync Servers, therefore, the solution is to start/enable the firewall and open required ports. Running Enable-CsComputer opens the required ports based on the server configuration.
Lync Edge server with multiple external NICs must have default gateway set on all NICsIf only one external NIC default gateway was set, the warning will be fired, resolution is to set the default gateway on ALL external Edge interfaces.
Set Up Network Interfaces for Edge Servers
Lync replication status is not up to dateThe CMS Replication Status is not up to date, meaning that this server may not have a copy of the most recent Lync configuration.
2667713 Introduction to the Lync Server 2010 CMS
PowerShell synthetic   transactions fail when there is more than one server in the Lync poolAdvisor detected that Windows Firewall is enabled on this server, and that there is no exception for Windows PowerShell. If you have more than one Lync server is in the pool, synthetic transactions will fail. See the following KB article for more information.

2751720 Lync Server 2010 PowerShell synthetic transactions fail
Enable-CsAdForest  failsHappens when you have locked down AD environment. Due to this required permissions are missing on Deleted Objects container.
Preparing a Locked-Down Active Directory Domain Services
Lync Server 2010 web service application pools issueBy default, the .NET Framework Version setting is v4.0 for the Lync Server 2010 application pools when you install Lync Server 2010 on a Windows Server 2012-based computer. However, the Lync Server 2010 web services use the Microsoft .NET Framework 2.0Preparing a Locked-Down Active Directory Domain Services
2777747 404.17 - Not Found error message when you try to connect to a Lync Server 2010 web service
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 issue
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
Routing errors occur whenever Front End servers are dual-homed with Primary and PSTN NICsWhen a Front End/Mediation server is configured with both a pool-facing Primary NIC (for internal communication) and an external-facing PSTN NIC (for Gateway/SIP provider communication), routing errors can occur - especially involving Lync mobile clients.

Properties

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

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