I have just upgraded/migrated vcenter 6.0 on Windows to vcsa 6.5. Everything looks fine, but when I want to connect to the vCenter server using the Connect-VIServer command, I need to add my Windows credentilas in a popup window.
Before the upgrade, the PowerCLI used my credentilas from my active Windows session.
Because of this, my scheduled scripts could not run. What coud be the reason of this changed behavior?
Can you check if the Advanced Settings on your VCSA contain the config.vpxd.sso.sts.uri entry?
Can you do a Get-VICredentialStoreItem?
Is there an entry for the new VCSA? Is there one for the older vCenter?
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
The config.vpxd.sso.sts.uri exists and tha value is:https://PSC_server_name/sts/STSService/vsphere.local
The Get-VICredentialstoreitem is empty.
We use extrnal PSC.
In case of Web and HTML 5 client the integrated authentication works.
Do you have entries in the vpxd log from around the time you did the Connect-VIserve?
Messages with SessionManager and SSPI in them.
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
This thread Connect-VIServer without prompting for user could also provide an explanation and solution, provided your old and new vCenter have the same hostname.
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference