ESXi 6.7 NEW Install

[RParker]

I installed ESXi 6.7.  IT boots.  I get an IP, I can connect to it.  If I use the console to the machine I enter root and the 'password'.  Everything works.

I go to web the SAME IP displayed on the console or one that I set, I enter root and 'password' and it DOES NOT LET ME LOGIN.  WHY?Y?Y?Y?Y?Y?Y?Y?

Just to make sure it's not me, I tried adding the machine to vCenter, same problem.  I type root and the 'password' (that I assigned) and it's NOT working.  Keeps saying my login info is incorrect but it's NOT incorrect.  Also password requirements have changed I now have to include a number or special character that wasn't a requirement before.  Why does VMware need to keep reinventing the wheel?!?!?!?

I have restarted and reinstalled twice.  I swear I am using the SAME login in both places, did they change root to something else?  I tried Administrator, Admin, root, etc.. it's NOT working.

What gives?

[peetz]

Greetings,

two thoughts:

1. When you set the password during installation at the console are you maybe using an unexpected keyboard layout, so that you type something different than you *think* you type?

2. Is the special character that you are using a *very* special character? Historically there have always been issues with certain special character in passwords leading to issues.

- Andreas

[RParker]

Nope, I have done literally hundreds of ESX installs I can basically do it blind.. anyway neither here nor there, suffice to say that on that host I never did get it to work.

Keyboard layout is not a factor, it was odd.  Also password is simple, Zxxxxx5!  (starts with caps, random letters in middle, and end with number and !) Just to make sure it would let me use it.  I reinstalled it twice to the same host going slow the second time to make sure no mistakes.   I had 2 consoles up side by side, the Vcenter on one side and a window with DRAC access to the host in the other.  I type the password it worked.  I go to the console of the host can see the characters I am typing they were correct.  I put the password in notepad window copied it and pasted in vCenter pane and it said 'incorrect password'... I spent like an hour just going over every scenario that's why the angst post...

I setup another host with 6.7 and that one worked (yes same ISO), so maybe something weird on the host.  I guess it must have been something off with that host but it IS on the HCL.

So on the next server install went as it should but when I tried to add it to vCenter, I couldn't do it.  I could go to the IP of the host on web client fine, but vCenter just showed "time out waiting for vpxa".  This is also 6.7.

I remember the same thing happened when vSphere 5.0 first came out.. same thing hosts wouldn't install and couldn't add to vCenter.

The thing that really bothers me is 6.7 is an incremental update yet you can't upgrade from any previous version, so why is it a minor build it should be version 7.. or wait until ALL features of 7.0 are ready, why make this one so different?

I am using 6.5 U2 with ZERO issues, so whatever features or upgrades in 6.7 that are useful (if any) will have to wait..

STILL waiting for Vmware to do something with UI on webclient so we can do update manager and extensions.. STILL WAITING.. what's it been 2, 3 years now??

[MergimBSA]

Wow, I just created a new VMware account to tell you we're having the VERY SAME issue.

6.5 U2 works perfectly fine. Installing ESXI 6.7 on a brand new server, setting our password (e.g. Abc.1234), rebooting the server and we're locked out. We can't log in, we use the "username" field to check whether we're having a typo or not. And hell no, the password is correct...

RParker​ did you download the ISO straight from VMware or did you use the ISO file provided by your server manufacturer? We're using the most recent version (ESXi 6.7 | 17 APR 2018 | ISO Build 8169922), the official ISO straight from the HPE server.

[IRIX201110141]

Did you reuse the IP address? So was there already an ESXi running earlier with different password?

What i seen more than once... the >= 6.0 ESXi comes with a access blocker when you enter wrong password 6 times or so. When there is a monitoring system is in place which tries to login several times minute into the root account with wrong password it will be locked forever.

Regards,

Joerg

[MergimBSA]

Hi Joerg,

no this is a new server (HP G10). Well, to be exact: 6 out of the box HP G10 servers and installed ESX 6.7 as previously mentioned.

We used the official HP ISO file on all our systems and we're seeing the very same behavior on all our systems.

We just installed the previous version, 6.5 U2, on two G10 servers. And guess what, working as expected.

Are you sure about that lockout policy? I remember there was a temporary lockout. But locking the root account permanently would be terrible, I really doubt that.

[SupreetK]

Abstract from the below document - "Starting with vSphere 6.0, account locking is supported for access through SSH and through the vSphere Web Services SDK. The Direct Console Interface (DCUI) and the ESXi Shell do not support account lockout. By default, a maximum of ten failed attempts is allowed before the account is locked. The account is unlocked after two minutes by default."

ESXi Passwords and Account Lockout

Cheers,

Supreet

[MergimBSA]

Knew it, a permanent lockout would be a terrible scenario. Thanks for your clarification! 😉

[IRIX201110141]

If the monitoring never stops trying it the account will be locked again, again and again. For sure there is an unlock after a couple of minutes but that doesnt help in this case. 

Regards,

Joerg

[RParker]

did you download the ISO straight from VMware or did you use the ISO file provided by your server manufacturer? We're using the most recent version (ESXi 6.7 | 17 APR 2018 | ISO Build 8169922), the official ISO straight from the HPE server.

I always install direct from VMware.  I did figure out that 6.7 hyper-visor host will ONLY work with vCenter 6.7 as well.. but still 6.5 works for us.  6.7 also requires that ALL hosts be 6.5 we have a lot of old hardware no way we can move to 6.5 compatible hardware any time soon, so 6.7 may LOOK good on paper but it's not a must have for sure.. 6.5 U01 is working great (vCenter Appliance and hosts).

In the past I have installed the Dell ISO but I don't see a need for that now we aren't using the built in agents for anything, so why use the manufacturer stuff if it doesn't give us anything more?

UI I did notice that vMware is making it more useful so updates are coming via update manager, for now the Client works fine.  Client is what UI is and Web Client is the flash enabled version right?  Or do I have it backwards..

I did install 6.7 vCenter its cool.. but with problems I had with ESX hypervisor I am not going to even marginally show any interest.  I plan to take this up at the upcoming VMUG in Atlanta.

I love vMware but sometimes they do some stuff that makes you say.. zoiks!? (scooby doo impression)

Also just FYI look at fling for vCenter they have a separate client HTML 5 version that is slightly more updated than what comes with vCenter 6.5.. you have to install another VM to use it but it seems a tad more stable.

vSphere HTML5 Web Client

(labs.vmware.com/flings/vsphere-html5-web-client)

IT looks daunting at first to install but it's not.. trust me..

[RParker]

Did you reuse the IP address? So was there already an ESXi running earlier with different password?

What i seen more than once... the >= 6.0 ESXi comes with a access blocker when you enter wrong password 6 times or so. When there is a monitoring system is in place which tries to login several times minute into the root account with wrong password it will be locked forever.

Can't speak for everyone but for me at least I typed the password PERFECT the first time (as I said I can do this in my sleep).  But I figured I must have fat fingered something, the second time I made SURE I wasn't crazy.. still no luck.  Then I tried it AGAIN with 6.5 worked perfect so I know it's not me.

The password does NOT work initially or at any time, not lock out nothing.  This is at the host console not remote, on the host itself so there is not mitigating keyboard problems or browser issue.. it's ALL the OS, and like I said if there was a problem it should behave the same way regardless.. 6.5 works great, 6.7 does not.  Not even going to attempt it again.  I wasted enough of my time.

[RParker]

Knew it, a permanent lockout would be a terrible scenario. Thanks for your clarification! 😉

Yeah it hasn't been a problem before now, so why all of a sudden the emphasis on this strict security?  I have made a note to change my hosts so they never lock out (no one has access anyway...).  We are gated behind a firewall, and layers of labs so it's not like we are publicly accessible, no need to have this password scheme in place.  And I make sure root does NOT prompt for password reset after 1 year something else vMware decided to implement, a lot of new 'oh what's this' stuff on these latest releases you have to watch them like a hawk.

[EricChigoz]

Hello RPaker,

My thoughts...

1. does your password have any special characters ?
2. Do you have console access?
3. Change your password to a simple password like password for a test and lets see how it goes.

Thank you.

[JordieFike]

was there ever a resolution found for this? I just upgraded our host from 6.0 to 6.7 and now I'm locked out.  It's late Friday, so if I don't get a good answer by Monday am I will just do a fresh install, but I shouldn't have to and from what I'm reading here it may not help

EDIT: Just did a fresh full install over top of my broken upgraded install and it's working just fine

[khankhan999]

On my machine it shows the following error.

password does not have enough character types.