Thanks .... This worked for me !
1 person found this helpful
Thanks David for your hints.
I tried workaround to "back-date" the sa-esxi-01.vclass.local and student-a-01 VMs to 13 Oct 2017, and install the VCSA appliance.
It completed successfully then logon to VCSA to change the root password.
after the web client is up; can change the expiration of root password
Can anyone tell the workaround to fix installation stuck at 62%.
what was the error message? please paste the screenshot if possible, that will be helpful.
Your back-dating method seems to be the most reliable I've found on the internet so far, can you walk us through it step-by-step to see if maybe we can all copy your workaround?
Please check previous comment in this same discussion, I have uploaded snapshot.
Thanks RSuryanto! Going into bios of the target esxi host and changing date to Oct 13 2017 allowed the installation to finish. I then logged into vcenter and changed Administration>Password Expiration Settings>Root Password Expires to 'No'.
This is what I've found...
Same thing happening to me. When you access the VCSA console, It mentions that the root password is invalid...no matter what you put in.
Went back to a fresh install and noticed the installer not accepting the proper characters when typing them for the root's password. Repeated typing password very carefully a couple time to make sure the verification went green. This has worked every time.
This definitely looks like a Flash issue...whatever the installer is based on.
I've also seen success with installing an older version of Flash Player and disabling the Flash Play auto-update service.
I do had similar issue. So far I did researched and found some interesting
1. Its because of the new ESXi 6.5 version
2. Its because of the type of hardware and firmware version you are using
To overcome the problem download new "VMware-VCSA-all-6.5.0U1c.iso"
Take a look at the VMware notes on VCSA Appliance
I too faced this problem with the older image. However in my case backdating didn't work so what I did was booted into single user mode and edited /etc/shadow to change the expiration date. This seems to have resolved it on my end.
1 person found this helpful
I just purchased the VMUG Advantage giving me access to everything for my home lab, and confirmed that the latest version of VCSA has this same issue for new deployments. These are the steps I took to get around it; I have tested 4 times and am successful each time:
- Mount the ISO to a folder with your favorite tool (I used Virtual Clone Drive).
- Log into one of your ESX hosts and choose the option to deploy OVF/OVA
- Browse on the ISO folder to vcsa and choose the ova file
- Complete the configuration prompts and let the image deploy. You will end up at the login screen of the appliance, with nothing configured.
- Login to the appliance (I had to use the default password of vmware) and manually change your password, configure IP settings, and change host name.
- Reboot the appliance, and when it comes back up browse to https://<IP of appliance>:5480
- The VCSA installer should kick right off at the installing RPM step. In all my testing of this it has completed within 5-10 minutes.
- Once RPM completes, you'll be able to click on the Set up vCenter Server Appliance option
- You will be prompted for all IP, DNS, and hostname information again, but for me it pulls all of the settings I configured manually on the appliance. I just had to click OK.
- The appliance second stage configuration will commence; this took me c. 20 minutes to complete.
This awesome solution, i login in console VM and installation contunue.
I had similar issues.
looking at the old vcsa i found that the temp log directory was full at 100%.
removed the logs and brought down the size to 50%.
rerun the migration and migration completed successfully.
If i may recommend. please remove all the unnecessary log files, address all the alarms before trying to start migration.
This works for me! Thanks!
I got the root cause of the problem. Its the problem with the NTP sync settings.
I mean if your ESXi and your windows/any other OS from where you run the Installer not SYNC then you will fail at 80% or RPM. so the fix is set the NTP server on ESXi server and on your Windows PC and run the installer. Once you set the NTP settings you good to go.
Don't wait long at 80% it takes hours before error out. Open the vCenter VM console and verify. It should had given you the error already.
Good Luck Guys.