Posts

Showing posts from July, 2014

VMware Client Error: Unable to contact the MKS or VMRC error

VMware VC Client Error: Unable to contact the MKS or VMRC error When we try to open the console from VC we use to get error on the TOP. To resolve this issue, remove the environment variable from the vSphere Client machine or vCenter Server:  Step 1:  Migrate the VM from existing esx to another esx. or Step 2: 1.     Click Start > Run, type sysdm.cpl, and press Enter. The System Properties window opens. 2.     Click the Advanced tab. 3.     Click Environment Variables. 4.     Remove any user variable and any system variable named User . 5.     Reboot Windows and launch vSphere Client. Step 3: If the issue persists, end any vmware-vmrc.exe processes in the Windows Task Manager: 1.     Close all vSphere Client sessions. 2.     Open Windows Task Manager. 3.     Search for any vmware-vmrc.exe processes and end the process. 4.     Start the vSphere Client and connect to the host directly or to vCenter Serve

VMware: How to Shrink a Thin VMDK on ESXi 5.0

Image
Many customer/service request we receive from our client is.. is it possible to reduce the disk? This means the files inside the VM, but the size of the VMDK as well.   So I wanted to shrink my VMDK size as much as possible.  After cleaning up the VM itself and running  sdelete , it’s time to shrink the VMDK. First let’s review the actual usage of it: The virtual disk size can be seen with  ls –lh *.vmdk .  In my example, I have a  40 GB  virtual size. To see the ‘real’ size of the vmdk, run  du –h *.vmdk .  This gives us a  36 GB  size (while the VM itself actually uses about 10 GB). Issue the command  vmkfstools –punchzero  VM.vmdk.  This will take a while so be patient (and oh yes, you VM must be powered off). On a 40 GB VMDK it took me about 10 minutes, but this will depend mostly on your SAN speed. After it’s done, let’s re-issue  du –h *.vmdk . Nice, now it’s actually  10.8 GB . 

Windows: iSCSI Target Server – windows 2012 server standard

Image
iSCSI Target Server – windows 2012 server standard   Error: Unable to import the virtual disk. A Virtual disk with that file path already exists When I try to import the virtual disk into Windows Server 2012 iSCSI Target Server, I encountered this error : Problem: The registration of virtual disk in iSCSI Target is not deleted properly in the registry . Solution: 1 . To v erify the iSCSI Target VHD that cause the issue Open Registry Editor and navigate to the following path      "HKLM\SOFTWARE\Microsoft\iSCSI Target\WTDisks" 2. Delete the value from the corresponding ID 7. Lastly, "Microsoft iSCSI Software Target" Service must be restarted . Verify the iSCSI Target VHD that cause the issue