In my case, after deleting the old object, the configuration wizard succeeded and my PSC appliance was ready for use. when I choose: PSC: HTTPS 443 SSO domain name: vmware.local SSO user: administrator (this should be 'Administrator' but vmware pre-populated the field with LowerCase) Unable to change this. the installer runs an import job at the end, but i think it doesn’t cleaned everything up.įor deleting the old object, use the following commandĬmsso-util unregister –node-pnid FQDN_of_failed_PSC_or_vCenter –username –passwd vCenter-Single-Sign-On-password This way of upgrade deploys a new appliance with a tempory ip adress and configuration. a few weeks ago, I’ve upgrade the PSC01 with a newer version, using the gui installer. var/log/vmware/vmdir/vmafdvmdirclient.log When hitting an error while deploying the appliance, you can use the following log file to get more information The bad thing was you cannot retry the configuration wizard, you must re-deploy the appliance.Īfter the second time getting the same error, I’ve enabled ssh for looking closer in the logging, I believe there was more. In my case I was trying to connect a second PSC appliance to my existing SSO domain with a new site.Īt almost 6%, I’ve received an error message which contains the following message “vmware psc failed to run vdcpromo”, and that was all. In the second admin interface ( stage 2 ), after deploying the appliance, you must specify which configuration you wanna used for your environment. Hi All, I’ve got something to share about an error while deploying a new PSC in an existing SSO domain.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |