Update Initialize-OSDBuilder.ps1 #19
Open
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
Initialize-OSDBuilder doesn't work in my lab when using the default "C:\OSDBuilder" location i.e. $SetHome is not used and thus "HKCU:\Software\OSDeploy" registry key is not populated. $global:GetOSDBuilderHome doesn't get set when using the $Null check on line 31 If I make the change proposed, my issue resolves (Not tested on other labs yet, sorry)
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.
Initialize-OSDBuilder doesn't work in my lab when using the default "C:\OSDBuilder" location
I do not pass the variable $SetHome and thus "HKCU:\Software\OSDeploy" registry key is not populated.
$global:GetOSDBuilderHome doesn't get set when using the $Null check against the registry value on line 31
If I make the change proposed, my issue resolves (Not tested on other labs yet, sorry)