If like a few of you I rushed off to install the latest VCSA, you may have come across some errors. I attempted multiple installs prior to consulting with Google and then came across this article by Olivier Gosselin.

With my limited French I was able to get enough out of this to spark an idea. The first thing I did was of course try was using an IP as the host name but it still failed. I can only assume this was still down to DNS and the NTP server.

Most of you would think this is not an issue but for me it was as I was starting from nothing. I also thought this was a good time to start my domain again too.

I fired up a new Windows 2016 DC on local disks attached to another server, then I got the bare basics up on including an A record for the VCSA. From here I tried the install again. I pointed the DNS and NTP to this server also using the default SSO settings and it worked!

This has made me want to try and install one more time later this week to see if this is a bug or not. The main thing that puzzles me is what does this mean for completely clean installs for a new site or even customer…. is there still an assumption here you have the DC, DNS and NTP all configured elsewhere. I know some sites I have gone to the DC is set up on the new environment and how can you do this if lets say you have a nice new 3 node VSAN… don’t you need the VCSA to create this in the first place?