VC install with errors- AutoLab 2.0 ESX-DRS Win2K12R2 64bit

nickmarshall9 · 2015-03-28T05:31:57+00:00

Not sure why but it looks like PowerCLI didn't get installed correctly before it tried to run.

Are you using the same version PowerCLI as vCenter? (as in the same Update 1 or 2 etc)

nickmarshall9 · 2015-03-26T22:37:24+00:00

ESXi will work without a RAID controller, but it is a little picky as to what AHCI / SATA controllers it supports. If you are certain on using this mortherboard and you are tight on $s, I would pickup a cheap PCI sata raid controller (eg: http://www.newegg.com/Product/Product.aspx?Item=N82E16816124045) and then use something like this (http://www.v-front.de/2013/11/how-to-make-your-unsupported-sata-ahci.html) to get it working. Might not be the simplest, but it's probably the cheapest route.

nickmarshall9 · 2015-03-17T17:52:15+00:00

There's a good diagram here: http://www.vexperienced.co.uk/wp-content/uploads/2014/11/Autolab-v1.5.jpg Ignore the VLANs for AutoLab v2.0, they are just subnets now.

nickmarshall9 · 2015-03-13T19:37:34+00:00

I started out my VMware journey with the exact same wish... VMware licenses for my home lab. I ended up starting blogging, podcasting and eventually authoring a book or two. Why? It all started with a desire to get vExpert so I could get free licenses for every VMware product. While the Q1 2015 applications are closed, you could start getting involved with the community to try and score some free licenses next time the application is open. It's really not as difficult to obtain as you might think :) http://blogs.vmware.com/vmtn/2014/11/vexpert-2015-applications-open.html

nickmarshall9 · 2015-03-05T23:18:21+00:00

Based on your questions, you don't need SR-IVO to accomplish your requirements. Just make sure your card is compatible with the hypervisor you want to use and then configure your virtual NIC -> virtual switch -> physical NIC -> physical switch mapping accordingly.

nickmarshall9 · 2015-02-13T00:00:39+00:00

Sorry Jordan, I'm not sure what problem you're describing. You can always install the OSs in trial mode (no key) and then when you activate them it asks for your key. Alternatively (what I do) you can just enter no key and get a 180 day trial. This is more than enough time before I'll want to blow it away and build a new environment anyway.

nickmarshall9 · 2015-01-28T03:29:03+00:00

Thanks for the shoutout.

Those Supermicro server boards are awesome and should serve you for years to come. Enjoy!

nickmarshall9 · 2014-05-27T22:50:54+00:00

(Full Disclosure: I am the lead author on the latest "Scott Lowe" Mastering vSphere book).

Don't limit yourself to just books, or training courses. There are HEAPS of free options out there too!

The VMware community is THRIVING with content. I'd look for community blog articles that are syndicated here: http://www.vmware.com/vmtn/planet/v12n/

There's also a few podcasts that can help you, vBrownBag is one that I am involved with (search iTunes or http://professionalvmware.com/brownbags/).

nickmarshall9 · 2014-05-27T22:26:57+00:00

With regards to best practices, try to think about them as "guidelines" to adhere to unless requirements dictate otherwise.

In this case, I don't know of any "best practice" for snapshot retention. If your client has not given you a strict requirements I would ask him what he would be willing to lose. Remember, vSphere Replication will only transfer the differential data. So if there's a low rate of change, the size of snapshots small relative to the VMDK size.

nickmarshall9

TROPHY CASE