There appears to be a bug with vSphere Management Assistant (vMA) 5.5 and resxtop. Fortunately, there's a quick fix.
Run the following command within the vMA:
sudo mv /usr/lib/vmware-rcli/lib/ /usr/lib/vmware
You will now be able to run resxtop against a remote host:
I'm a Sr. Systems Engineer at a Global Environmental Engineering company. I've been in IT since 1999 and from 2005, my focus has been VMware datacenter products. More recently, my attention has been for Microsoft Azure services. As the Global Service Owner for VMware Datacenter products, I've had the pleasure of having in-depth and hands-on experience with not only VMware products, but server, storage and networking technologies.
Friday, February 14, 2014
Thursday, February 13, 2014
VMware vMA: BAD PASSWORD: is too simple
This week I deployed the vSphere Management Assistant (vMA) version 5.5. When entering the New password for the vi-admin user, I was "greeted" with the following error:
BAD PASSWORD: is too simple
Although the password I tried to use met our Domain Password Policy, it did not meet the complexity requirements for the vMA. The requirements for the vMA are:
Bit of background:
The vMA uses the Linux Pluggable Authentication Module (PAM). PAM along with CrackLib tests passwords to determine if they meet given complexity requirements. CrackLib prevents users from using simple passwords.
To disable CrackLib, perform the following steps:
***Always adhere to your company's Password Policy requirements***
1. Log into the vMA using the vi-admin account.
2. Run the Substitute User Do(sudo) command.
3. Run the following command to remove the cracklib requirement. Then Exit.
pam-config –d –-cracklib
4. Run the passwd command and enter your new password:
5. Test the newly applied password:
BAD PASSWORD: is too simple
Although the password I tried to use met our Domain Password Policy, it did not meet the complexity requirements for the vMA. The requirements for the vMA are:
- Eight characters
- One upper case character
- One lower case character
- One numeral character
- One symbol such as #, $
Bit of background:
The vMA uses the Linux Pluggable Authentication Module (PAM). PAM along with CrackLib tests passwords to determine if they meet given complexity requirements. CrackLib prevents users from using simple passwords.
To disable CrackLib, perform the following steps:
***Always adhere to your company's Password Policy requirements***
1. Log into the vMA using the vi-admin account.
2. Run the Substitute User Do(sudo) command.
3. Run the following command to remove the cracklib requirement. Then Exit.
pam-config –d –-cracklib
4. Run the passwd command and enter your new password:
5. Test the newly applied password:
VMware vMA: has no associated network protocol profile
Powering on a newly deployed vMA 5.5 from OVF prompted me with the following:
By default, the vMA is expecting a predefined set of IP address ranges (IP Pools). IP Pools are network configurations that is assigned to a network used by a vAPP. The VM can then use vCenter to acquire an IP.
If IP Pools are not used in your environment, disable vAPP from the VM properties to successfully power on your vMA.
By default, the vMA is expecting a predefined set of IP address ranges (IP Pools). IP Pools are network configurations that is assigned to a network used by a vAPP. The VM can then use vCenter to acquire an IP.
If IP Pools are not used in your environment, disable vAPP from the VM properties to successfully power on your vMA.
Monday, February 10, 2014
Windows Drivers for VMware Virtual Machines
Here's the quickest way I've found to get the latest Windows drivers for a VMware VM.
1. Download the appropriate version of the VMware tools ISO from the following site:
http://packages.vmware.com/tools/esx/index.html
2. Mount the ISO to a virtual CD drive. In my example, I used h:\.
3. Create a folder in C:\ called "extract".
4. Launch the command prompt and run the following command:
setup64.exe /A /P c:\extract.
5. Specify the location of the extract folder when prompted.
6. The windows drivers will be located in the following location:
C:\extract\Program Files\VMware\VMware Tools\VMware\Drivers
1. Download the appropriate version of the VMware tools ISO from the following site:
http://packages.vmware.com/tools/esx/index.html
2. Mount the ISO to a virtual CD drive. In my example, I used h:\.
3. Create a folder in C:\ called "extract".
4. Launch the command prompt and run the following command:
setup64.exe /A /P c:\extract.
6. The windows drivers will be located in the following location:
C:\extract\Program Files\VMware\VMware Tools\VMware\Drivers
Subscribe to:
Posts (Atom)