tag:blogger.com,1999:blog-2228947945609574437.post463297414468955022..comments2024-03-17T16:23:31.499-04:00Comments on Terence Luk: Joining an existing vCenter Single Sign-On (SSO) installation fails with the error message: “Error 29103. Cannot read file or directory.”Terence Lukhttp://www.blogger.com/profile/02612575579652280306noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-2228947945609574437.post-13757092659833926062013-03-12T15:30:08.572-04:002013-03-12T15:30:08.572-04:00Hi Terence,
My question is there an easy way of r...Hi Terence,<br /><br />My question is there an easy way of reconfiguring the second production vCenter 5.1 that was not joined the SSO in linked mode when it was first deployed as a simple install. I have an environment with dvswitch which can be a pain bringing all back to normal if i have to uninstall everything on the vCenter.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-2228947945609574437.post-45040943039117238802013-02-23T22:17:20.348-05:002013-02-23T22:17:20.348-05:00That would work but we would ultimately have to pe...That would work but we would ultimately have to perform another install on the original VM and point it back if we want to collocate the services together. I would probably prefer to just take the vCenter service down for a bit to just do it once. Terence Lukhttps://www.blogger.com/profile/02612575579652280306noreply@blogger.comtag:blogger.com,1999:blog-2228947945609574437.post-10791041151532817342013-02-23T22:12:36.755-05:002013-02-23T22:12:36.755-05:00I havent tried uninstalling SSO while vCenter was ...I havent tried uninstalling SSO while vCenter was pointed at it. I think I would probably install multisite SSO on another VM, point vCenter at that, then uninstall the old SSO instance. But your idea may work as well.Thomas Brownhttps://www.blogger.com/profile/12258386374163111315noreply@blogger.comtag:blogger.com,1999:blog-2228947945609574437.post-63794812309110904972013-02-23T20:05:55.660-05:002013-02-23T20:05:55.660-05:00Thanks Thomas. I suppose we can treat the SSO serv...Thanks Thomas. I suppose we can treat the SSO service collocated on the same vCenter service server as "corrupted" and proceed to uninstall, reinstall, then point the vCenter service to a newly installed one.Terence Lukhttps://www.blogger.com/profile/02612575579652280306noreply@blogger.comtag:blogger.com,1999:blog-2228947945609574437.post-23145436478219088312013-02-23T19:54:37.180-05:002013-02-23T19:54:37.180-05:00This comment has been removed by the author.Terence Lukhttps://www.blogger.com/profile/02612575579652280306noreply@blogger.comtag:blogger.com,1999:blog-2228947945609574437.post-16449667603769588672013-02-23T19:42:30.457-05:002013-02-23T19:42:30.457-05:00Hey Terence, there actually is a VMware KB article...Hey Terence, there actually is a VMware KB article regarding how to change the SSO instance that vCenter is using. In case someone does have a production vCenter that can't be uninstalled, that would probably be the best route going forward.<br /><br />http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2033620Thomas Brownhttps://www.blogger.com/profile/12258386374163111315noreply@blogger.com