Hi Jacob,
Sorry for the late response.
Steps for 6.0 Windows VC WITH EMBDED PSC NODE:
1.) Copy the provided 'server-configure.bat' to any directory on the vCenter for Windows. (This file is one of the Fling downloads on the top left from https://flings.vmware.com/vsphere-html5-web-client)
2.) NOTE: If you have installed vCenter into any folder other than default (%PROGRAMFILES%), the script may not find the appropriate files.
You will need to edit the file and replace the two references to %PROGRAMFILES% with the appropriate path so that the “KEYTOOL” and “VECS_CLI” paths line up.
These two variables are at the top of the file.You may also need to change this at the end of the file to the correct path (this is for the ds.properties file):
SET CLIENT_DIR=%PROGRAMDATA%\VMware\vCenterServer\cfg\vsphere-client
3.) Open an Administrator Command Prompt and run the 'server-configure.bat' script. The following files will get generated:
i) store.jks
ii) ds.properties
iii) webclient.properties
4.) In webclient.properties change
keystore.jks.path=/etc/vmware/vsphere-ui/store.jks
5.) Login to the appliance and create the following folders:
/etc/vmware/vsphere-ui and /etc/vmware/vsphere-ui/config
6.) Copy "store.jks" and "webclient.properties" from the vCenter for Windows to folder "/etc/vmware/vsphere-ui" at the appliance.
7.) Copy "ds.properties" from the vCenter for Windows to folder "/etc/vmware/vsphere-ui/config" at the appliance.
8.) At the appliance change the owner of folder "/etc/vmware/vsphere-ui" to user vsphere-ui:
chown -R vsphere-ui /etc/vmware/vsphere-ui
9.) Restart the vsphere-ui service:
service-control --restart vsphere-ui
If you have external PSC node the steps are different!
I have Vcenter 6.0 u3 running on Windows. I am trying to run server-configure and getting this error:
Using the get-machine-id as get-ldu is returning an error for this vcenter.
Error 100001: An unknown option was present on the command line.
Using the default reverseproxyport=443 since no custom port found.
Creating ds.properties file...
Everything is installed in the default Program Files folder path. Has anyone encountered and resolved this?