Today on a customer site I had to upgrade the vCenter Operations Manager to the latest version.
The problem was that the password of the admin account was not known.
After some research on the internet (google is my friend) I found a VMware KB article that describes step by step how to recover.
The VMware KB number is 2013358
We had already vCenter Operations manager 5.7 running but the resetadminpwd.sh was not on the machine. I had to follow the steps as described for version 5.0.
Hope this will help you.
Today I received an email from a customer with the message that a message appeared on the Cluster summary tab.
Also on each host separately I saw that the information on CPU used and Memory used was frozen and set to ZERO
After some research on the VMware KB site, I did not find any solution.
Then I started to play with the DRS settings. I tried to set it from Fully Automatic to Manual with no result.
After that I disconnected the host and reconnected the host again, the CPU and Memory usage meters were getting active again.
Also the message on the DRS cluster disappeared.
Problem fixed and again a happy customer.
VMware vCenter Error Call “PropertyCollector.RetrieveContents” for object “propertyCollector” on vCenter Server failed
A customer of mine called me with a weird problem with a Template which was converted back to a Virtual Machine. See here the problem which occurs when the customer wanted to edit the settings of this VM.
The cause of this problem is that an ISO was mounted from a datastore which does not exist anymore.
To solve this problem, just connect to the ESX host where the VM is registered on. Edit the setting here and put the CDROM on “Client Device”.
Then check on which datastore the VM is located. Then unregister and register the VM again in the ESX host. Now you are able again to edit jthe setting of this VM via vCenter
On the VMware Labs website you can find a free appliance that can give you limited access to the management tools available in vSphere vCenter. The appliance is called vCMA or vCenter Mobile Access.
How to install?
- Go to the vmware.com/labs website and download vCMA as a OVF. Jump to site
- Extract the zip file that contains the OVF.
- In vCenter, go File – Deploy from OVF and point to the extracted OVF file.
- Once deployed, you can start the VM.
After the VM is started, there are 3 options to change settings
Using the menus on the console (to set network, timezone, login in to the command console)
Using the web interface https://vcma-host-or-ip:5480
Or using the command console. (use login in first screen)
- By default the root account has as password vmware (remember the console is by default in qwerty)
Special configuration settings to thing about!
- Set the IP to a fixed address
- Enter the DNS servers
- Change the default hostname and domainname. (http://communities.vmware.com/message/1335001)
- Change the root default password using the passwd, in the command console
How to use?
- It is very easy to start using this app.
- Open a browser (on you PC or mobile device)
- Point to http:// vcma-host-or-ip/vim (the folder /vim is needed and I hope VMware will change this in a next release)
- Enter the vCenter server name and the userID and password you normally use in the vcenter.
Now you can do some functions like
- Edit settings of a VM
- Change Powerstates of a VM
- Etc, install and discover.
Alternative apps you need to buy!
iDatacenter http://nym.se/idatacenter/ (iPAD)
iVMControl : http://itunes.apple.com/us/app/ivmcontrol-control-vmware/id404263941?mt=8 (iPAD, iPhone)
The upgrade to wordpress 3.05 did go as smooth as it should be. Website was completely corrupt. and as each good IT guy I had a backup (NOT). Copied all files that were still available, copied the WP 3.05 sources to my web host, then the config file back and everything in the contect dir (database was still ok) and lucky everything came up again. Only updating the plugins and finished I was.
I also added the WPTOUCH plugin so the website has a nice view on the mobilephones as iPhone and Android.
Any good backup plugis available? please recommend….
Doing a P2V is very easy using the VMware Converter (Standard / Enterprise). But after the machine has been migrated the P2V is not yet finished, we need to do some extra stuff.
- Remove all hardware related software via add / remove programs (if possible) or disable the service.
- Old unused devices should be removed using device manager after setting a special SET parameter (set devmgr_show_nonpresent_devices=1). This can be done manually are using a script.
- Update virtual hardware settings (CPU / Memory)
- Enter the IP configuration on the new NIC. (Can be automated)
- Depending on the MS license you are using you maybe need to reactivate.
Some software vendors are licensing there product according the amount of CPU’s there are in you server (Physical or Virtual).
Each vCPU you add in a VMware Virtual Machine is seen as a kind of “physical socket”. This means that if you add 4 vCPU’s in your VM and you need to install software where the software is licensed on CPU SOCKET, you have to pay for 4 CPU’s.
VMware has a advanced setting that makes this 4 CPU SOCKET machine look like a Quaqcore SOCKET, which means only 1 CPU SOCKET.
How to change this setting? Look at VMware KB article 1010184
VMware is working on a new SRM version in the labs. if you want to know more on SRM goto VMware SRM
I will give you here some product higlights (can change because product is still in devellopment.
* both sites (protected and recovery) are visible in 1 interface. Communication will be encrypted between sites. Certificates can be used.
* Array Managers for both sites can be configured from within one SRM UI. There will be tight integration towards storage.
* SRA interface will be available for each adapter. This will give you a overview of the arrays.
* Array Diagnostics is available to have an overview on storage connections
* Protection groups can be organized in folders
* Protection groups are available for both sites. This to enable failback.
* Protection groups will give of status of individual VM’s.
* Recovery plans are available for both sites to support failback.
* Quick summary for recovery plan and last operation.
* VM startup order can be set in recovery plann
* You can create VM dependencies. Can also start scripts before and after a VM poweron
* IP Custimazation can now be set in VM configuration. You can set een ip config for protected and recovery site.
* Also IPv6 support.
* Possible to do a planned failover. This will assure no data loss dureing migration. This is possible because of tight integration with storage.
* Dashboard will show evolution of the failover on VM level.
* after a failover a Reprotect can be done so a failback can be done without losing data. SRM will tell to the storage to start replication the the other way. A status can be follwoed.
Looking at all these new features, we can hope this version is launched very soon??
Nice work VMware, go on.