provisioning a windows server 2008r2 machine gets stuck on setting the password #3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ata-get and retry getting correct data three times
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While provisioning the password did not get set automatically. I had to login via the predefined one.
set-administrator-password.vbs did not run successful because it tried to set "SUCCESS" as Administrator password (which is somehow invalid and not what was specified in metadata).
mdata-get did return the correct password in two out of three tries - the third try did result in no output at all.
I did change the login a little to ignore those unwanted strings ("SUCCESS", "NOTFOUND") and added a retry counter of three to be sure to fetch and set a password.