Powershell not creating registry key when script is run -


I'm currently making a powershell script in which technicians can run to help implement various registry make PC automatically Editing is not allowed for. However, whenever I run my script, I pre-existing value with the keys is no problem in changing times PowerShell, even when using the command "New Item" It will not be the key to what I've been thinking a Why would any idea as to the registry key is that I have no errors when run 

  HKLM set ItemProperty -Path "will create not receive :. \ SOFTWARE \ Microsoft \ Windows NT \ CurrentVersion \ Winlogon "-name AutoAdminLogon -Value 1 set ItemProperty -Path "HKLM: Microsoft \ Windows NT \ CurrentVersion \ Winlogon" -nam DefaultUserName -Value domain \ Test Set ItemProperty -Path "HKLM \ \ SOFTWARE: \ SOFTWARE \ Microsoft \ Windows NT \ CurrentVersion \ Winlogon" -nam DefaultPassword -Value TEST123 Test-path -Path "HKLM: \ \ WindowsNT \ CurrentVersion Winlogon \ ForceAutoLogon \ SOFTWARE \ Microsoft" if (-not (Test-path "HKLM: \ SOFTWARE \ Microsoft \ Windows NT \ CurrentVersion \ Winlogon" )) {new items -Path "HKLM: \ SOFTWARE \ Microsoft \ Windows NT \ CurrentVersion \ Winlogon" -nam ForceAutoLogon -Value 1}

test path is not designed for the value of the value you try / catch block Can be used. You also need to get / set item property 

  $ path = "HKLM: \ Microsoft \ Windows NT \ CurrentVersion \ Winlogon software \" {Get-ItemProperty-path $ path} } Object-ExpandParty Forceautoallogon-Arrayation Stop. Set Null out itemProperty-path $ path -name ForceAutoLogon -Value 1} {Catching New ItemProperty-Path $ path -name ForceAutoLogon -Value 1}

If get -ItemProperty < / Code> fails that key should not exist so we can make it! If Get-ItemProperty is successful, then we can ensure that the price is set correctly. I can use registry keywords incorrectly, but let the code speak for itself.


Comments

Post a Comment