If you a running a Windows 2012 failover cluster and you tried to access the resource by using a resource name from a Windows XP-based or Windows Server 2003 computer, you will receive the following error message:find the following issue:
is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. Logon Failure: The target account name is incorrect
This issue occurs because the rc4-hmac keys on the Domain Controller and the cluster side for the virtual computer object (VCO) are different. The ticket decryption fails when the ticket is encrypted by using the rc4-hmac encryption. Additionally, the cluster becomes unavailable for any computer that uses the rc4-hmac keys.
Note: This applies to Windows 8 and Windows 2012 Fail over cluster and as per Microsoft advise it can impact Hyper-V deployments where the CNO password gets out of sync and you can no longer do Live Migrations.
So this should be proactively deployed
The hotfix is available here: http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=2838043&kbln=en-us
Microsoft published an article that documents the hotfixes that are currently available for Windows Server 2012-based Failover Clusters.
Failover Clustering allows multiple servers to provide high availability of server roles. Failover Clustering is often used for File Services, Virtual Machines, Database Applications, and Mail Applications.
The recommended hotfixes and updates for Windows Server 2012-based Failover Clusters : http://support.microsoft.com/kb/2784261
Microsoft released an update to improve the cloud service provider in Windows 2012
Note : The KB2870270 roll-up hotfix replaces KB2848344. This hotfix contains the fix for Trim as well as ODX. It is no longer necessary to disable Trim or ODX with this fix applied
The following issues are also resolved with this update:
– An Windows 2012 Hyper-V Cluster that uses CSV is moved or is toggled between directed access and redirected access when the performance monitor is running. In this situation, the performance counters no longer function.
– An Windows 2012 Hyper-V Cluster and the Virtual Machines VHD files are stored on a scale-out file share and the server is under a heavy load. In this scenario, the server may crash, and you may receive a Stop error message that resembles: STOP: 0x000000C2 (parameter1, parameter2, parameter3, parameter4) – Notes: The parameters in the Stop error message vary, depending on the configuration of the computer and not all “Stop 0x000000C2″ errors are caused by this issue.
– When you use the Windows thin provisioning feature on a Windows Server 2012-based computer, you experience the same I/O delays or I/O stalls that occur during the volume-unmounting process in NTF volumes.
Plus the issues that are described in the following Microsoft Knowledge Base (KB) articles are resolved:
Microsoft just released a critical fix for hyper cluster that have been backed up by System Center DPM
“Physical Disk resource move during the backup of a Cluster Shared Volume (CSV) may cause resource outage”.
If you have configured a Windows Server 2012-based Hyper-V failover cluster CSV and your backup software perform the backup by using snapshots and the Physical Disk resource is moved to another node in the cluster, the Physical Disk resource may fail to come online if the backup of the CSV is in progress. As a result, virtual machines that rely on the CSV may crash.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
More info :http://support.microsoft.com/kb/2869923
- Windows Server 2012 Datacenter
- Windows Server 2012 Essentials
- Windows Server 2012 Foundation
- Windows Server 2012 Standard
W2008R2 Failover Cluster : New hotfix to improve performance enables faster failover times in a SQL 2012
After you enable the AlwaysOn Availability Group feature in Microsoft SQL Server 2012 on a Windows Server 2008 R2-based failover cluster, using local and remote Availability Group database replicas, the failover time to the local replica takes longer than expected.
Note This issue occurs because of inter-node communication within the cluster.
To improve the performance of the “AlwaysOn Availability Group” feature in SQL Server 2012 is available for Windows Server 2008 R2.
Important : You must restart the computer after you apply this hotfix
To download: http://support.microsoft.com/kb/2687741/en-us
Here is the list of required and optional post Windows 2008R2 SP1 hotfixes.
Please keep in mind that it all depends on which hardware and software combinations are used:
Note: Windows Server 2008 R2 SP1 should be installed at a minimum plus the required hotfixes.
Validate SCSI Device Vital Product Data (VPD) test fails after you install Windows Server 2008 R2 SP1
http://support.microsoft.com/kb/2531907(required for 3+ node Hyper-V clusters)
The network connection of a running Hyper-V virtual machine may be lost under heavy outgoing network traffic on a computer that is running Windows Server 2008 R2 SP1
The Cluster service stops unexpectedly on a Windows Server 2008 R2 failover cluster node when you perform multiple backup operations in parallel on a cluster shared volume
http://support.microsoft.com/kb/2494162(required for Veeam backup software)
MPIO failover fails on a computer that is running Windows Server 2008 R2
The MPIO driver fails over all paths incorrectly when a transient single failure occurs in Windows Server 2008 or in Windows Server 2008 R2
Performance decreases in Windows Server 2008 R2 when the Hyper-V role is installed on a computer that uses Intel Westmere or Sandy Bridge processors
http://support.microsoft.com/kb/2517329 (for example : Intel Xeon 5600 series processors )
Stop error 0x0000007a occurs on a virtual machine that is running on a Windows Server 2008 R2-based failover cluster with a cluster shared volume, and the state of the CSV is switched to redirected access.
http://support.microsoft.com/kb/2494016 (required for Veeam backup software)
An update is available for Hyper-V Best Practices Analyzer for Windows Server 2008 R2
“0x0000009E” Stop error when you add an extra storage disk to a failover cluster in Windows Server 2008 R2
A virtual machine online backup fails in Windows Server 2008 R2 when the SAN policy is set to “Offline All”
Cluster node cannot rejoin the cluster after the node is restarted or removed from the cluster in Windows Server 2008 R2
Cluster service stops when an error occurs in the registry replication process of a failover cluster in Windows Server 2008 R2 or in Windows Server 2008
“0x20001″ Stop error when you start a Linux VM in Windows Server 2008 R2 SP1
A heap memory leak occurs when an application or service queries the MSCluster_Resource WMI class in Windows Server 2008 R2
Cluster service initiates a failover after a delay of about 80 seconds when you shutdown the active node in Windows Server 2008 R2
New registration entries are added to the Persistent Reservation table when the physical disk resource that is associated with the CSV is taken offline on a Windows Server 2008 R2-based Failover Cluster
A transient communication failure causes a Windows Server 2008 R2 failover cluster to stop working
Cluster service leaks memory when the service handles state change notifications in Windows Server 2008 R2 or Windows Server 2008
Hyper-V Export function consumes all available memory in Windows Server 2008 or in Windows Server 2008 R2
Microcode update for Intel processors in Windows 7 or in Windows Server 2008 R2
Corrupted VSS snapshot
FIX: The guest operating system may crash (STOP 0xd) when you perform a live migration of Hyper-V virtual machines in a Windows Server 2008 R2 environment
A BIG Thanks to Hans Vredevoort
Sometimes you need an hotfix but you find that hotfix is currently unavailable for online request. How to find out a superseding hotfix.
I found out the procedure in this wiki page : http://social.technet.microsoft.com/wiki/contents/articles/windows-server-how-to-determine-update-supersedence-and-find-replacing-hotfixes.aspx