Thursday 30 October 2014

VMware tools installation will fail with Error - The Microsoft Runtime DLL installer failed to complete installation

Came across this issue during a P2V migration of a Windows 2008 machine. 

Issue : VMware tools installation will fail with Error " VMware Product Installation" - "Setup cannot continue.  The Microsoft Runtime DLL installer failed to complete installation."

The Logs for the VMware tools is located in temp Directory of the Machine as vminst.log. You can access the log by typing %temp% in the Run window.

* BootStrapper-build-1734305| ** InstallVCRedist [vcredist_x86.exe][ /Q]
* BootStrapper-build-1734305| Found 
"C:\Users\vmadmin\AppData\Local\Temp\{81330AE8-6050-4FD6-8271-BA97348C4118}~setup\vcredist_x86.exe"
* BootStrapper-build-1734305| Attempting to launch ""C:\Users\vmadmin\AppData\Local\Temp\{81330AE8-6050-4FD6-8271-BA97348C4118}~setup\vcredist_x86.exe"  /Q"
* BootStrapper-build-1734305| Child exited with code 1603
* BootStrapper-build-1734305| Process returned 1603
* BootStrapper-build-1734305| Launching VC dll installer failed with 1603.
* BootStrapper-build-1734305| DisplayMessageBox: "VMware Product Installation" - "Setup cannot continue.  The Microsoft Runtime DLL installer failed to complete installation."

How the issue was fixed:

1) When looked at the log file, the error indicated that "vcredist_x86.exe" was not being installed and this caused the Installation to fail.

2) Downloaded the file from Microsoft website and tried installing the file which also failed.

3) Tried installing Windows updates, which was not done for a long time.There were around 100 updates that had to be installed and strangely all of the udpates failed.

4) As a last step we tried doing chkdsk and it complained that the disk was in use and it would schedule the scan the next time of restart.

5) Okay, so we went ahead with the resart of the VM and during bootup there was the message, " CANNOT OPEN VOLUME FOR DIRECT ACCESS".. WOW now that was a error message that I had seen first. 

6) So, we felt it was some service that was locking the disk that was causing the issue and a quick search on the internet pointed torwards the Anti-Virus software causing the issue.

7) Logged back into the OS and to be on the safe side, uninstalled the Anti-virus. Enabled the chkdsk and restarted the Machine. There it was the same error message. :-( 

8) Atlast, I thought let me connect the Drive to another machine and do chkdsk maybe it might help.I shutdown the VM, and in the vCenter Inventory, selected another 2008 VM. In the Edit Settings, selected " Add Disk" browsed through the datastore and added the VMDK of the faulty VM as the second disk.

9) Logged into windows,the disk was offline brought the disk online and when I ran a chkdsk there it was . The disk had a lot of invalid entries which started getting fixed. Once this was completed. I shutdown the VM. Removed the VMDK and Powered on the faulty Virtual Machine. During the bootup, chkdsk ran by itself and fixed some more entries.

10) After a while, Windows came and VMware tools installation completed successfully.

Hope this info helps.

xx

Saturday 31 May 2014

P2V Migrations using VMware Converter - Things to remember

P2V migrations needs Planning and Preparation if you need to be successful. So, I wanted to consolidate some of the helpful links around P2V Migration and share my experience.If you have any feedback\suggestions, please feel free to comment  or contact me and I will add any additional information.The majority of the steps mentioned here are for Windows Machines. 

Helpful Links:

1)  Best practices for using and troubleshooting VMware Converter (1004588)

2) Converting a physical or virtual machine with VMware Converter takes longer than expected (1038454)


3) Disabling SSL encryption on VMware Converter Standalone 5.x (2020517)

This article helps if the Migration is taking very long.

4) Virtualizing existing domain controllers in VMware vCenter Converter (1006996)



Steps to remember before Migration:


1) From my Experience I have realized that it's best keep the configuration of the Physical Sever for the VM untill the first power on is completed and VMware tools is installed. Once Installed we can then reduce the VM configuration in terms of CPU, RAM and other devices.


2) Always have the following information handy before you start the Migration:

a) No of CPU's. How many Sockets and Cores.
b) Size of Memroy
c) How many Network Cards and which network on the ESXi Server.
d) Which Datastore to store the VM.
e) Location of the VM in the vCenter Inventory - Cluster and Folder.
f) If you think the Migraton will take time then the Final Synchronization time.
g) IP address of the Physical Machine - ipconfig /all should give you the result.

3)  Logging in as the Local Administrator is always good, however if you don't have the Administrator password. Ensure that you have logged in as a domain Admin atleast once before the Migration.

4) Install the VMware Converter locally on the Machine and star the Migration.During the end of the configuration ensure that you have disabled all Network is disconnected.

5) Ensure that you enable Final synchronization ideally Immediately if possible or schedule for a later time.

Note: that if you are doing a file clone i.e reducing the size of the disks you cannot synchronize the changes.

6) Once the Migration is complete, power on the VM with the Network card disconnected. Login to the VM and wait for the device detection to complete. You should see an icon in the Taskbar bar showing the progress.Be patient once the CD is detected you can mount the VMware tools. Install VMware tools.

NOTE: For Windows 2008 and older Machines, it is a good idea that you copy the VMware tools folder on the desktop as I have seen that it takes multiple attempts for the CD drive to be detected after the Migration. So, if you already have the VMware tools on the Desktop you can start the tools install even if the CD drive did not get installed.

7) Go to Device Manger. View => Show Hidden Devices.Remove any devices that are not relevant in the VM. In the VM properties, remove any unnecessary devices like floppy or USB.


8) Assign the IP address using the Information you had collected earlier. Shutdown the VM.

9) Power on the VM with the Network connected and wait for the VM to come up.

xx

Friday 30 May 2014

vCloud Director 5.5 - Configuring vCloud Director - Module 5 - Part 1

vCloud Director 5.5 - Configuring vCloud Director.

Module 1 - vCloud Director 5.5 - Deploying VC Appliance v5.5
Module 2 - vCloud Director 5.5 - Deploying vCloud and vShield Appliance
Module 3 - vCloud Director 5.5 - Preparing for vCloud Deployment
Module 4 - vCloud Director 5.5 - Preparing vShield and vCloud Director
Module 5 - vCloud Director 5.5 - Configuring vCloud Director - Part 1  

In this module lets start with the configuration of vCloud components so that we can deploy vApps.

DVSwitch configuration:


1) If you have not completed the Network uplink configuration the following slides will         help you with it.If you have already completed the configuration, you can skip this           configuration. Figure 1.

Figure 1: Adding ESXi hosts.

2) Click on Add Hosts. Figure 2.
Figure 2: Click on Add Hosts.

3) Select the 2 ESXi hosts that were added to the VC. Figure 3.
Figure 3: Select the ESXi servers.

4) Select "Manage Physical Adapters" and click Next.
 Figure 4: Select "Manage Physical Adapters".

5) Select and verify that the Correct uplinks have been assigned. Figure 5.
Figure 5: Assign the correct uplinks.

6) If there are any impact to your existing environment, the next screen should       
    highlight it.Figure 6.
Figure 6: Verify if there is any impact to the services.

7) Review the Information and click Finish to complete.Figure 7.
Figure 7: Review the configuration and click Finish.

vCloud Director Configuration:

1)  Let's start with the vCloud Director Configuration after which we will be able to build      and deploy our vApps. To start with, lets first add our vCenter to the vcloud            
     Director.Click on Attach a vCenter Figure 8:
Figure 8: Select Attach a vCenter.

2) In the next screen enter the relevant details of the vCenter.Figure 9.
Figure 9: Enter the relevant details of your vCenter.

3) Enter the details of the vShield Manager.Figure 10.
Figure 10: Enter the details for vShield Manager.

4) In the next screen. Review the details and click Finish. Figure 11.
Figure 11: Review the details and click Finish.

5) The great thing about configuring vCloud Director is that the home screen shows
    us which tasks have been completed and which needs to be completed. Now the    
    home screen will have green check mark next to the vCenter server as the    
    configuration is completed. Next we will create a Provider vDC. In the Home screen 
    Click on " Create a Provider vDC". Figure 12.
Figure 12. Click on Create a Provider vDC.

6) Enter the name for the Provider vDC and a short description. Select the Enabled option     and select the lowest version of VM Hardware that would run in your environment.Click     Next. Figure 13.

Figure 13: Enter a name for the PvDC.

7) Select your vCenter and the appropriate Resource pool, in my case "Resource" to deploy    the vCloud VMs. Click Next.Figure 14.
                             Figure 14: Select the Resource Pool for VM deployment.

8) Add the Storage Policy that we had created earlier.Click Next. Figure 15.
  Figure 15: Select the Storage Policy created earlier.

9) Enter the Credential for the Esxi Servers. Figure 16.
Figure 16: Enter Credentials for Esxi hosts in the vCenter.

10) Review the Summary page and click Finish when completed.Figure 17.
Figure 17: Review the Summary Page and click Finish.

11) The Next Step is the Create an external Network. Go back to the Home Screen and 
     click on "Create an External Network". Figure 18.
Figure 18: Create an External Network.

12) In the "New External Network" screen select your vCenter and this will bring up all            the Network's available. I am selecting the vCloud-PG. Figure 19.
Figure 19: Select the Portgroup already created in vCenter.

Figure 20: The Portgroup that was selected in the previous steps for reference.

13) Enter the Network details appropriate for your environment.Figure 21.
Figure 21: Enter the Network details.

14) Verify the details in the next screen. Figure 22 and Provide a meaningful name for the network.Figure 23.Review the Final screen and click Finish. Figure 24.
Figure 22: Verify the network details. 
Figure 23: Enter a name for the network.
Figure 24. Review the final screen and click Finish.

Create a New Organization:

15) In the Home Screen, click on "Create a new organization".Figure 25.
Figure 25: Create a new Organization.

16) Provide a name for the Organization and the description.Figure 26.
Figure 26: Provide a name for the organization.

17) Since, I do not want to integrate my vCloud with Active Directory now, I will select " 
     Do not use LDAP". Click Next. Figure 27.
Figure 27. Select "Do not use LDAP"

18) The next screen will prompt you to add a new User for Managing the Finance 
     Organization.I have created a user call Finadmin and assigned him the role of 
     Organization Administrator.Figure 28.
Figure 28. Create a user for the Organization.

19) I will come back to the Catalog option later, for now keep the default(nothing 
     checked) and click Next.For Email Preferences,Figure 29.Keep the Policies to the 
     Default and keep Next. Figure 30.
Figure 29: Keep the defaults.Click Next.
Figure 30: Review the Policies.Click Next.

20) Review the Entire Configuration and Click Finish. Figure 31.
Figure 31. Review the Configuration, Click Finish.

xx