-
-
Notifications
You must be signed in to change notification settings - Fork 360
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
[Bug]: -InstallationUserCredential mixed up in New-LabPSSession #1620
Comments
I think, in my Case, there is a mistake: In AutomatedLab/LabXml/Machines/Machine.cs In my Case, there are put the DOMAIN @ MachineLocalInstallationUser together... They must like DOMAIN @ DOMAINInstallationUser |
@Mr-Kappelmann, can you post the full deployment script here, please? |
what do you need in detail? |
The problem needs to be somehow isolated and reproducible for us to work on it. AFAIK this is the first we've heard of it, and without a concrete error scenario there's little we can do. Can you please reduce the script to the essentials? |
Ah okay, I understand. |
I have updated the first Post. There are a little script. that reproduce my problem with swtching Accounts in New-LabPSSession, so that ended in: New-LabPSSession: [172.22.69.11] Connecting to remote server 172.22.69.11 failed with the following error message : Access is denied |
Ok, I see the error. I will look into this the next couple of days. |
That sounds good news for me... Have you a tip/better workaround for that: I see a problem like that in the WindowsNT "AutoLogon"... mixed up with local & domain In AutomatedLabWorkerVirtualMachines.psm1 near line 205
|
Description
I will use for every machine a different local/Administrator Account password
You see, thats is right, I think:
New-LabPSSession Entering... UseLocalCredential=True
later than a mix from local and domain Account:
Creating a new PSSession... UserName='$domainName\Administrator'
I think, they must use UserName='$ComputerName\Administrator' #SDC\Administrator
In the VerboseLog, I see that during "Installation" the UseLocalCredential= toggle between True and , that are interpreted as False. They generate New-LabPSSession: Access denied errors
Steps to reproduce the issue
see in description
PowerShell Version
AutomatedLab Version
The text was updated successfully, but these errors were encountered: