Windows Server Add VHD disk or boot from VHD disk #WS2012 #VHD

 

Did You know that you can add a VHD disk to your windows 2008 R2 Server and /or boot from it ?

You can easy edit the VHD and reuse it in hyper-v.

So go to disk manager and right click on disk management image

You can create a new VHD. image If you use dynamic make sure you have the disk space that u needed.

I use a fixed disk with windows 7 on it. that I use in hyper-v as golden Image for my desktops.

image fill in the VHD location. image  You can make it read only if you need software install that is on a VHD, I have a VHD with all the ISO files on it that I can mount on every server if I need to install extra software or tools.

But now I use the Windows 7 VHD image now that I mounted the disk I can use it.

I need a WallPaper on the windows 7 image image

image now I can do a offline or detach vhd , If I don;t I get this error in hyper-v

image even if the disk is offline image

image You can also delete the VHD 😉

image image image

or You can boot from the VHD it is just like in windows 7   mount it and use bcdedit to change the boot string.

below are samples.

bcdedit /set {GUID} device file=[c:]\vhd\win7.vhd
bcdedit /set {GUID} osdevice file=[c:]\vhd\win7.vhd

 

Here are some articles and video about booting from VHD.
http://blogs.msdn.com/cesardelatorre/archive/2009/01/11/windows-7-natively-booting-from-a-vhd-virtual-pc-image-file.aspx

Inside Windows 2008 R2 Virtualization Improvements and Native VHD Support (Mark Russinovich)
http://www.microsoft.com/emea/teched2008/itpro/tv/default.aspx

Robert Smit MVP Blog

SQL Server Failover Cluster Installation

The installation of a SQL cluster is easy There is a Menu Item Create new Failover Cluster. #ws2012 #SQLsp1 #sql2012 #cluster #fail #howto

Well I don’t use this option Winking smile Why not to easy eh yes but more important is something fails like wrong IP etc the SQL install is lost , you need to deinstall the whole SQL mesh, I like the advanced version and trust me it will be easy.

OR you can loop at the technet site to see how and when:

SQL Server Failover Cluster Installation

SQL Server 2012

To install a SQL Server failover cluster, you must create and configure a failover cluster instance by running SQL Server Setup.

http://technet.microsoft.com/en-us/library/hh231721.aspx

So how Do we start this installation. Well you can see my blog post :

https://robertsmit.wordpress.com/2012/03/27/how-to-create-a-new-sql-2012-server-failover-cluster-setup-multiple-instances-on-windows-server-2012/

This blog post covers all the screen shots but this post is more a part…

View original post 900 more words

Robert Smit MVP Blog

For Creating a ISCSI target on a cluster you get a high available iscsi target.

Sure you can run this on a single server (VM ) and move this between the hyper-v nodes.

for doing this in a cluster you need to do the following steps.

Add cluster Resource ISCSI target , fill in the netbios name that you want for the iscsi target

 

clip_image002clip_image004

give the target a disk that will hold the VHD files

clip_image006clip_image008

clip_image010

Now that the cluster resource is created the iscsi target is ready to use.

 

clip_image012 clip_image014

There is no option in the cluster to start the iscsi target you have to start this in the server manager

clip_image018clip_image020

As here you can create a new VHD file and use this for targeting , I have no groups so this needs to be created first. I use a small disk just for testing.

 

clip_image022 image

for…

View original post 92 more words

Robert Smit MVP Blog

Now that Windows 2012 is here and you want to test if the OS is as good as you want and see if the application is still running on windows 2012.

In this case We build a NLB website easy with just the basic steps any one can do this.

First we add the roles and features to the servers that we are going to use for the NLB.

Select the Features “ Network Load Balancing ” only this you need for NLB

 

 

clip_image002

After this I look at my NIC’s most important that you use two nic’s in a VM this is easy in a physical box now days there are at least 2 nic’s in the server. use them.

I gave the Nic’s an IP that is not in the same subnet as the production lan, and also you can use a different VLAN for the NLB…

View original post 316 more words

Robert Smit MVP Blog

Now that windows 2012 is in beta we can talk almost about anything and it is time to create my demo SQL 2012 machine. In this case I uses the Windows server 8 cluster from the other blog item to create a SQL 2012 cluster with 3 instances. All of the instances are created on different ways , Instance 3 is a ZTI Winking smile  #WS2012 #TEE #TEE13 #MVP13

For starters build a 2 node cluster or more nodes if you want and use the SQL 2012 Media. I use the Enterprise version.

Remember that I create the Server Group image and my cluster image I already added the disk to my cluster mounted the SQL 2012 ISO file to the node. Ready for the Setup.

again I use a lot of pictures in this blog and I do almost everything twice just to show you how you can configure your cluster.

clip_image002 the…

View original post 1,068 more words

Team in windows 2012 do’s and don’ts

Sometimes you need more network true put than you have.

But did you know you can create a Team in windows 2012 ?

In my lab I did some testing just to show you how things can be done and what do should not do. ( Remember It is all LAB )

clip_image002

In a Hyper-v VM you can create Up to 12 virtual network adapters per virtual machine

8 synthetic network adapters ( 10 Gb ) and 4 emulated network adapters ( 100mb )

This is the Maximum count of network adapters in a VM. This in not only in windows 2012 but also in Windows 2008R2 no changes there.

In this sample I will create a team with a 60GB network true put and one 300 Mb network adapter just because you can 😉 I could create more but I need different nic’s on my cluster.

Fire up the server manager and default the NIC Teaming is disabled To enable this click on disable and a new window will open

 

clip_image002[4]   clip_image004[4]

As you can see NIC teaming is no disabled , but click on disabled a new window pops up.

Form this windows we going to create a Team 

clip_image006[4]    clip_image008[4]

Here We can create a new TEAM DO NOT TRY this in your production environment This is WRONG

Did you see I added 10gb and 100 mb nic’s oh whoow 10,1 gb nic this makes no sense remember this only if this is a backup line and the nic is not active but standby. In general this is a bad Idea. but for now I do this just because you can.

I create my team and select different NIC’s

clip_image010[4]

I create My team <> add to new Team

clip_image012[4] clip_image014[4]

When configuring NIC Teaming in "Switch Independent" mode, the teaming configuration will work with any Ethernet switches – even non-intelligent switches – because Windows Server 2012 handles all of the intelligence with this NIC teaming mode. No special configuration changes are necessary. You can even use this mode to team across separate switches in scenarios that require switch diversity for extra network fault tolerance.

clip_image016[4]    clip_image018[4]

Now that the team is created it shows up in a nice icon in the network adapters

clip_image019[4] The VM can hold Up to 12 virtual network adapters per virtual machine

8 synthetic network adapters

4 emulated network adapters

clip_image021[4] clip_image023[4]

Now that we have made a team ( I did Correct the mix with 100mbit and 10 gb )

 clip_image027[4] clip_image029[4] 

So now I have two teams on adapter from 300 Mb and one from 60 Gb

60 Gb I would use for CSV in my cluster Winking smile or I could use this for SQL always on

clip_image031[4]

As you can see the networks shows up in my cluster so you can use them directly or you can create several virtual networks on top of this NIC team. this will be in my next blog.

 

Greetings

Windows Server 8 Beta Hyper-V Component Architecture Poster

The link for this poster is: http://www.microsoft.com/download/en/details.aspx?id=29189

 

Provides a visual reference for understanding key Hyper-V technologies in Windows Server 8  Beta and focuses on Hyper-V Replica, networking, virtual machine mobility (live migration), storage, failover clustering, and scalability.

Windows Server 8 Beta Hyper-V Component Architecture Poster

Here are links to previous posters:

1. Windows Server 2008 Hyper-v Component Architecture with Service Pack 1
http://www.microsoft.com/download/en/details.aspx?id=2688

2. Hyper-v Component Architecture
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=3501

3. Windows Server 2008 R2 component posters
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=7002

4. Windows Server 2008 Component Posters
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=17881

Technorati Tags: ,,,,,,,,,,,,,,,,,,
Windows Live Tags: Windows,Server,Beta,Hyper,Component,Architecture,Poster,details,Provides,Replica,machine,Here,posters,Service,Pack,microsoft,download,aspx,displaylang
WordPress Tags: Windows,Server,Beta,Hyper,Component,Architecture,Poster,details,Provides,Replica,machine,Here,posters,Service,Pack,microsoft,download,aspx,displaylang

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

 

Technorati Tags: ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Windows Live Tags: List,Cluster,Hotfixes,Server,Service,Pack,provider,performance,exception,Failover,Print,node,Validate,Multiple,Arbitration,Configuration,Wizard,backup,Authentication,requests,Kerberos,protocol,Negotiate,replication,operation,BitLocker,disk,computer,resource,storage,Stop,error,machine,System,Installation,Option,SCSI,Device,Vital,Product,Data,communication,failure,memory,shutdown,registration,Persistent,Reservation,MSCluster_Resource,LUNs,machines,interfaces,disks,systems,operations,notifications,nodes,quorum,registry
WordPress Tags: List,Cluster,Hotfixes,Server,Service,Pack,provider,performance,exception,Failover,Print,node,Validate,Multiple,Arbitration,Configuration,Wizard,backup,Authentication,requests,Kerberos,protocol,Negotiate,replication,operation,BitLocker,disk,computer,resource,storage,Stop,error,machine,System,Installation,Option,SCSI,Device,Vital,Product,Data,communication,failure,memory,shutdown,registration,Persistent,Reservation,MSCluster_Resource,LUNs,machines,interfaces,disks,systems,operations,notifications,nodes,quorum,registry

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.

image

OR

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 :

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Linkage\Bind

image

Open the Bind

image

 

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

image

 

Your Done

Create Hyper-V VHD in Seconds With WAIK WIM2VHD.WSF

There are several ways to install a VM simple create and install OS. Or with SCVMM 2012 Winking smile 

But If you want to do it fast and you don’t like the Image thing witch I don’t like. then there is a solution. In under the 3 minutes I create a Fresh installed Windows 2008R2 SP1 Server for Hyper-V.

How ? with an unattend install Create an XML put in your stuff and you are ready to go.

But there is more, Choose the right tools there are multiple ways to do this. I show you how to use the WAIK tools. in the WAIK tools there is this little script WIM2VHD.WSF this can do magic for you.

First Install the WAIK 3.1 Version this is the latest version till now. Download the 3.0 WAIK and update it with the waik_supplement_en-us this will make the version 3.0 <> 3.1

The ISO can be downloaded from the following link:

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=0aee2b4b-494b-4adc-b174-33bc62f02c5d

Installation Instructions

The ISO does not contain instructions for installation.  More information on the update can be found at the following location:  http://technet.microsoft.com/en-us/library/dd349350(WS.10).aspx.

To install the updated WINPE you copy the contents of the ISO over top of the following directory:

C:\Program Files\Windows AIK\Tools\PETools image

You should choose to overwrite the files.  It basically replaces all the WINPE specific files and Optional Components (OC’S). 

ConfigMgr and Microsoft Deployment Toolkit Information

 

 

C:\Program Files\Windows AIK\image

Now we start up the WIM2VHD.WSF

And using the Parameters :

where is your WIM file on the Source :

/WIM:Z:\en_windows_server_2008_r2_with_sp1

Source Files

\sources\install.wim

What is your version

/SKU:SERVERENTERPRISE

The VHD Name

/VHD:D:\foo.vhd

And the unattend file used for installation

/UNATTEND:C:\zero.xml

 

imageimageimageimage

So with this I have a complete unatted install in just under de 2 min. Yes then the image is ready to use but the OS needs to setup.

With a little Powershell Script I create a auto VM create and startup. You can adjust this anyway you like. Just for testing.

 

image

Type the Virtual Machine’s name: TEST01
How much memory to assign? In MB: 4096
How many CPUs to assign? Integer Number: 4

Virtual Machine TEST01 has been successfully created
Start and Connect to  Type [Y]ES or [N]O: So with this I have a complete unatted install in just under de 2 min. Yes then the image is ready to use but the OS needs to setup.

This takes also about 5 Min depends on the unattend.xml if you do a lot of after config then it needs more time

imageimage

image

Microsoft Deployment Toolkit 2012

Microsoft Deployment Toolkit (MDT) 2012 Beta 1 rides the next wave of System Center releases with support for System Center Configuration Manager 2012. For Lite Touch installations, MDT 2012 improves the overall client-side user experience, while also providing behind-the-scenes enhancements for partitioning, UEFI, and user state migration. These features, combined with many small enhancements, bug fixes, and a smooth and simple upgrade process, make MDT 2012 Beta 1 more reliable and flexible than ever.

MDT 2012 Beta 1 provides new capabilities, such as:

· Support for Microsoft System Center Configuration Manager 2012 Beta 2, including the new application model and user device affinity (UDA).

· Improved Lite Touch partitioning, supporting the preferred partition layouts described in the Windows Automated Installation Kit.

· Support in Lite Touch for deploying 64-bit Windows® to computers that support Unified Extended Firmware Interface (UEFI) (without requiring compatibility support for legacy BIOS).

· New Lite Touch “Deploy to VHD” task sequence templates that support deploying a Windows 7 or Windows Server® 2008 R2 image into a virtual hard disk (VHD) file that can then be used for booting the OS (“boot from VHD”).

· Added support for deploying Windows ThinPC and Windows POSReady 7.

· Improved Lite Touch wizard look and feel.

· Continued support for System Center Configuration Manager 2007 SP2 and all operating systems supported by MDT 2010.

· Many bug fixes and other small improvements.

This release supports the deployment of the Windows 7, Windows Vista®, Windows XP, Windows Server 2008 R2, Windows Server 2008, and Windows Server 2003 operating systems. See the Microsoft Deployment Toolkit Documentation Library, which is included with MDT 2012 Beta 1, for the complete documentation for this release.

image image

Technorati Tags: ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Windows Live Tags: Microsoft,Deployment,Toolkit,Beta,System,Center,Configuration,Manager,Lite,client,user,UEFI,migration,features,Support,Installation,Firmware,Interface,legacy,BIOS,Deploy,task,sequence,Server,image,disk,boot,ThinPC,POSReady,Many,supports,Vista,Documentation,Library,installations,enhancements,computers,templates,systems,improvements
WordPress Tags: Microsoft,Deployment,Toolkit,Beta,System,Center,Configuration,Manager,Lite,client,user,UEFI,migration,features,Support,Installation,Firmware,Interface,legacy,BIOS,Deploy,task,sequence,Server,image,disk,boot,ThinPC,POSReady,Many,supports,Vista,Documentation,Library,installations,enhancements,computers,templates,systems,improvements

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

http://support.microsoft.com/kb/2494036

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 http://support.microsoft.com/kb/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

http://support.microsoft.com/kb/2494036

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 http://support.microsoft.com/kb/2494036

Lost Default Gateway Windows 2008 R2 SP1

Do you know the problem reboot your server and you can’t RDP to it but you can ping and if you are in the same subnet you can RDP ?

Well maybe you hit a bug , yes I was surprised to where is my DGW ? try bing and you find more of the same problems but easy to fix with a hot fix but why one server does this and others don’t ?

See in google / Bing / Yahoo

The default gateway setting is lost when you reboot the server

for some reason my LAN just suddenly lost its Default Gateway

No Default Gateway  ?

Default Gateway Missing After Reboot

my tcpip default gateway gets reset on reboot

It looks like this after a reboot your Ip and subnet and DNS is there but no default Gateway

image

And if you looked it up in the registery

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Para
meters\Interfaces\<GUID>\DefaultGateway
Where <GUID> is the interface value for the network card.

It is not there , sure you can put it in but after a reboot it is gone.

Yes a scheduled task Winking smile No there is a hot fix for this.

image

 

Or you can reset the IP stack.

netsh int ip reset

netsh: this is a Windows utility that allows one to display or change network settings locally or remotely.

int: this argument specifies that you wish to use the “interface” context within the netsh utility.

ip: this argument specifies that you wish to use the “ip” context within the “interface” context of netsh. An example of another context that could have been specified here instead would be “ipv6.”

reset: this argument is an instruction within the previously-specified context and subcontext means what it says, to reset to default.

Consider the following scenario:

  • You use the netsh command to enable a network interface on a computer that is running Windows Server 2008 or Windows Vista. The computer retrieves IP addresses from a DHCP server.
  • You use the netsh command to set a default gateway for the network interface.

In this scenario, the default gateway is set successfully. You can verify it by running the ipconfig /all command. However, the default gateway of the network interface is missing after the computer restarts. If you double-click the following registry entry, you find that a null character exists in the value data of the DefaultGateway subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\<GUID>\DefaultGateway

Note <GUID> is the interface value of the network card.

To work around the issue, use the following command to set the default gateway on the interface:

Netsh int ipv4 set address <Interface Name> source=dhcp

Go here to get the HOTFIX :

Article ID: 973243 – Last Review: February 16, 2011 – Revision: 6.0

The default gateway is missing on a computer that is running Windows Server 2008 or Windows Vista after the computer restarts if the default gateway is set by using the Netsh command

 

 

Technorati Tags: ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
WordPress Tags: Lost,Default,Gateway,Windows,Yahoo,Reboot,HKEY_LOCAL_MACHINE,SYSTEM,CurrentControlSet,Services,Tcpip,Para,Interfaces,GUID,DefaultGateway,Where,interface,display,argument,context,Consider,scenario,computer,Server,Vista,DHCP,double,data,Parameters,Note,issue,Netsh,Name,HOTFIX,Article,Last,Review,February,Revision,same,subnet,find,reset,value,network,card,specifies,wish,within,here,command,restarts