Home » Posts tagged '2008'

Tag Archives: 2008

How to move Quorum disk in a failover cluster.

In a Windows Cluster, you can move roles from one node to another. Unfortunately, you may not find an option to move quorum disk to another node.

However, there is an option to move quorum disk to another node using the command line tool.

You can view the cluster status using the command:

Cluster Group

Note: This will list the status for all available resource group.

In order to move the quorum disk, you need to move the “cluster group” group to the desination node using the below command:

Cluster group “Cluster group” /moveto:NodeName

Note: Replace the NodeName with the destination node name. This is to be executed from the node that is holding the quorum disk.


Cannot open programs unless “Run As Administrator

One of the application was recently installed on Windows 2012 Server, when I click on the short cut its gives an error message stating ” … has stopped working. Windows can check online for a solution to the problem”.  Further, it gives options to check online for a solution and close the program or close the program.

To my surprise, it was found that the application opens by clicking on “Run as Administrator”. Later, clicking “Run as admin” every time was annoying. Hence, the application was set to run as administrator by default following the steps listed below:

Right click the program and select Properties

Under the compatibility tab, select Run this program as an administrator

Click Apply and OK



Verify WMI for MS Cluster issues

In a cluster environment, WMI is often used to share information and notification within the nodes. Some of the cluster issues/error due to the WMI is as listed below:

“RPC Server Unavailable” error.
Access is Denied.
The computer ‘Node1’ could not be reached.
Failed to retrieve the maximum number of nodes for ‘{0}’.
The computer does not have the Failover Clustering feature installed. Use Server Manager to install the feature on this computer.
Note: first confirm you have installed the Failover Clustering feature on this node

In above case we need to make sure that the WMI is working fine and this can be confirmed following the steps listed below:
Make sure that the WMI service is up and firewall settings.

1. Launch CMD
2. Type “WBEMTest” (without quotes”).
3. The Windows Management Instrumentation Tester will launch
4. Select Connect
5. Namespace: Root\MSCluster
6. Select Connect and if you see more options available, it means you are connected and WMI is working
7. Click on Query and enter SELECT * from MSCluster_Resource to confirm (any error shown represents WMI issue).


Server (HP) not reachable on network “Port was disabled because a pause flood was detected” .

Host was not reachable on network. When checked on ILO server is up and running. When I try to ping the server its unresponsive.Host is a blade server, hence suspected an issue with the network module. Therefore, connected virtual connect. Found one of the virtual connect module was degraded. When analysed the HP Virtual connect found an error message stating “Port was disabled because a pause flood was detected”

Further to this when validated the server port assigned to the bay1/bay2 found the status “Not Linked/Pause Flood Detected”. It confirms the issue was caused by pause Flood. In some cases, a flex-10 port can enter into disabled state due to the triggering of “pause-flood”, or network-loop. You can confirm the same port status using Virtual Connect Manager CLI. Connect to Virtual connect using SSH and Execute the below command:

Show port-protect

This would show the blade server that’s in impact. To fix the issue, please execute the below command:

reset port-protect

Verify the port status again using the command “show port-protect” and ensure no port’s protect types are reported as “Pause Flood”.
Another action plan would be to update the Drivers and Firmwares.

You can also disable is using the command listed below
set port-protect pauseFlood=Disabled


Windows could not finish configuring the system.

Recently, I was installing Windows 2008 R2 on a HP ProLiant DL380 Gen9 server. Found that the server was throwing an error message stating “Windows could not finish configuring the system.”. When you click on “OK”, servers gets automatic reboot and shows again the same error.

When searched on google, I found that this error message occurs with Windows Server 2008 R2 operating systems if the system contains a registry key that is larger than 8 kilobytes (KB). A Hotfix for this problem is available from Microsoft


In my case it was during a clean install of Windows OS, hence it was fixed following the steps listed below:

When you find the error message stating that the “Windows could not finish configuring the system” appears on your screen:

1. Hold down the SHIFT key and press F10 (SHIFT + F10) to open command prompt.
2. At command prompt type: cd oobe (& press Enter).
3. Then type: msoobe (& press Enter).
4. Finally Restart your computer.

You will see your machine back with CTRL+ALT+DEL screen.


Visitors Count

Subscriber Count

March 2017
« Feb