VMware


Yesss, VMware vExpert 2014!

I’m very honored to be awarded vExpert 2014! A vExpert is an active member of the community who impacts his or her knowledge on others. VMware uses the following explanation : “ A vExpert is not a technical certification, VMware selected people who engaged with their community and who had developed a substantial personal platform of influence in those communities. There were a lot of very smart, very accomplished people, even VCDXs, that weren’t named vExpert this year. “

 

image

You can find the full list of members here.

The proof :

image


VMware vCenter virtual appliance : schedule reboot

My experience is, in my whitebox environment to reboot the VMware vCenter virtual appliance from time to time. I used to do this manually but I decided to create a scheduled task. Hey we are IT people right? 🙂

vmware001

First login to the console with your password (I hope you changed the default root/vmware password combination :-))

vmware002

go to the /etc directory and open the crontab file

Edit the crontab (just press the i key for insert, and go to the bottom line).

As you see there are 5 options before the command :

  • minute (from 0 to 59)
  • hour (from 0 to 23)
  • day of the month (from 1 to 31)
  • month (from 1 to 12)
  • day of the week (from 0 to 6, 0=sunday)

If you use a * it means every, In my example every friday at 1 o’clock in the morning my appliance will reboot itself)


VSS error FAILED: Unable to create a VSS snapshot of the source volume(s). 2

I ran into a problem with VMware converter.  I got the following error :

unable to create a VSS snapshot of the source volume(s). Error code: 2147754774

The following steps worked for me :

Confirm that there are no errors with the following command :

vssadmin list writers

 

I found more then one provider with the following command :

vssadmin list providers

 

I deleted the second (everything but the first) provider (please back-up your keys first!) :

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Providers

I then did a restart of the VSS service (net stop vss , net start vss)

Followed by enabling shadow copies (and made a snapshot of the drive)

Now I was able to succesfully create VSS and import a running physical machine using VMware converter!