[SDP3][3db601d0-f012-4959-8fc5-b0c9f9806a6a] CTS Reports Diagnostic Package

Information Collected

Boot Information

Devices and drivers

Driver Verifier Information

Event Logs - Failover Cluster

Event Logs - General

Event Logs - Networking

FailoverCluster Feature

File Version Information (Chksym)

General Information

General Performance Information

General Registry Data Collection

Hyper-V role

Memory Dump Information and Files

Print Drivers and Printers information

Server manager and server roles information

Storage Information

In addition to collecting the information that is described earlier, this diagnostic package can detect one or more of the following symptoms:

• One or more processes are using a high number of handles
• Possible Kernel Memory performance related problem
• This system is currently running under low System PTEs
• This system is currently running under low Virtual Memory
• Memory Dump Related Issues
• Print Drivers and Printers information
• Detect Advanced Format Drives
• Detect Native 4K drives on the system
• Check if KB982018 is not installed or files are outdated
• Check if cluster groups are in Offline or Failed state
• Check for errors gathering cluster information via Get-ClusterNode cmdlet
• Check if the state of one or more cluster nodes is down or paused
• Check if Cluster service is not running or offline
• Check if there are virtual machines using High CPU utilization
• Check if Dynamic Memory is enabled on one or more Virtual Machines with old Integration Services
• Check for version mismatches of Integration Services
• Check if one or more Virtual Machines have virtual hard drives located on an disk with Advanced Format Drives (512e disks)
• Check for Active Directory replication failures
• Check if has been too long since this domain controller replicated
• Active Directory replication is failing for one or more partitions: Status -2146893022 The target principal name is incorrect
• Active Directory replication is failing for one or more partitions: Status 1127 - While accessing the hard disk, a disk operation failed even after retries.
• Active Directory replication is failing for one or more partitions: Status 1256 - The remote system is not available
• Active Directory replication is failing for one or more partitions: Status 1396 - Logon Failure: The target account name is incorrect
• Active Directory replication is failing for one or more partitions: Status 1722 - The RPC server is unavailable
• Active Directory replication is failing for one or more partitions: Status 1753 - There are no more endpoints available from the endpoint mapper
• Active Directory replication is failing for one or more partitions: Status 5 - Access is denied
• Active Directory replication is failing for one or more partitions: Status 8452 - The naming context is in the process of being removed...
• Active Directory replication is failing for one or more partitions: Status 8453 - Replication Access Was Denied
• Active Directory replication is failing for one or more partitions: Status 8524 - The DSA operation is unable to proceed because of a DNS lookup failure
• Detect Lingering objects on domain controllers
• Active Directory replication is failing for one or more partitions: Status 8451 - The replication operation encountered a database error
• Active Directory replication is failing for one or more partitions: Status 1818 - The remote procedure call was cancelled
• Active Directory replication is failing for one or more partitions: Status 8456 or 8457: The source or destination server is currently rejecting replication requests
• Active Directory replication is failing for one or more partitions with status 8589
• Active Directory replication is failing for one or more partitions with status 8333 - Directory Object not Found
• Active Directory replication is failing for one or more partitions: Status 8446 - The replication operation failed to allocate memory
• Active Directory replication is failing for one or more partitions: Status 8240 - There is no such object on the server
• Active Directory replication is failing for one or more partitions: Status 1783 - The stub received bad data
• Check for potentially risky audit failure settings (CrashOnAuditFail)
• Check for a possible STOP error caused by audit failure
• Check for High CPU usage by Local Security Authority Subsystem Service (LSASS)
• Check if either SYSVOL and/or NETLOGON shares are missing on domain controller
• Check for domain controller missing Rid Set reference attributes in Active Directory
• Check if DC is pointing to itself for DNS exclusively
• Check for USN Rollback
• Check state of Intersite Messaging service.
• Check if DFSR UpdateWorkerThreadCount setting is lower than 64
• Detect if IPv6 was disabled on a domain controller
• Detect Win32time configuration for time skew
• Detect MaxConcurrentApi NTLM bottlenecks or delays
• Detect Certificates with Weak RSA Keys
• Check if the Cluster Name Object (CNO) exists and it is enabled in Active Directory
• Check if Cluster Shared Volumes is configured to Redirected access
• Check if Cluster Shared Volumes is configured for Local Access
• Check if Cluster Shared Volumes is configured to Maintenance Mode
• Check if Cluster Shared Volumes is configured to Network Access
• Check for third party virtualization solution from Xsigo
• Check for LmCompatibilityLevel setting
• Check firewall rules on cluster nodes with IPv6 enabled
• Check if PMTU has been disabled on machine
• Check for unexpected TcpIp registry settings (KB 967224)
• Check if Opportunistic Locking has been disabled
• Check for excessive number of 6to4 adapters which may result in decreased startup and logon performance
• Check if Tunnel.sys driver is missing a Windows Server 2008 R2 Server Core installation option
• Check if InfoCacheLevel setting is configured to enable caching for all files and folders
• Checks if Appsense EM 8.1 is installed on machine
• Check for large number of Inactive Terminal Services ports
• Checking if Registry Size Limit setting is present on the system
• Check PoolUsageMaximum Setting
• Checking for shared PST files
• Check for McAfee Endpoint Encryption version which may cause slow boot issues
• Check for terminal services licensing binary versions for Windows Server 2003
• Check for specific version of SEP that may cause handle leak
• Check RPC settings for allowing unauthenticated sessions
• Check for Performance counters to see if there is an issue with NTFS metafile cache memory consumption
• Check for ProcessorAffinityMask setting for multiprocessor Windows Server 2003 machines
• Check for ClearPageFileAtShutdown setting which may cause slow shutdown
• Check for NMICrashDump setting on HP ProLiant DL385 G5
• Check for older version of MPIO.SYS on Windows Server 2003 with Multipathing solution installed
• Check for Broadcom Advanced Server Program driver information
• Check if Users group have permissions under HKCR\CLSID
• Check HeapDecommitFreeBlockThreshold registry value
• Detect Netapi32.dll version
• Detect if fail to install due to an invalid Registry entry for Autoruns
• Check for missing registry keys that can cause issues with Component Services
• Check for possible startup performance problems on Hyper-V Servers due to a large number of orphaned registry keys
• Check Xeon Processor 5500 Series processor erratum related with Hyper-V (KB 975530)
• Check if update KB2263829 is installed on Hyper-V on Windows Server 2008 R2 Service Pack 1 systems
• Check for event ID 21203 or 21125 in the Microsoft-Windows-Hyper-V-High-Availability/Admin event log over the past 15 days.
• Check for Symantec Endpoint Protection MR1/MR2
• Check for unsupported versions of Windows Vista or Windows Server 2008
• Check if DEP and PAE is enabled on a 32-bit system
• Check if Telnet service is running under System account
• Check the value of 'SystemPages' in Memory Management registry key
• Check for Evaluation Media
• Check if Page Heap is enabled to one or more processes
• Check if driver verifier has been enabled for at least one driver.
• Check for ephemeral port usage

References

For more information about the Microsoft Automated Troubleshooting Services and about the Support Diagnostics Platform, please open the following Microsoft Knowledge Base article:


2598970 Information about Microsoft Automated Troubleshooting Services and Support Diagnostic Platform