Home » 2015 » March

Monthly Archives: March 2015

Forcibly remove failover cluster feature.

Forcibly remove failover cluster feature.

I was asked to take a clone of Windows 2008 server and release it to appliation team as a replacement server for another standalone Windows 2008 server. Clone was successfully completed and found that the source of the clone is a cluster node. Hence, I had to remove the filover cluster. As this was a virtual server I had the liability of disconnecting it from network and conencted using local admin account. Unfortunately, it was not allowing to uninstall cluster, it required AD authentication. Taking the server back to network and trying to remove the cluster was challenging as this had the possibilities of impacting the existing cluster setup. Sever Manager will not allow you to remove the cluster feature as its still a part of a cluster. Hence, I was then able to find a work around using the registry.

1. Take the complete backup of the registry.
2. Locate HKLM\CurrentControlSet\Services\
3. Delete the keys “ClusDisk” & “ClusSvc”
4. Now try uninstalling the Failover CLustering.
5. You will be prompted with “Have you removed this server from the cluster?”. Yes, I’ve removed this server from the cluster or No. I still need to remove this server from the server.”
6. Click on “Yes, I’ve removed this server from the cluster.”
7. Reboot the server.

You now has the liability of adding the same feature back and setup a new cluster.

Thanks,
WintelAdmin

VMware Error 0x0000005D

When you try to install Windows Operating System, you would come across an error code 0x0000005D. This is purely an issue related to the virtual machine profile. Please validate if you have selected a correct profile. if not please choose the correct profile and restart the installation process.

In my case, was trying to deploy Windows 2003 std edition for a legacy application using SCCM 2012. Had no clue with the error code 0x0000005D, though I have set Windows 2003 Std 32 Bit in profile. Later realized that the SCCM is using the latest version and then selected the corresponding 64bit profle like Windows Server 2003 Enterprise x64 Edition – from the drop-down list. Voila it fixed my issue.

VM profile is available at below path.

VM->Edit Settings->Options->General Options->Version

Regards,
WintelAdmin

Powershell Script to start/stop/disable service on multiple remote server

Powershell script to control windows service on multiple remote servers.

Get-content “Filename” | foreach {set-Service -ComputerName $_ -Name “Service Name” -StartupType Disabled -Status Stopped}

Note:
Replace Filename with filename location (Ex C:\hostname.txt).
Add all servers names to filesname (Ex hostname.txt)
Change StartupType as Disabled/Manual/Automatic
Change Status as Stopped/started

-WintelAdmin


Visitors Count

Subscriber Count

    3981
March 2015
M T W T F S S
« Dec   Apr »
 1
2345678
9101112131415
16171819202122
23242526272829
3031