Came across this useful little gem today, its the executable responsible for running, or at least managing the VMware Virtual Center Service.
Where is it located?
C:Program FilesVMwareInfrastructureVirtualCenter Server>dir vpxd.exe
Volume in drive C is C_DRIVE
Volume Serial Number is F463-F653
Directory of C:Program FilesVMwareInfrastructureVirtualCenter Server
07/12/2008 04:07 AM 13,557,760 vpxd.exe
1 File(s) 13,557,760 bytes
0 Dir(s) 378,903,293,952 bytes free
Cool, so what can we do with it? Lets take at look at some of the parameters:
C:Program FilesVMwareInfrastructureVirtualCenter Server>vpxd -h
Usage: vpxd [FLAGS]
Flags:
-r Register VMware VirtualCenter Server
-u Unregister VMware VirtualCenter Server
-s Run as a standalone server rather than a Service
-c Print vmdb schema to stdout
-o port Listens on the specified port instead of 902
-b Recreate database repository
-p Reset the database password interactively
-P pwd Reset the database password to the specified password
-v Print the version number to stdout
Ok… so when would some of these be useful? When troubleshooting of course. The first three control the service itself, which is useful when your Windows Server does something wonky, like forget the service was registered.
-p and –P pwd are useful when you want to play a prank on your other VI admins… kidding, should you have a security policy that requires this change, or have a naughty admin leave the practice, they’re quite useful.
-o is useful if you need to run more than one vCenter on a single IP, just make sure you change this in your clients & ESX hosts as well.
-b is for when you want to start over, without passing go, or collecting $200. For when you really break things.
-s is for when your service isn’t starting and you want to find out why. It starts up in the DOS box and prints all logging there too. No need to go find the logs.
-c well, I’m not sure I’d want to be reading database schema from the console, but hey, if that’s your thing, go for it. Might help to redirect to a file :>
Lastly, –v, print the version. Well… just in case you don’t recall the build number that’s printed everywhere else.
Keep at least some of this stuff in your lossy grey matter memory, you never know when you’ll need it.
Vpxd -p is needed if you replace VirtualCenter SSL certificates. The password is encrypted with the certificate, and the service can't decrypt the PW once the certificate is changed. Therefore the password needs to be given again.
I'd say this is not a new command and is quite common knowledge.
Interesting. Hadn't seen too much on it before, so figured I'd write it up in case someone else would find it useful.
Vpxd -p is needed if you replace VirtualCenter SSL certificates. The password is encrypted with the certificate, and the service can't decrypt the PW once the certificate is changed. Therefore the password needs to be given again.
I'd say this is not a new command and is quite common knowledge.
Interesting. Hadn't seen too much on it before, so figured I'd write it up in case someone else would find it useful.
In your explanation;
===============
-h is for when you want to start over, without passing go, or collecting $200. For when you really break things.
===============
I think you mean “-b” 🙂
In your explanation;
===============
-h is for when you want to start over, without passing go, or collecting $200. For when you really break things.
===============
I think you mean “-b” 🙂
Good catch. I’ve updated the post accordingly.