Here is the documentation for the password asked for by the SSO installer. I found it in a document called vSphere Installation and Setup (vsphere-esxi-vcenter-server-55-installation-setup-guide.pdf).
5 Set the password for the vCenter Single Sign-On administrator account.
This is the password for the user administrator@vsphere.local. vsphere.local is a new domain that is created by vCenter Single Sign-On. After installation, you can log in to vCenter Single Sign-On and in to vCenter Server as adminstrator@vsphere.local.
By default, the password must have at least eight characters, at least one lowercase character, one uppercase character, one number, and one special character. See the vSphere Security documentation for information about changing the password policy. The following characters are not supported in passwords: non-ASCII characters, semicolon (;), double quotation mark ("), single quotation mark ('), circumflex (^), and backslash (\).
No mention of the password needing to be the same as the local Windows Administrator account.
And here is the screen that asks for a password:
So I think I just discovered the true reason it was failing. In the documentation above, they say that ;"'^\ are not valid characters in a password. But, they missed a character: The space. I was using a space character in my password.
I tried out the installer a bunch of times. When one of the above invalid characters is used, the installer continues anyway. And then throws a 1326 in that other log file I mentioned. Using a space does the same thing. And it's not like they aren't checking the password at all. If you don't meet the complexity requirements that's in their documentation, then you get this notice:
I don't know why they accept invalid characters in the installer. And I don't know why they missed listing the space character as an invalid character in their documentation. It is an ASCII character, after all (0x20).
I did try a couple other passwords long ago, but I think it was before I found this documentation, so I may have used one of the other invalid characters. Or maybe I used another invalid character that is undocumented. If space is not documented as an invalid character, then who knows how many other invalid characters there are?
And so, I say to all who believe they are having the same problem that I did:
First, make sure it's the same problem. Verify that you are getting an error code 1326 in the other vminst.log file, located one directory above %TEMP%. If you cannot find 1326, then you probably have a different problem.
Then, try other passwords. Don't use the documented invalid characters. And keep in mind that there may be other undocumented invalid characters.
The password does not need to be identical to the local Windows Administrator account's password. It just can't contain any undocumented invalid characters.
Hola.! Referente a todo lo comentado esta duda, de igual forma intentamos hacer lo en un Windows server 2008 r2, pero causaba muchos problemas de instalación el VMware 5.5 u1 Single Sing-On. Pero una Opción que fue bastante buena fue instalarlo en Windows Server 2012. No presento problema alguno. La verdad es que ninguna de la soluciones que dan ayuda. (Lo siento).
1.- De igual forma se instalo primero VMware-OpenSSL (D:\Single Sign-On\prerequisites)
2.- Y después VMware-python (D:\Single Sign-On\prerequisites)
3.- Por ultimo se instala VMware-SSO-Server (D:\Single Sign-On)
