KACE Product Support

I've been using this in the k1000.

I haven't tested it in the k2000 but i think it'll work.

Add you script as an application and use this as the command line.

powershell.exe -nologo -executionpolicy bypass -WindowStyle hidden -noprofile -file "script.ps1"

dchristian, that is sweet, didn't know you could do that, I always write a script that changes the registry of the execution policy first, then run my .ps1 file

"HKLM\SOFTWARE\Microsoft\PowerShell\1\ShellIds\Microsoft.PowerShell", "ExecutionPolicy", "REG_SZ", "RemoteSigned"

So I'm assuming I would take out the set-executionpolicy remotesigned -force from my script and the "script.ps1" is the name of my file right?

That is correct, the execution policy must be set first, prior to running a .ps1 file, or in this case, as you are calling the file.

Picked up the tip from [link]http://powershell.com/cs/[/link].

They got a great RSS feed!

WOW, great resource, thank you dchristian.

I created a batch file that says:
powershell.exe -command add-computer -domain domainname
pause

Named this JoinDomain.bat, saved to C:\ and added a RunOnce entry that called this file. It ran no problems. For some reason I didn't have to modify the executionpolicy calling the command from a batch file.

very strange indeed. If you did a fresh scripted install, you would have to set this execustion policy. Are you doing it to an image, because maybe it is set there already. You can go to the registry key I mentioned above to see what it is set to.

I thought that at first so I removed the pc from the domain, ran set-executionpolicy restricted to set the policy back to restricted, then fired up powershell and tried running a ps1 script and it gave the message about scripts being disabled blah blah blah. I then added the RunOnce key and rebooted and it ran again no problem. It really is odd that I don't have to set the executionpolicy when doing this from a .bat file but I do have to set it before I can run it from a .ps1 file.

When you use the -command option for powershell.exe, you are not actually running a .ps1 file, so the execution policy does not apply.

I have run into PowerShell issues if PowerShell is not launched as admin or elevated The command below will elevate PowerShell to admin and will allow more functionality... 

Start-Process PowerShell -Verb RunAs