Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
It's just a regular exe installer that has to be installed on a 64-bit OS. Win7 isn't supported though, has to be either XP x64, 2k3 x64, or 2k8 x64: http://kb.vmware.com/selfservice/mi...nguage=en_US&cmd=displayKC&externalId=1022101
You'll also need SQL express for the backend, which can be installed on the same box.
It comes as a 60 day free trial if you don't put in a license key. After that, rebuild again for another 60 days. Unfortunately VMware doesn't have a good licensing option that is similar to Technet...I really wish they did. It would make it so much easier for those of us who run it for home labs
How much are you spending on technet to have your own home lab?
It's bundled with it. So you can have it install sql express on the same box or point it to another instance. For home lab purposes the sql express install works fine.Does it install SQL express itself or do you need to do that separately?
Yes, a lot of people use virtualized vCenters. That's the current VMware best practice since you can protect it with HA and FT. I have several small customers using SQL Express in prod..just be careful you don't hit the 10GB database limit. There is a sizing tool to estimate your DB size after a year that's useful for checking that.
what fills up the database, is it the performance logs?
This is what happened to us. We run vCenter as a VM in prod, but filled up the DB pretty fast. When upgrading from 3.5-->4.1 I moved to regular SQL, but the actual service runs great in a VM.Yes, a lot of people use virtualized vCenters. That's the current VMware best practice since you can protect it with HA and FT. I have several small customers using SQL Express in prod..just be careful you don't hit the 10GB database limit. There is a sizing tool to estimate your DB size after a year that's useful for checking that.
This is what happened to us. We run vCenter as a VM in prod, but filled up the DB pretty fast. When upgrading from 3.5-->4.1 I moved to regular SQL, but the actual service runs great in a VM.
Just be careful if you run vCenter virtualized along with Distributed switches on your hosts. You can run into problems if vCenter goes down since you can no longer assign VM's to the dvswitch port groups.
Try removing the vpxuser account from that host and then re-adding it. I've seen that error before and I believe that fixed it.
Are these ESXi 4.1 hosts btw?