Re: vCenter Single Sign On master password

The unsupported "build a new database and copy the hash" process is discussed in this thread; http://communities.vmware.com/message/2230313

Read the post by Grasshopper.

Basically, it goes like this;

1. Install a unconnected, totally seperate, new vCenter and SSO install, and have it use a new database. This is all temporary, so just put it on a standalone server or something.
2. When doing this new install, record and write down that NEW Master password.
3. When this new install is complete, pull up the database tables and look for the hash for the "admin" SSO password. This is the hashed password for the new install. This is described in the Grasshopper links.
4. Copy that hash from the NEW install.
5. Paste that hash into the database on your OLD, Production SSO database.
6. The database table and field locations are mentioned in the post and links from Grasshopper
7. Now the hold, production database will have the password you set in the new install.
8. There are some other steps about stopping services, etc., so read those posts.

Disclaimer; I'm sure this processes has the ability to totally mess up your cluster, or your production SSO database. It's also unsupported by VMware, but several folks have used it successfully. I've used it with success on other similar databases, but not SSO specifically.

This really is a "last resort" process.