VMware Support Assistant is a must have FREE tool for your VMware vSphere installation.
Look at the VMware Site for more info on the VMware Support Assistant appliance.
During the installation at a customer site I found out that configuring the applicanse not always works as it should be. During the installation wizard where we make a connection to the SSO server I got following error:
Something failed. Try again.
A general error occured while attempting to acquire token from SSO service; will wrap and re-throw the exception. Re-trying the request might solve the problem; check the error details for more info A general error occured while attempting to acquire token from SSO service; will wrap and re-throw the exception. Re-trying the request might solve the problem; check the error details for more info Error communicating to the remote server https://MyServer:7444/sts/STSService/vsphere.local
Error communicating to the remote server https://MyServer:7444/sts/STSService/vsphere.local
com.ctc.wstx.exc.WstxIOException: Invalid null character in text to output Invalid null character in text to output Invalid null character in text to output
After some research I found out that it was a browser issue.
It does NOT work in the newest Chrome (version 37) on MAC and NOT on Internet Explorer on Windows 7.
It works on Internet Explorer 10 on a Windows 2008 R2 server.
After the configuration it is working perfectly now.
In a migration project to VMware vSphere 5.5 I bumped into duplicate MAC address issue (I found out after some investigation).
Some info on the setup.
There are ESXi hosts that we are migrating from 5.0 to 5.5. Some VM’s where 2 VM’s (VM1 and VM2) share the same MAC address (production and test machine).
On ESXi 5.0 these 2 VM’s can run together on the same ESXi host.
I want to move the VM’s to an already upgraded ESXi 5.5 host, the first VM (VM1 moves without any problems. ) For the second VM (VM2) I get following error during vMotion. Same error happens when I cold migrate the VM2 to the same host (ESXi 5.5) as VM1 and try to power VM2 on.
After some Google research I came across following blog
And adding the advanced setting to VM2 fixed the problem.
Before starting an upgrade at a customer site I was surprised how long an ESXi host can run. Here the proof.
A lot of my customers are running the vCenter Appliance version 5.1. Now they start to ask to upgrade this appliance to the newest version.
Here I will show you step by step the upgrade process. This is based on the VMware KB article 2058441
- Verify the time set on the old (VMware vCenter 5.1) appliance and the new (VMware vCenter 5.5) appliances are in sync. Be aware that from version 5.5 the clock on the appliance is always set to the UTC time zone. In the older version you could select your own tome zone. (see VMware KB)
- Be sure SSO (if installed on separate machine) is on the same version of the vCenter you want to upgrade to.
- If the vCenter database is external, make backup on the Database server. For backing up the embedded database look at this KB
- Create a snapshot of the OLD vCenter appliance before you start the upgrade procedure.
- First step of the upgrade procedure is deploying a fresh VM of the latest vCenter Appliance.
- Next is to configure the VM so that network connectivity is possible. The only thing that needs to be configured is IP address, subnet and gateway. The Original vCenter hostname and IP settings will be configured (copied) in the NEW vCenter Appliance based on the setting of the old vCenter.
- Connect to the old and new vCenter appliance via a supported web browser. (personal experience is that IE works and Chrome not! For the upgrade process.
On the NEW vCenter, Accept the EULA
- Next step in the upgrade process is to specify that you want to upgrade from a previous version
- Still in the NEW appliance, copy the local appliance code to the clipboard
On the OLD vCenter appliance, go to the Upgrade tab and paste the clipboard content in the text box and press the import button.
If the import was successful you get a notice and then copy the upgrade key back to the clipboard
On the NEW server paste the upgrade key in the bottom text box and proceed by clicking the next button.
There is an option to replace the SSL certificates on the NEW with those ones from the OLD vCenter Appliance
Now the new SSO password must be entered for the SSO administrator account email@example.com. (this was admin@system-domain in pre 5.5 versions)
Select now all the servers that need to check for compatibility with the new vCenter
After pressing next we see that we are ready to start the migration.
Pressing next will get following screen where you have to confirm that the upgrade process can proceed.
When you hit the start, the migration process start.
When you start the migration you will notice that the OLD vCenter server will be shut downed and the NEW vCenter server will have the IP configuration (hostname, IP settings) of the OLD ESX host.
After a successful upgrade you can start upgrading the ESXi hosts to the latest ESXi version.
- Can you login in the new vCenter Appliance via the Web Client and everything works fine you can remove the old vCenter Appliance from the inventory and from disk.
Since the last VMworlds VMware has re-launched the VCA certification. This blog will help you to get through the procedure of registration en starting the exam.
UPDATE: The Voucher code mentioned later in de blog is only giving 50% discount insted of 100% discount since 2 decmber 2013
Here the links to all e VCA certifications VMware has launched.
- VMware Certified Associate – Data Center Virtualization (VCA-DCV)
- VMware Certified Associate – Cloud (VCA-Cloud)
- VMware Certified Associate – Workforce Mobility (VCA-WM)
First of all you need to get trained to do get the certification. Use the links below on the above pages to get the FREE E-Learnings from the VMware Mylearn website. To get access you need to get a Mylearn account. Create account or login using following link.
Check the Blue Prints to see what the required knowledge is for each VCA exam by clicking on the following screen
After the preparations we are ready to register for the exam. You can do the exam online and do not need to go to a Pearson Vue center.
Use the links below to start the certification process for your VCA exam.
Following steps will guide you to the registration and start of examination for the VCA-DCV
Login into mylearn.vmware.com
Enter user and contact information
Registration is done. Give Pearson Vue up to 15 min to authorize you for the exam.. Also on the last screen you get a link that brings you to the trainings plan for this VCA exam.
Go to http://www.pearsonvue.com/vmware and login with your Pearson account to proceed the certification process
If the authorization is not yet happened you get following screen
After some refreshes of above screen the authorization came trhough
Click on the link to proceed.
- You see the exam normally cost some money. Later on in the registration process you can use above voucher code to get this for free. Read the requirements to execute the exam and proceed with the registration
Select the language and proceed with next
Proceed to the checkout and use the voucher code VMRT7B204E2E
Modify some personal info in step 1 of the checkout process and continue
In step 2 of the Checkout process you will agree with the policies
On the payment step DO NOT FORGET to enter the voucher code VMRT7B204E2E
Submit the order and get the receipt to start the exam
- On the receipt page you see the availability of the exam (24h) and the start button
Success with the certification and keep on going with VMware Certifications
When you succeed you will see following screen
During an upgrade at a customer site we removed a Dell Appliance that was connected to vCenter. We dit remove the aplliance just by powering it off and then remove it from the entry. Normally you should do an unregister from in the Dell Appliance.
Now we saw that there was a plugin that could not be loaded.
After some research on the internet I passed by on the website of William Lam (virtuallyGhetto).
He has written a nice article that describes step by step how to fix the problem we had. Look here.
Problem solved, thanks William for the good work.
Today I was asked to expand a local datastore of a ESXi 4.1. Expanding a disk is normally no problem when you are able to increate the size of the disk. After increasing the disk size you should be able to increate the partition size.
The ESXi was managed by a vCenter 5.0. On the storage adapter I did a RESCAN data stores after the disk size was increased. Then I went into the DATASTORE properties and I saw following
This above view was via a vCenter connection. Then I found following VMware KB which told me to make a direct connection to the ESXi host. After going to into the datastore properties I found out that I could increase.
When I selected this local datastore and finished the expansion I saw following result in the vSphere Client direct to the ESXi and via vCenter.
Lucky for the customer this expansion went OK.
Hopefully if you have this problem this KB article fixes also your problem.
Gert Van Gorp
Today 12th of July VMware announced a new suite of products. Look here for news release.
I the near future I will blog about this new release in a sort of “How to” format to introduce the new feature.
The suite consists out of following products.
A new product most of the time means, a new set of licenses. VMware moved from 6 different licenses to 5, they removed the Advanced license. Lucky for the owners of this license (with a active subscription, they will be migrated to Enterprise. Look here for the license paper
Here a list of vSphere 5 introduction links
VMware Cloud Infrastructure: http://www.vmware.com/cloud-infrastructure/
The Console Blog: VMware Unveils vSphere 5 and the Cloud Infrastructure Suite
VmwareTips: VMware 2011 Mega Launch
Virtual Geek: Raising the Bar V = vSphere 5!
vTexan: really cool things in vSphere5
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