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.

Continue reading

Note: This article covers material present in Version 1 Revision 3 and below.  Topics found below may be mitigated in the most current version of the ESXi 5 STIG.  Ensure you are using the most current version of the DISA STIG documents.

Before we move into Part 2 of the ESXi 5 STIG documentation we need to talk about file persistence and how to deal with it.

Note: This is UNSUPPORTED!  Also, changes made to the rc.local and/or local.sh file may not persist after an update or upgrade.  Take good configuration notes of your systems and verify once an update or upgrade is applied.

Those of you that have been using ESXi for a while now realize that files do not persist across reboots unless they are tagged by VisorFS as persistent.  While this may be inconvenient at times the reasons behind it are valid.

So, along the lines of the ESXi 5 STIG, we have a few things that we need to set and persist across reboots.  Findings that have us modify existing files on ESXi are fine.  We can modify those and they will persist, typically.  Always test with a reboot to ensure your settings stick.  What about the findings where the configuration file doesn’t exist?  The SSH Client (ssh_config) settings are a prime example of this.  ESXi 5+ does not currently have a ssh_config file present in /etc/ssh, so any attempt to create and populate one with settings will be lost on reboot.  That’s a problem for you SAs out there needing to comply with the STIG.

How do I create configuration files and make them persist you ask?  Smoke and mirrors my friend.  Persist by way of recreation at boot.  You could do this with a custom package file too, but that violates another STIG setting, so lets stick with this method for now.

Continue reading

Update: VMware has now published a KB article covering this issue.  The fix steps provided there are the same as below.

Using Horizon View 5.2 Feature Pack 1 against a Windows XP Desktop source HTML access connections fail with:

An error has occurred: {“code”:”ECONNRESET”}

Subsequent tests against a Windows 7 Desktop source all function correctly, so I know my configuration is correct.  What’s the problem here, and is there a solution?

Great question, so what’s actually going on here?  It’s even talked about on Wee Kiong Tan’s blog here, he had the same issue, so lets walk though what causes this.

Continue reading