Home » Windows(2003/2008/2012) (Page 2)

Category Archives: Windows(2003/2008/2012)

VMware Virtual Machine Reporting from VSphere

VMware PowerCLI is a powerful utility to generate virtual machine information and status. This is very cool and handy tool. I use to generate VMTools status, Datacenter and ESX host name information.

Command to connect vCenter:

Connect-VIServer vcenter1, vcenter2, vcenter

Initialize VMTools Version:
New-VIProperty -Name ToolsVersion -ObjectType VirtualMachine -ValueFromExtensionProperty ‘Config.tools.ToolsVersion’ -Force

Initialize VMTools Status:
New-VIProperty -Name ToolsVersionStatus -ObjectType VirtualMachine -ValueFromExtensionProperty ‘Guest.ToolsVersionStatus’ -Force

Verify VMTools status on all virtual machines and export the output to excel:
Get-VM | Select Name, ToolsVersion, ToolsVersionStatus | Export-Csv -NoTypeInformation -UseCulture -Path C:\Temp\VMToolsInfo.csv

Export VM name, cluster and ESX Host:
Get-VM | Select Name, @{N=”Cluster”;E={Get-Cluster -VM $_}}, @{N=”ESX Host”;E={Get-VMHost -VM $_}} | Export-Csv -NoTypeInformation C:\temp\VM_CLuster_Host-.csv

Export VM name and Cluster name:
Get-VM | Select Name, @{N=”Cluster”;E={Get-Cluster -VM $_}} | Export-Csv -NoTypeInformation C:\temp\test-VM_CLuster.csv


Error: Could not access VBscript run time for custom action.

Recently got an update from the application team that they are unable to install and software. When executing the setup file they are getting an error pop-up window stating “Could not access VBscript run time for custom action.”. This issue was fixed using below steps:

1. Open Registry Editor” and locate the below key.


2. Expand {B54F3741-5B07-11CF-A4B0-00AA004A55E8} key, locate InprocServer32 and click on it.
In the right column you should see two values.

3. Right-click InprocServer32 > Permissions > Advanced > Permissions > highlight Administrators, choose Edit > and in the Permissions check box next to Full Control; Save all changes;

4. Then in the right column or Registry Editor right-click (Default) > Modify, and insert the correct path in Value Data:


5. If you have 64-bit Windows repeat steps 3 – 5 for next registry keys:



6. After that close Registry Editor.

After the above changes when we tried executing the same setup it went success.


VMware Tools is no more depended on vSphere/Esxi release.

VMware tools 10.0.0 is now no more dependent on vSphere release/Esxi builds. I think this is the first time when VMware released VMware Tools separately. As per release note its backward compatible, compatible with Esxi 5.0 and also compatible with Workstation 12.0 and VMware Fusion 8.0. It will allow to get the latest new features and enhancements made to the VMware tools faster to the customers.

You can download and install the latest version of VMware Tools from Here.


Enable Time Synchronization Between Windows (VM Guest) and ESX (Host).

This is in continuation to my previous post RDP Connection on a virtual server

As discussed earlier there was an issue with the AD authentication and connectivity. It was all because of the different time zone set on an ESX host and the guest operating system. Changing time on DC was not recommended by the AD Team as the impact was unknown and similarly we have no clue on the impact due to time change on ESX cluster. Hence, I decided to manually do the time sync between the ESX host and Guest machine.

Time sync status was validation using the command:
VMwareToolboxCmd.exe timesync status

Enter the command to enable or disable periodic time synchronization.
VMwareToolboxCmd.exe timesync Enable/Disable

We executed below command to fix the issue
VMwareToolboxCmd.exe timesync Enable

Note: VMTools installation directory on Windows is C:\Program Files\VMware\VMware Tools.


RDP Error – The connection cannot be completed because the remote computer that was reached is not the one you specified. This could be caused by an outdated entry in the DNS cache. Try using the IP address of the computer instead of the name.

Unable to connect to the Remote Desktop. Server operating system is Windows Server 2012 Standard R2. When we try to RDP, we get the below error message:

The connection cannot be completed because the remote computer that was reached is not the one you specified. This could be caused by an outdated entry in the DNS cache. Try using the IP address of the computer instead of the name.

There was two server with same configuration and setting but one of connecting to RDP with AD authentication whereas the other was not working. One was physical and the other was virtual hosted on an ESX host.
RDP on physical was good and the issue was with the virtual host. It was confirmed that the issue was due to time latency.
Therefore, this issue was due to the time difference between the virtual machine and the NTP server set on an ESX host.
This issue was later fixed by synchronizing the server time with the ESX host.

If you do not wish to have auto sync, disable the Windows Time service or block the outbound port 123 on your local firewall.


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.


Windows 2012 Network Share: The specified network name is no longer available

Shares created on Windows Server 2012 R2 are are inaccessible from Windows XP, Windows Server 2003 or Windows Server 2008.

When you try to access the share you will get an error message stating “The specified network name is no longer available”. Windows 2012 will not accept traffic from an older operating systems.

In rorder to fix the issue, a registry setting on Windows Server 2012 R2 must be modified as listed below:

Back up the Registry Hive/Key and make the following change:


Original Value: SamSS Srv2

Change to: SamSS Srv

Note: Just delete the 2

After making the change, reboot Windows Server 2012 R2

Note: You may also need to reboot the clients/servers involved


RDP issue, Port No 3389 not listed under netstat

Came across an issue, where users were unable to connect to the Windows 2008 using RDP. When checked the RDP port 3389, its not listed under netstat -ano. Therefore, tried uninstalling the remote desktop services and reinstalled it multiple times. Was still unlucky and issue persists.

Finally was able to fix the issue by deleting the terminal services connection and recreating it.

1. Open “Remote Desktop Host Configuration”.

2. Delete the RDP-tcp.

3. Create a new RDP listener.

Voila! was able to connect to RDP instantly.


Script execution error code 80070005 on Windows 2012

Recently found that some of the our maintenance VB script used for placing servers in Maintenance mode on SCOM were not working and were throwing errors as listed below:

Error: Invalid root in registry key
Code: 80070005
Source : WshShell.RegWrite

Well, found that the same script is working fine when executed as Run as Administrator. Validated the UAC and found that its already disabled on control panel.

Later its found that, disabling UAC will not help in executing the scripts and the UAC has to be disabled in registry by following below steps:

1. Open registry using “regedit”.
2. Browse to the following registry key:
3. Double-Click the EnableLUA Key on the right and Change the value data from 1 (UAC Enabled) to 0 (UAC Disabled).



Windows Server 2008 keeps rebooting to repair mode.

Today, one of the Windows 2008 server was rebooted and the server was not back online after the expected time. When checked the console, server was on to Windows repair mode. On multiple reset and reboot the scenario was same. Server was keep on login to repair mode. Laer, I was success in fixing the issue following the steps listed below:

Booted the server using the DVD or any bootup media.

Run sfc /scannow /offbootdir=f:\ /offwindir=f:\windows

If this does not fix the problem, continue with below steps:

Loaded hive into the registry:

1. Open Registry Editor.
2. Click either the HKEY_USERS key or HKEY_LOCAL_MACHINE key.
3. On the File menu, click Load Hive….
4. Select System file from “c:\windows\system32\config”.
4. Find the hive you want to load and click it.
5. Click Open.
6. Key name as TEST

Checked with the currentcontrolset001

Unloaded the hives

Rebooted the server normally and the issue is fixed.


Visitors Count

Subscriber Count

May 2017
« Apr