Turns out Microsoft decided to not allow you to run Powershell scripts out of the box. The Execution-Policy is set to be disabled and you have to go to Powershell to run<\/p>\n\n\n\n
Set-ExecutionPolicy unrestricted -force<\/pre>\n\n\n\nThe
-force<\/code> switch skips the prompt. However, this is a chick and egg problem with slipstreaming as you need to execute this first programmatically. I tried to use CMD files to dopowershell -command \"Set-ExecutionPolicy unrestricted -force\"<\/code> but it does not work and quite a few people reported ignoring execution policy with-ExecutionPolicy Bypass<\/code> switch topowershell.exe<\/code> does not work with NTLite either.<\/p>\n\n\n\nIt’s a colossal pain in the butt. Microsoft deciding to prevent Powershell scripts from running by default broke NTLite’s powershell scripting.<\/p>\n\n\n\n
I decided to take a look at registry values that can be changed and this website<\/a> suggested there is one. There’s a typo on the website. It’s not in HKCU but in HKLM (his screenshots says HKLM). The correct path is changing the string value
ExecutionPolicy<\/code> toUnrestricted<\/code> in the keyHKLM\\SOFTWARE\\Microsoft\\PowerShell\\1\\ShellIds\\Microsoft.PowerShell<\/code> <\/p>\n\n\n\nI cannot confirm when the registry files are loaded in NTLite. It could be too early or too late. (Looks like it’s too early to me since MDM fake enrollment registry<\/a> files do not take effect and I had to use
reg<\/code> command script later).<\/p>\n\n\n\nSo instead, I’ll do the registry change as a CMD script:<\/p>\n\n\n\n
reg add \"HKLM\\SOFTWARE\\Microsoft\\PowerShell\\1\\ShellIds\\Microsoft.PowerShell\" \/t REG_SZ \/v ExecutionPolicy \/d \"Unrestricted\" \/f<\/pre>\n\n\n\n