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 am at customer site to upgrade en vSphere environment to the latest and greatest version of VMware vSphere 5.1.
We started the migration process by importing the VMware ESXi image we downloaded from the VMware download website.
In Update Manager we checked the server and saw that the server was not compliant with the new ESXi version so we could start the remediation.
After the remediation started we got the following message in Update Manager stating that the server was incompatible for this upgrade.
After some research on the internet I found following VMware KB 2034945 article.
As pointed out in this article the upgrade worked after a reboot of the ESX host.
As you can see on my blog it is been very quiet. I have been very busy doing some personal stuff.
It has also been quite busy as a Virtualization Consultant specialized in VMware. Had to do nice new projects, upgrades and a lot of healthchecks just before the upgrades.
The last year I have also done a lot of teaching VMware classes. As a VCI I also had to start teachig / learning new classes for vCloud / vCenter Operations Manager / vSphere Optimize and Scale and ofcourse the 5.1 courses.
I am also very busy with some projects for the next year. Stay tuned for more info on this
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
After reoganizing my life I was very happy to receive a mail from the vExpert Progam that I am one of the aprox 400 vExperts that are nominated for 2012.
Congrats to all that are (re)nominated.
Within these aprox 400 there are 3 kind of categories:
The Evangelist Path includes book authors, bloggers, tool builders, public speakers, and other IT professionals who share their knowledge and passion with others with the leverage of a personal public platform to reach many people. Employees of VMware can now also apply via the Evangelist path.
The Customer Path is for internal evangelists and community leaders from VMware customer organizations. They have contributed to success stories, customer references, or public interviews and talks, or were active community contributors, such as VMUG leaders.
VPN (VMware Partner Network) Path
The VPN Path is for employees of our partner companies who lead with passion and by example, who are committed to continuous learning and to making their technical knowledge and expertise available to many. This can take shape of event participation, video, IP generation, as well as public speaking engagements.
With this nomination I am again encouraged to go forward with my believe in VMware & Virtualization. This will be seen in coming blogs on this site.
I get a lot of questions of students and customers about resizing a virtual disk. This is the reason for this blog.
The following procedure will guide you step by step through the process of resizing (increasing) a disk of a virtual machine.
Before you make virtual hardware changes be sure you have taken a full backup of the virtual machine.
NOTE: If you do not want any troubles only increase the disk size. Decreasing can cause loss of data.
Increase Disk using diskpart
Step 1: Edit the virtual machine settings and increase the size of the disk (VMDK).
Step 2: Open the console of this virtual machine and start a command prompt.
Step 3: Start diskpart and execute following steps.
à this gives you a list of the available partitions
select volume x
à select the partition number you want to increase
à this will add the empty disk space into the partition.
Now the partition has increased in size.
NOTE: On Windows 2008 this can be done via the Device Manager / Storage, but I have seen some weird things like showing incorrect partition sizes.
Increase Disk using Third Party tool
Step 1: Be sure you have a boot image (ISO) of the Acronis Disk Director Tool that supports your guest OS.
Step 2: Boot your virtual machine using the boot image ISO. Use the ESC button during booting your virtual machine to activate the “one time boo menu”
Step 3: Select the partition you want to increase and right mouse click on it. Then select “Resize Volume”
Step 4: Increase the disk space of the selected partitions by decreasing the unallocated space to 0
Step 5: After increasing the partition you have to commit the changes.
Step 6: Now you need to reboot your virtual machine after disconnecting the boot image.
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
During a migration process from ESX to ESXi at a customer site we had a problem removing a server from the vCenter inventory.
We checked the permissions on this server and we saw that the user who wanted to remove the server was admin on datacenter level. Here the screen we got.
Knowing there is a PowerCLI command to remove a ESXi host from the vCenter, we walked that way with success.
I used this
PowerCLI script to remove this server from the inventory after moving the
server out of the cluster to the datacenter level.
Remove-VMHost “HostThatCannotBeRemovedViaGui” –confirm:$false
When you are using MS SQL Server in mixed mode, it is very important that you know your SA password.
There can be different reasons you lost the password
- Person who installed the SQL Server knows the password but has left the building.
- You did not write down the password in your password file
- Password file is lost
Steps to recover the SA password
Start SQL Server Configuration Manager
Stop the SQL services
Edit the properties of the SQL Service
Change the startup parameters of the SQL service by adding a –m; in front of the existing parameters
- Start the SQL services. These are now running in Single User Mode.
- Start CMD on tthe SQL server
Start the SQLCMD command. Now you will see following screen
Now we create a new user. Enter following commands
- CREATE LOGIN recovery WITH PASSWORD = ‘TopSecret 1′ (Remember SQL server has default strong password policy
- Now this user is created
Now we grant the user a SYSADMIN roles using the same SQLCMD window.
- sp_addsrvrolemember ‘recovery’, ‘sysadmin’
- Stop the SQL service again
Change the SQL service properties back to the default settings
- Start the SQL service again and use the new created login (recovery in my example)
Go via the security panel to the properties and change the password of the SA account.
- Now write down the new SA password.