Top Support Solutions for Windows Server 2012

This is a collection of the top Microsoft Support solutions for the most common issues experienced when using Windows Server 2012 R2 and Windows Server 2012 (updated quarterly). Note that some content that applies to earlier versions of Windows Server is listed, because it can be also helpful with Windows Server 2012 issues.

1. Solutions related to remote access (DirectAccess):

• Remote Access (DirectAccess, Routing and Remote Access) Overview
• Recommended hotfixes and updates for Windows Server 2012 DirectAccess
• Update adds BPA rules for DirectAccess in Windows Server 2012
• Remote Access (DirectAccess) Troubleshooting

2. Solutions related to File Replication Technologies (FRS and DFSR):

• Where’s my file? Root cause analysis of FRS and DFSR data deletion
• Understanding DFSR debug logging (Part 14: A sharing violation due to a file locked upstream between two Windows Server 2008)
• Understanding DFSR debug logging (Part 17: Replication failing because of blocked RPC ports (uses debug severity 5))
• Common DFSR Configuration Mistakes and Oversights
• DFSR Event ID 2213 is logged on Windows Server 2008 R2 and Windows Server 2012
• The performance of DFS Replication in Windows Server 2008 is slower than expected on a WAN connection, and no error message is logged in the DFS Replication log

3. Solutions related to Active Directory replication:

• Troubleshooting Active Directory Replication Problems
• Replication error 1256 The remote system is not available
• Replication error 1396 Logon Failure The target account name is incorrect
• Replication error 1722 The RPC server is unavailable
• Replication error 1753 There are no more endpoints available from the endpoint mapper
• Replication error -2146893022 The target principal name is incorrect
• Replication error 8451 The replication operation encountered a database error
• Replication error 8453 Replication access was denied
• Replication error 8524 The DSA operation is unable to proceed because of a DNS lookup failure
• Replication error 8614 The Active Directory cannot replicate with this server because the time since the last replication with this server has exceeded the tombstone lifetime

4. Solutions related to DCPromo and the installation of domain controllers:

• DCPROMO fails with error "Access is denied" if the user performing the promotion is not granted the "trusted for delegation" user right
• How to remove data in Active Directory after an unsuccessful domain controller demotion
• How to troubleshoot an "Internal error" error message during the replication phase of dcpromo
• Upgrade Domain Controllers to Windows Server 2012

5. Solutions related to Remote Desktop Services (Terminal Services) licensing:

• Windows Server 2008 RDS and Windows Server 2008 TS CAL Compatibility
• Removing Terminal Server licenses from an RDP client
• Troubleshooting Remote Desktop Licensing Issues

6. Solutions related to Bugchecks, Stop errors, and unexpected restarts:

• Windows RT, Windows 8, and Windows Server 2012 update rollup: January 2014
• "0x00000139" Stop error on a Windows Server 2012-based computer that has many TCP connections
• Stop error when you defragment a Bitlocker-encrypted drive on a Windows 8 or Windows Server 2012-based computer
• Windows Kernel event ID 41 error "The system has rebooted without cleanly shutting down first" in Windows 8, Windows Server 2012, Windows 7, or Windows Server 2008 R2
• "0x000000D1" Stop error when you open the MPIO snap-in on a computer that is running Windows Server 2008 R2 or Windows Server 2012
• "0x0000007f" Stop error when you move the mouse pointer over nested windows in Windows 8 or Windows Server 2012
• "0x000000D1" Stop error on a virtual machine in Windows Server 2012
• "0x0000004E" Stop error when shadow copying fails on a computer that is running Windows Server 2012
• "Stop 0x00000149" when you restore backup files in Windows 8 or Windows Server 2012
• Windows does not create a memory dump file when a Stop error occurs in Windows 8 or Windows Server 2012
• Save Support Dollars by Checking Your Memory Dump before Calling Support

7. Solutions related to DNS:

• Don't be afraid of DNS Scavenging. Just be patient.
• Optimizing your network to keep your DNS squeaky clean
• The size of the Active Directory increases rapidly on a Windows Server 2003-based or Windows Server 2008 R2-based domain controller that hosts the DNS Server role
• Some DNS name queries are unsuccessful after you deploy a Windows-based DNS server
• No records in the secondary DNS zone and DNS error 6527
• A DNS Update is recorded as failed: Event ID 5774, 1196, or 1578

8. Solutions related to Sysvol access or replication issues:

• DFSR Event ID 2213 is logged on Windows Server 2008 R2 and Windows Server 2012
• How to force an authoritative and non-authoritative synchronization for DFSR-replicated SYSVOL (like "D4/D2" for FRS)
• What's New in Group Policy in Windows Server 2012
• Group Policy Management Console
• Group Policy Settings Reference for Windows and Windows Server

9. Solutions related to Windows Volume Activation:

• Volume-licensed copy of Windows 8 prompts for activation unexpectedly
• Windows activation fails and may generate error code 0x8004FE33
• Installing Volume Activation Services Role in Windows Server 2012 to setup a KMS Host
• Active Directory-Based Activation vs. Key Management Services
• Converting KMS Clients to MAK Activation
• How to troubleshoot the Key Management Service (KMS)
• Volume Activation Troubleshooting
• Appendix A: KMS Client Setup Keys
• Configuring KMS Clients
• Update adds support for Windows 8.1 and Windows Server 2012 R2 clients to Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, and Windows Server 2012 KMS hosts
• Error 0x8007232b or 0x8007007B occurs when you try to activate Windows

10. Solutions related to Clustering issues – General:

• Validate Hardware for a Failover Cluster
• Recommended hotfixes and updates for Windows Server 2012-based failover clusters
• Can't access a resource that is hosted on a Windows Server 2012-based failover cluster
• Clustered shared volumes go offline or the Cluster service stops during VM backup on a Windows Server 2012 Hyper-V host server
• Clustered virtual machine cannot access LUNs over a Synthetic Fibre Channel after you perform live migration on Windows Server 2012 or Windows Server 2012 R2-based Hyper-V hosts
• Virtual Machine goes to Resync-required state after live migration
• The Microsoft support policy for Windows Server 2012 failover clusters