VMware Cloud Community
raleysm
Enthusiast
Enthusiast
Jump to solution

Working on new ESXi box and ready to install vCenter but it won't install

So I have downloaded the vcenter iso file several times to make sure there was no problem. I have it unzipped and have watched several video of what i should be clicking on to start the install.  I have done this on both a windows client and actual windows machines. It will pop open the box to install but the box is all white and nothing every pops up.  I'm planning to install the linux version and have a blank VM setup for this that matches the spec on another server I have. Of course the image type is not for this as the machine never picks up an image.  Any suggestions on this for vsphere 6.7 file that I downloaded that is in my account for what was purchased?

Thanks

Reply
0 Kudos
1 Solution

Accepted Solutions
raleysm
Enthusiast
Enthusiast
Jump to solution

Yes I put ina ticket to fix this and VMware ran this all through a DOS script that we had to modify a few times.

View solution in original post

Reply
0 Kudos
11 Replies
daphnissov
Immortal
Immortal
Jump to solution

If you're talking about the vCSA, you should be opening the installer executable in the win subfolder. This should start an installer wizard which will connect to an ESXi host and deploy the entire VM for you. There is no VM you need to prep beforehand. If this isn't working, show some screenshots of what you have and what you're doing, because it's not clear.

Reply
0 Kudos
raleysm
Enthusiast
Enthusiast
Jump to solution

Yes I run the install from the folder that opens a screen that has the title but stays white and provides no options in the white box

Reply
0 Kudos
raleysm
Enthusiast
Enthusiast
Jump to solution

Sorry I just tried to create a blank VM to see if that had any effect but it did not. Just a piece of information

Reply
0 Kudos
daphnissov
Immortal
Immortal
Jump to solution

Screenshots, please.

Reply
0 Kudos
raleysm
Enthusiast
Enthusiast
Jump to solution

Will have to post tomorrow as I am not with the server and no remote for this.

Reply
0 Kudos
raleysm
Enthusiast
Enthusiast
Jump to solution

Here is the screen shot attached.

Reply
0 Kudos
raleysm
Enthusiast
Enthusiast
Jump to solution

Screen shot showing what I'm opening

Reply
0 Kudos
MBouillon
Contributor
Contributor
Jump to solution

Reply
0 Kudos
raleysm
Enthusiast
Enthusiast
Jump to solution

Did not fix. Still comes up to a white screen with the title on it. Nothing ever pops up in the middle of the white box.

Reply
0 Kudos
AhmedIbrahimVMw
Enthusiast
Enthusiast
Jump to solution

Have you checked the checksum value of the ISO file that you downloaded and compared it to the one mentioned in the download page?

You can generate the SHA-1 checksum value of the downloaded ISO using the following PowerShell cmdlet:

get-filehash -algorithm sha1 C:\Users\my-user-name\Downloads\VMware-VCSA-all-6.7.0-12345678.iso

I also noticed that you're running the installer from a Windows Server machine, so maybe the "Internet Explorer Enhanced Security Configuration" setting needs to be disabled:

Turning off IE enhanced security - Windows Server 2016 Administration Fundamentals [Book]

If this didn't fix the issue, then please try the command line installer, I always prefer using this method; since it is very easy and the whole installation can be run in unattended mode.

Just edit the appropriate JSON template (for example D:\vcsa-cli-installer\templates\install\embedded_vCSA_on_ESXi.json), add all required info and save to your desktop (or any other location).

Next open cmd.exe as administrator, and run the following command:

D:\vcsa-cli-installer\win32\vcsa-deploy.exe install --accept-eula -v C:\Users\my-user-name\Desktop\embedded_vCSA_on_ESXi.json

If you don't like the command line installation method, then create a new Windows machine, install VMware Tools, give it an IP address but don't join it to any AD domain, and try to mount the ISO and run the installer from there.

Reply
0 Kudos
raleysm
Enthusiast
Enthusiast
Jump to solution

Yes I put ina ticket to fix this and VMware ran this all through a DOS script that we had to modify a few times.

Reply
0 Kudos