HZW 1.5-1220937 Password Expired Error

HZW 1.5-1220937 Password Expired Error

Got this? Yep, that’s what I thought. If you’re working with the GA release of Horizon Workspace 1.5 (Build 1220937) dated July 30th, 2013 and you are performing a new installation (after September 8th 2013) you will be greeted with the screen above.  In this article I’ll walk you through how to fix this issue on existing Horizon Workspace 1.5 (Build 1220937) installations, and cover something you need to know in product that the KB does not tell you.  At least it doesn’t yet.

You can read the official VMware notice at the link below.  Spoiler alert, you need to download a new build.

Installing VMware Horizon Workspace 1.5.0 Build 1220937 fails with the error: WARNING: Your password has expired (2059293)

So, what are your options here.  Well, the previous build (1220937) is no more.  If you have a copy of it and need to run a new installation, don’t, download a new copy from Horizon Workspace 1.5 Build 1318295.

But wait, there’s more.  What if you already have 1.5 Build 1220937 deployed and running?  So that’s fixable as well, and it’s pretty quick.

Note: VMware has published a KB article (KB 2059395) that now covers existing installations as well.  What it doesn't cover is the datava-template.  At the moment, that's only covered here in this article.  The datava-template must be repaired as well or else attempts to roll out another data node will fail.

From vCenter open a console to each VM in the Horizon Workspace vApp.  Once the console is open login as root and the password you set at installation.  From the command line run the following command on each and every VM in the vApp.  DO NOT power on the datava-template VM yet, there’s one extra step for that one.

chage -M -1 configurator

If this errors it’s because you are not logged in as root. If you did this via SSH and logged in as sshuser no worries, just su –, enter the password as before, then run the above command.  Regardless of how you do it, once you run the command above on every VM in the vApp you’re done, just log out.

Datava-Template Repair

Now, what about the datava-template VM that’s powered off?  You MUST unplug it’s NIC from the VM Settings prior to powering it on.  If you do not it will come up on the same IP address as the original data-va (master) that you have in production.  Can’t have that, now can we?  Once you unplug the NIC just power it on, run the above command like you did on the others, and power it down.  Be sure and use shutdown -h now from the command line so it will be clean.  Oh, and don’t forget to plug the NIC back in!