After a bit of digging around it appears that I was using a custom ESXi ISO from HP which was the cause of the problem. The ESXi installer was looking for HP hardware information which it couldn't gather. So next time remember when doing a nested build just use the default VMware ISO.
Subscribe to:
Post Comments (Atom)
New Azure KMS IP and domain Addresses for activation
For Windows virtual machines deployed into Azure using marketplace images you may have created rules in your NSG or firewalls to allow the s...
-
For Windows virtual machines deployed into Azure using marketplace images you may have created rules in your NSG or firewalls to allow the s...
-
If you have Azure AD Premium P2 licences one of the reasons would of been to use Privileged Identity Management (PIM) as its a great tool to...
-
There is an article by Microsoft that lists all the URLs that Visual Studio requires to install or interaction with Azure services if you wa...
No comments:
Post a Comment