Archive for the ‘Windows 2008 R2 Printer Cluster’ Category

production network card is not the first bound network card

Often when you do a validation health check the first nic is not the first nic and you did check it in the network options. There is a way to change this or to checkit.

You can change it in the advanced settings with the up down arrow.



Do this with WMI

Open a admin Command prompt in the search/run  type CMD and instead of hitting the Enter key, use Ctrl+Shift + Enter this opens the Admin CMD.

Now Run :

wmic nicconfig get description, SettingID > C:\nicguidconfig.txt

Lookup the nicguidconfig.txt

It looks like this :


Description                                  SettingID                              
WAN Miniport (SSTP)                          {E28D896F-9EA8-433A-9C10-66C97C19A921} 
WAN Miniport (IKEv2)                         {DEA99649-B5BF-4318-B16E-A36317939C93} 
WAN Miniport (L2TP)                          {483C9FF8-503D-414B-B402-E4C1F1F568CB} 
WAN Miniport (PPTP)                          {C0DE3E38-8BA7-479F-8B75-833F294C5AA8} 
WAN Miniport (PPPOE)                         {DB2B4279-B5CF-4626-9DBA-32D0ECE44C87} 
WAN Miniport (IPv6)                          {F3229805-869E-479E-BA76-DD643F1D1B80} 
WAN Miniport (Network Monitor)               {72DD97A9-E544-4915-88D8-44E829C34F68} 
Intel(R) 82566MM Gigabit Network Connection  {39F6A82E-D18C-4642-A721-61BB49CC894B} 
WAN Miniport (IP)                            {7C5653F0-144A-4534-9E34-28AC99CBA85E} 
Broadcom 802.11 Multiband-netwerkadapter     {C4A5D563-B776-40BB-BA44-FF01E000D37B} 
RAS Async Adapter                            {E2F8A220-AF88-446C-9A55-453E58DD3A33} 
Microsoft ISATAP Adapter                     {D70E80B8-8684-4391-AAE8-F7104BBD5749} 
Microsoft ISATAP Adapter                     {5EAB7E38-392E-42DD-AF36-3540D3265724} 
Bluetooth-apparaat (Personal Area Network)   {EBFF2180-B91D-409C-B983-3DD788A7F3BC} 
Microsoft ISATAP Adapter                     {A0E7C614-5C66-4A1F-8C5E-E41F81C0A5C2} 
Microsoft 6to4 Adapter                       {4749EF9C-66DA-499B-BA8D-43AA8D76422A} 


Now that we have the Guid we go to the Register and look it up :



Open the Bind



Cut and paste GUID’s so that production network card (or NIC team) is at the top of the list.

Save key and confirm binding is correct via ipconfig /all



Your Done

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

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.

  • 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.

6.0.600 2 . 22xxx Windows Server 2008 SP2


Get the Hotfix

Microsoft sends invitations to testers for Windows 7, Server 2008 R2 SP1


You are receiving this invitation based on the quality of feedback you have provided on previous Windows programs and the Microsoft Windows release team would like you to participate in the Microsoft Windows 7 and Windows Server 2008 R2 Service Pack 1 (SP1) release program, to be available shortly, as announced at the Microsoft’s TechEd conference.

Accepting this invitation will allow you to access pre-release versions of the Service Pack for the purposes of validating the release readiness. We highly value your past feedback and know we can count on you again to help us build a great new version of Windows!

The SP1 release version is not available quite yet but we need to assemble a great team of program peers early so you are ready to go when we are! If you accept this invitation you’ll be notified when the release version becomes available.

What you will get if you choose to participate

• Early access to downloadable Windows 7 SP1 and Windows Server 2008 R2 SP1 releases
• Access to private newsgroups to share information about the release with other program peers and with Microsoft staff
• The ability to report bugs and track their status
• An opportunity to help us build a better Windows by validating the release readiness

What we will ask of you if you choose to participate

• Download and install Windows 7 SP1 or Windows Server 2008 R2 SP1 on at least one PC each
• File bugs if you encounter them as well as respond to surveys as you can.
• Validation we are seeking
o Set-up and installation
o Application Experience/Compatibility
o Device Experience/Compatibility
• We ask that you actively participate in discussions on the newsgroups and share your opinions with us and others


Read more :

  • Tag