-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add vCenter User #1
Comments
Hey there, I've tried myself on the issue for a bit, and maybe it works by just passing along your credentials after saving them where you're running the script from:
And then of course update the connect command accordingly:
You'll need to enter your credentials the first time you run it, but after that it should run on its own. |
Hi MeinhartEsrohr Sorry didn't see this issue notification. I have the script running against two different vCenter in linked mode and never seen the popup. I have seen the popup issue before when the certificate from vCenter is not trusted. Have you check this. Also you could look at using New-VICredentialStoreItem to save credenital that can be a called later but it not something I can't add to the script as it different for each environment. New-VICredentialStoreItem -User domain\username -Password Password -Host vc.domain.local -File C:\Temp\vicreds.xml $logon = Get-ViCredentialStoreItem -File C:\Temp\vicreds.xml |
Hello TheSleepyAdmins,
I have a question, is there a possibility to define a username and password when running the script ?
When I run the script, after a short time a window opens where I have to enter the credentials of the vCenter, so unfortunately my planned task does not work either.
We have three vCenter servers, on one it runs without problems, on the other two the login window pops up.
In Windows where I run the script I am logged in with my domain user who also has access to the vCenter servers.
Thank You!
The text was updated successfully, but these errors were encountered: