VCenter install Fail! Help me install this! EP-192

I try and fail to install VCenter server.

Thanks for watching! I hope you all enjoy...

For PayPal or Patreon donations to Unkyjoe's Playhouse, please visit the "About" section on my channel. All cash donations are directly put back into Unkyjoe's Playhouse channel projects.

I cannot respond to all emails, but give it a go!

*PLEASE NOTE*
I do not respond to YouTube or Google+ private messages. Please contact me via the official Facebook page or via my email address to get in touch.

[edseit]

I just move my vcenter appliance install to a bare metal win server windows vcenter install and works just fine. Imho, I would try doing that first and then maybe migrate it to an appliance if you need too. Just my $0.02.

[bendyinkmachinefan]

I ran into the same problem when I tried to deploy vcenter server appliance and changing the year back to 2016 worked for me and it completed successfully

[TrcRat]

didn't read all the comments so forgive me if this is duplicate. I have done this without any issues. The only difference is I uploaded the ISO and used thick provisioning. Not sure if that will help with your issue but just a thought

[Hancock_nl]

I don't see the mac-adres of the appliance being attached to the hostname, as a static dns entry. That was/is a prerequisite.
But i see you got it working 👍🏼 Now on to the vm-kernels 😉

[pastyk]

Frustrating I'm sure!
I've just tried exactly the same setup as you but with VCSA 6.7.0a deploying on an ESXI 6.7.0a host. The only differences were that its 6.7.0a and I deployed the appliance to a 410GB datastore (4x 146GB in RAID5).
In my experience, the first error usually causes all the rest - the "dfsys" disk didn't get allocated/created during deployment. The error doesn't explicitly state disk space is an issue, but my hunch is this is probably because the selected datastore is smaller than the requested disk size - despite thin provisioning.
I would try to replicate that on my own - can you manually add a thin provisioned 200GB disk to a VM from a datastore smaller than the requested disk size, or does it throw an error/not let you?

[mySanctuary]

on step 7 do you have other networks in the drop down as sometimes this does not match.

[nickharvey]

have you tried connecting to the venter via the webui? The main one I use takes ages to fully start, but it always gets there. I also noticed that you installed it on a datastore with much less than the 250Gb it requires. Maybe that's an issue?

[johnveldthuis]

Maybe it did not like the password you supplied. Was okay for the app but esxi may not have liked it. Make it more simple. 7 chars long with 1 caps, 1 number, 1 special (maybe try !) and the rest lower case. I have installed the tiny several times and never had an issue until I changed esxi password policy so that it did not need special characters. After doing that it failed to install until I put the password policy back to the default. Once I did that it installed fine.

[DAVIDGREGORYKERR]

If you cannot solve the problem them have a word with Morton but I think that ESXI6.5 Updae1 is for the RYZEN range of processors and there are people running this package on an AORUS ZENITH EXTREME X399 and 1950x and 1TB of DDR4 3000MHZ RAM

[xfowokan]

hello, did you manage to get this resolved

[PassMeABeerDude]

Did you try the 64 bit installer as well? Did you get the same results with it?

[andersgjerlw]

can you please give out a link on how to make that image on the x3650 m3 server? I'm interested in doing this myself.

[brak]

Not to add to your stress level, or to change the topic, but your fish tank could use a cleaning!

[thtadthtshldntbe]

DId Morten get it working? Almost everything I know about esxi I learned from him over the years

[SakuraChan]

getting all the iso's and OVA's from vmware atm so i can try, not going to deal with DNS it will be direct internal IP addresses so wont have that part of this setup prrcess, i was able to install this before on 6.5.0, trying on 6.7.0 using i think some newer CPU's then you have not sure there, will keep you posted however

[jims-tek]

I understand that it is a credentials error, but I kinda wonder if it has something to do with the tiny deployment error? I have used VMware server a few times but I never deployed the VCenter app just cause it costs money that I didn't want to spend. I personally like Hyper-V better mainly cause it is integrated into most versions of Windows.

[epsyuma]

FYI: You cannot install vCenter if you are using the free license of ESXi. It will hang at 80%.

[LadislavBrezovnik]

If you are using a trial installer that is older than 60 days the install won't work. It will get stuck at 80% every time.

[gene]

If you set the date of the esx server that you are installing it on to 2016
it will complete the install after that you can set the date back correctly
i just did this several time to make sure.. hope this helps someone

[davidsomething]

It is clear as you say that the settings are not being applied hence why IP address, hostname and credentials are not correct. I did have this same issue about a year ago a couple of times but got it to work in the end. I'm really sorry I can't help you out as I can't remember how I resolved, I can only try and point you to some articles to help. I'd certainly suggest making sure any log files are viewed on the ESXi host, make sure that there are no remains of a failed install in the datastore. Can you also check that you can resolve the ESXi hostname of itself through the Network Management tests on the console of the ESXi host. But to be honest if you have support with VMWare then I'd log a ticket, if you have evaluation they may still help or post the issue on the VMWare forums if you hav not already.