Archive for the ‘Windows Server 2008 R2’ Category

List of Cluster Hotfixes for Windows Server 2008 R2

Hotfixes that were rolled-up to 976932 — Windows 7 and Windows Server 2008 R2 Service Pack 1 (SP1)

  • 974930 — An application or service that queries information about a failover cluster by using the WMI provider may experience low performance or a time-out exception
  • 976571 — Stability update for Windows Server 2008 R2 Failover Print Clusters
  • 978001 — Cluster resources do not automatically fail over to another node when you disconnect the private and public network interfaces in a Windows Server 2008 failover cluster or in a Windows Server 2008 R2 failover cluster
  • 978562 — The "Validate Multiple Arbitration" test on a Windows Server 2008 R2-based failover cluster may incorrectly fail
  • 979782 — An update rollup package for the Validate a Configuration Wizard of the Failover Clustering feature is available for Windows Server 2008 R2
  • 2277439 — The Cluster service stops responding if you run backup applications in parallel in Windows Server 2008 R2
  • 2294255 — MS10-086: Vulnerability in Windows shared cluster disks could allow tampering
  • 2353832 — Authentication requests between nodes in the same failover cluster may be unable to use the Kerberos protocol if the Negotiate SSP is specified in Windows Server 2008 R2
  • 2353808 — The WINS replication operation fails on a failover cluster node that is running Windows Server 2008 R2

Hotfixes that were released after Windows 7 and Windows Server 2008 R2 Service Pack 1 (applicable to both SP0 and SP1 systems)

  • 2446607 — You cannot enable BitLocker on a disk volume in Windows Server 2008 R2 if the computer is a failover cluster node
  • 2462576 — The NFS share cannot be brought online in Windows Server 2008 R2 when you try to create the NFS share as a cluster resource on a third-party storage disk
  • 2485543 — You cannot access or mount a Windows Server 2008 R2-based NFS share after a failover if the NFS share uses Krb5 or Krb5i authentication
  • 2494016 — 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
  • 2494036 — A hotfix is available to let you configure a cluster node that does not have quorum votes in Windows Server 2008 and in Windows Server 2008 R2
  • 2494162 — 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
  • 2496034 — 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
  • 2512715 — Validate Operating System Installation Option test may identify Windows Server 2008 R2 Server Core installation type incorrectly in Windows 7 or in Windows Server 2008 R2
  • 2520235 — "0x0000009E" Stop error when you add an extra storage disk to a failover cluster in Windows Server 2008 R2
  • 2531907 — Validate SCSI Device Vital Product Data (VPD) test fails after you install Windows Server 2008 R2 SP1
  • 2549448 — Cluster service still uses the default time-out value after you configure the regroup time-out setting in Windows Server 2008 R2
  • 2549472 — Cluster node cannot rejoin the cluster after the node is restarted or removed from the cluster in Windows Server 2008 R2
  • 2550886 — A transient communication failure causes a Windows Server 2008 R2 failover cluster to stop working
  • 2550894 — Cluster service leaks memory when the service handles state change notifications in Windows Server 2008 R2 or Windows Server 2008
  • 2552040 — A Windows Server 2008 R2 failover cluster loses quorum when an asymmetric communication failure occurs
  • 2575625 — Cluster service initiates a failover after a delay of about 80 seconds when you shutdown the active node in Windows Server 2008 R2
  • 2578113 — The Cluster service takes about 30 seconds to fail over IPv6 IP addresses in Windows Server 2008 R2
  • 2579052 — 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
  • 2580360 — A heap memory leak occurs when an application or service queries the MSCluster_Resource WMI class in Windows Server 2008 R2
  • 2606025 — "0x000000D5" Stop error on a failover cluster node that has special pool enabled and that is running Windows Server 2008 R2
  • 2648385 — You cannot use WMI to manage CSV resources in Windows Server 2008 R2
  • 2637197 — CSV LUNs fail if you use a VSS hardware provider to back up virtual machines on a Windows Server 2008 R2-based cluster
  • 2616514 — Cluster service sends unnecessary registry key change notifications among cluster nodes in Windows Server 2008 or in Windows Server 2008 R2

Posted March 14, 2012 by Robert Smit in Windows 2008 R2, Windows 2008 R2 Cluster, Windows 2008 R2 SP1, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2

Tagged with ,

A hotfix is available to let you configure a cluster node that does not have quorum votes in Windows Server 2008 and in Windows Server 2008 R2

Get the hotfix

Windows Server Failover Clustering (WSFC) uses a majority of votes to establish a quorum for determining cluster membership. Votes are assigned to nodes in the cluster or to a witness that is either a disk or a file share witness. You can use the Configure Cluster Quorum Wizard to configure the clusters quorum model. When you configure a Node Majority, Node and Disk Majority, or Node and File Share Majority quorum model, all nodes in the cluster are each assigned one vote. WSFC does not let you select the cluster nodes that vote for determining quorum.
After you apply this hotfix, you can configure a cluster node that does not have quorum votes.

 

After you apply the following hotfix, you can select which nodes vote. This functionality improves multi-site clusters. For example, you may want one site to have more votes than other sites in a disaster recovery. Without the following hotfix, you have to plan the numbers physical servers that are deployed to distribute the number of votes that you want for each site.
By default, all nodes in the cluster have one vote. After you apply the following hotfix, administrators can change the vote functionality in the quorum model by configuring a node to have 0 votes.
This hotfix adds the following functionality:

  • The NodeWeight common property for nodes
    This property can be configured by using either the Get-ClusterNode Windows PowerShell cmdlet or the Cluster.exe command. For example, you run the following command at a command prompt:

    Cluster.exe . node <NodeName> /prop NodeWeight=0

    To query the NodeWeight common property, you can use the following PowerShell cmdlet command:

    Get-ClusterNode “NodeName” | fl *

    To modify the NodeWeight property, you can use the following PowerShell cmdlet command:

    (Get-ClusterNode “NodeName”).NodeWeight = 0

    A new NodeWeight property is added to the MSCluster_Node WMI class to let you manage node weights by using WMI.

  • The PreventQuorum (PQ) switch
    This switch starts the Cluster service (ClusSvc) and prevents a node from reaching quorum. The Cluster service can be started by using the PQ switch. For example, you can run the following command at a command prompt:

    NET START ClusSvc /PQ

    The PQ switch can be used to enforce the cluster owner and to maintain consistency in the Cluster database.
    For example, you have a partitioned 2-node cluster in which NodeA has one vote and NodeB has zero votes. By default, NodeB cannot reach quorum and cannot start the cluster. However, the Cluster database may be updated when the ForceQuorum switch is used to start NodeB even if it does not have quorum. Therefore, NodeB has a newer Cluster database, and NodeB can prevents NodeA from starting and from incorrectly overwriting the updated Cluster database by using its one vote to reach quorum. The PQ switch can be used to prevent NodeA from reaching quorum. Therefore, NodeA waits until it can communicate with the existing cluster and until it can join the existing cluster that has NodeB to obtain the updated Cluster database and to maintain consistency.
    The PQ switch performs the opposite action of the ForceQuorum switch. The ForceQuorum switch allows the Cluster service to form a cluster even if it has not received a majority of votes. The PQ switch does not allow the Cluster service to form a cluster even if it has received a majority of votes.

    get more on the source : MS

Posted February 28, 2012 by Robert Smit in Windows 2008 R2 Cluster, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2

Tagged with ,

Clustering DHCP Windows Server 8

On the BUILD conference highlights Microsoft showed new features of windows server 8. one of the new things was clustering DHCP. Now in windows 8 the DHCP clustering is easy to setup and to manage.

Clustering DHCP Windows Server 8 When you have your cluster just add the Role and select DHCP server. Just for the Demo I turned off the second node. Just make sure that you have installed the Windows Role DHCP on both nodes. this is not the cluster Role.

Clustering DHCP Windows Server 8 We choose a netbios name and a IP that will be used for the Clustered DHCP server.

And We select some storage that hold the DHCP files ( DB ) image

image And as I said the Second node is turned off just for the demo to show you the warning the wizard shows you. it is in yellow and says there is only one node.

The Cluster Overview Clustering DHCP Windows Server 8 As you can see the DHCP resource is running on node 1 and in the lower screen you can see the DHCP cluster configuration. Disk , IP, Name. and If you want to change this, this is the place to do this.

If you want to manage the DHCP server just do manage in the Cluster View

image Right click on the DHCP role.

 

Sample overview of the DHCP server Clustering DHCP Windows Server 8

Now that I have turned on the second node I can do a failover. Eh but you did not configure anything on this node Except installing the Windows DHCP role.

Yes but as it is a cluster the configuration moves to the other node.

image Clustering DHCP Windows Server 8 And I can do manage on both nodes or on a management server open the DHCP scope based on the DHCP netbios name.

Clustering DHCP Windows Server 8 Easy as that and the configuration of all the DHCP scopes are here.

A nice new feature of windows server 8.

Posted October 7, 2011 by Robert Smit in DHCP Cluster, Windows 2008 R2 Cluster, Windows 2008 R2 DHCP Cluster, Windows 8 Cluster, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2

Tagged with ,

« Older Entries
Newer Entries »

  • Tag

    ADK Analyzer Application Virt Azure Book Cleanup Cloud Computing Cluster Events Exchange Forefront GPO Hyper-V Infrastructure Planning Intelligent Application Gateway SP2 MAP McAfee MDT Microsoft Azure Microsoft Most Valuable Professional Microsoft Vista mvp SCM SCUG Security SQL Server SQL Server 2014 Storage Spaces System Center Techdays Teched Teched 2008 The New Efficiency Tools Vista VMWARE Windows Windows 7 Windows 2008 Windows 2008 R2 Windows Server 2008 R2 Windows Server 2012 Windows Server 2012 R2 Windows Server 2015 Windows Server 2016