Did you use a fully-qualified hostname that is resolvable (both forward and reverse) in DNS which it can access? If not, you must provide working DNS. Without it, vCSA will not install.
Try to login with b’<root password>’ (without the < and >).
That is, add b’ infront of the root password and ’ after.
Tell me if that works.
Thank you booth so far.
i set up a dedicated dns server with booth dns entries (forward/reverse) but it didn't worked that well. i Also tried it with the b’password’ method but notihg happens it was in a loop for arround 2 hours after i tried it again and even after an reboot.
i will now download a newer version of the installer i tried it with the Version VMware-VMvisor-Installer-6.7.0-8169922 and i am now downloading 8217866 maybe it will make a difference ^^.
I will keep you Updated.
I'm having the same problem. Tried it multiple times. I'm unable to logon to the local console or the web. DNS works like it should.
Also on workstation 14 and the latest vcsa ova image.
Got it. Reset the root password. I've followed this guide:
First, shut down the VCSA and take a snapshot.
1. Start the appliance up and press the space bar to freeze the GRUB menu. Note that you need to be somewhat quick here.
2. Press e to enable edit mode.
3. Append rw init=/bin/bash to the list of options as shown in Fig. 2.
4. Press F10 to reboot. The appliance will now boot up in bash or root shell.
5. Type passwd to change the root password. Type it twice and press Enter to confirm.
6. Optionally, you can unmount the file system using umount /
7. Type in reboot -f
im back with some new issues ^^ The Password bug seems not existent in the latest Version of the VCSA, but on the Deployment /Stage 2 it aborts at 2 %
in the error.log from the VCSA there is this messages:
No file found matching /etc/vmware/install-defaults/cm.url
No file found matching /etc/vmware-vpx/vcdb.properties
No file found matching /etc/vmware-vpx/vc-extn-cisreg.prop
im back and it now has finaly worked. The Soultion i had was to leave everyting on default and configure the Network and the Hostname afterwards.
I know it sounds stuppid, but it aint stuppid if it works ^^
maybe someone else can confirm that was also the solution for the Problem.