Posts Tagged ‘VMware’

VMware ESXi Update Failed: Cannot run upgrade script on host.

December 30, 2014

I faced some problems while upgrading my VMware infrastructure from ESXi 5.1 to 5.5. On one of the server; the remote and manual update both failed and resulted in error:

Cannot run upgrade script on host. 

Upon exploring the issue; came across a KB article that suggested to move the boot sate file up a folder level. But that didn’t helped either. The issue was only solved when the H/A agent (VMware FDM) was removed manually. Although there were other servers in the cluster with agents installed and they upgraded seamlessly. Anyhow the manual uninstall solved the issue. Following snapshot shows the commands on how to uninstall the VMware FDM agent manually.

Update Fail Issue ESXi

vSphere Design Pocket Book

September 13, 2013

f224e-01-cover

Came across this eBook today and finished it reading almost two times on the go. Its basically a combination of tweets by VMware tech evangelists/experts giving away some very valuable tips and tricks on ESXi, vSphere, clustering, hardware considerations and resource allocation. I surely will start to follow these guide lines for my data-center. Thanks to PernixData; its available as a free download. You can access it here.

 

VMware Standalone Converter 5.1.0: Error: Unable to obtain hardware information for the selected machine.

May 29, 2013

converter

With updating of VMware Infrastructure to 5.1; I also installed the latest Standalone Converter 5.1.0. While doing P2V conversions with Windows Server 2008 R2; I faced a few problems.

With Converter 5.1 Build 1087880: Was constantly getting the error:

Unable to obtain hardware information for the selected machine.

I made sure to follow the checklist given on VMware KB 1016330 but to no avail. Hence reverted all the changes I did according to the given list.

With Converter 5.0 Build 470252 (as used that version previously with success but with vCenter 5.0): Surpassed the initial error but when pointed to my vCenter 5.1; the Converter would stop responding and get crashed.

I then finally resolved the issue by using Converter 5.0.1 Build 875114. Worked like a charm!

I still haven’t figured it out what could be the issue!  But for now the Converter 5.0.1 is working great with vCetner 5.1 Update 1. But I did figured out the following steps bears no fruit;

  • VSS Shadow Copy service on source machine does not need to be on.
  • Third Party antivirus or backup services on source machine need not to be stopped.
  • Simple file sharing on source machine need not to be disabled.

 

LDAPS Identity Source for VMware vCenter Single Sign On 5.1

May 21, 2013

ldap-logo

Once you are done with installation of VMware vCenter 5.1; you will notice that vSphere 5.1 client wont let you login into your vCenter Server. Either you will need to configure a local admin ID on your vCenter Server or if you have an active directory (AD) running in your environment; you will need to link that to your vCenter Server i.e. by configuring an identity source.

During installation of vCenter Single Sign On 5.1; it tries to add the identity source but in my case resulted in error (Error 29155.Identity source discovery error). I then found out its the case with other users as well and also was pointed out in VMware in their KB articles. The workaround for the issue given was to add the identity source manually. Doing so I got the following errors.

[LDAP: error code 8 – 00002028: LdapErr: DSID-0C0901FC, comment: The server requires binds to turn on integrity checking if SSL\TLS are not already active on the connection, data 0, v1db1]

and

simple bind failed:yourdomain:636

These errors are due to the fact that your AD is configured to communicate over LDAPS SSL connection. Hence to register your identity source; you will need the X.509 certificate of your AD domain controller (DC). For that export the certificate of your AD but make sure its the Base-64 X509 Certificate.

Cert 03

Once imported; again add the identity source as demonstrated below.

LDAPS

Once you chose the certificate from Choose Certificate tab; make sure you get the following confirmation. If not there must be something wrong with your certificate.

certsucc

You can click on Test Connection to verify your AD connectivity.

connecsucc

If you are still facing problems in adding the identity source; make sure of he following things:

  • Your vCenter, vSphere, vSphere Web Client, vCenter SSO etc must all be installed in the same default directories.
  • Do add the port 3269 with your FQDN.
  • There must a proper forward and reverse pointer entry on your DNS for your vCenter Server.
  • Enter the complete user name for authentication e.g. user@domain.com
  • If your domain controller is behind a firewall; make sure you have configured a policy to allow vCenter traffic.

Installation of VMware vSphere 5.0

September 29, 2012

So folks here is another of the VMware series blog I promised. The first one was about the setup of the VMware ESXi 5.0. This time am going to tell you about how to install the VMware vSphere 5.0 which you will use to log into your ESXi server. And here’s how you would be able to do that.

1.   To install VMware vSphere take any network PC with Windows XP/2003Srv/2008Srv/Vista/7 (32 bit or 64 bit), minimum 600 MB free space and minimum of 2 GB ram. Locate the setup file having the name “VMware-viclient-all-5.0.0-455964.exe” and double click it.

2.   Click Run to bypass the security warning.

3.   Setup will start extracting the files.

4.   Select the installation language and click OK.

5.   Click next to begin installation procedure.

6.   Click Next to agree to end-user patent agreement.

7.   Click “I agree to terms…” to agree to VMware end-user license agreement and click Next.

8.   Enter the required information and click Next.

9.   Browse to the destination installation folder and click Next.

10.   Click Install to begin the installation.

11.   Click finish to complete the installation.

12.   An icon for vSphere client will appear on your desktop. Double-click on it to launch the vSphere client.

13.   Enter the credentials for the virtual host machines and click login.

That all folks! Enjoy!


%d bloggers like this: