aaronwsmith's Accepted Solutions

I figured out the problem, and documented the findings in my blog post here: Troubleshooting Expired PSC Certificates with vSphere 6 | Virtually Understood
What version of FreeBSD?  Check the compatibility matrix to ensure it's fully supported by ESXi 5.1, including VMXNET3: http://www.vmware.com/resources/compatibility/vcl/result.php?search=FreeBS... See more...
What version of FreeBSD?  Check the compatibility matrix to ensure it's fully supported by ESXi 5.1, including VMXNET3: http://www.vmware.com/resources/compatibility/vcl/result.php?search=FreeBSD&searchCategory=Guest+OS For example, FreeBSD 7.4 does not support VMXNET3 under ESXi 5.1: http://partnerweb.vmware.com/comp_guide2/detail.php?deviceCategory=software&productid=17579&supRel=76,168,171,187&vcl=true&testConfig=16 In contrast, FreeBSDE 9.0 supports VMXNET3 under ESXi 5.1: http://partnerweb.vmware.com/comp_guide2/detail.php?deviceCategory=software&productid=17596&supRel=171,218&vcl=true&testConfig=16 Also, what version is the virtual hardware running this VM?  VMXNET3 is available in v7 and later: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1001805
Are you running ESXi 5.0 Update 4? http://kb.vmware.com/kb/2006859
That's odd.  Can you take a screenprint of what you can see from the Administration page? Also - Can you try any of your logins you previously mentioned via the Web Client and see if you're ab... See more...
That's odd.  Can you take a screenprint of what you can see from the Administration page? Also - Can you try any of your logins you previously mentioned via the Web Client and see if you're able to login?  Perhaps one of those IDs is now the SSO admin ID.
This command will show you all packages within your Image Profile that are not Stateless Ready: Get-EsxSoftwarePackage | ? { $_.StatelessReady -eq $False } Add/Removing packages from a cust... See more...
This command will show you all packages within your Image Profile that are not Stateless Ready: Get-EsxSoftwarePackage | ? { $_.StatelessReady -eq $False } Add/Removing packages from a custom image profile requires you to create a variable referencing that profile.  Let me know if you need more specifics.  For now I'll assume $customProfile points to your image profile and now you want to remove the non-Auto Deploy friendly packages from it: Get-EsxSoftwarePackage | ? { $_.StatelessReady -eq $False } | Remove-EsxSoftwarePackage -ImageProfile $customProfile On the flipside, if you're building a fresh image profile and don't want to add any packages that are not StatelessReady: Get-EsxSoftwarePackage | ? { $_.StatelessReady } | Add-EsxSoftwarePackage -ImageProfile $customProfile Hope this helps.  I am in the process of creating our PowerCLI scripts for handling our Image Profile building process to create custom ESXi 5.1 images.