Powershell Unauthorized
Hello All,
The School I work for has just started using PDQ Deploy & Inventory, and we are liking it alot so far.
We are making our first custom deployment to deploy Python. Python installs fine however we are trying to run two powershell scripts, one fixes the python uninstall location, the other uses pip to install extra python modules.
The problem is both of these scrips get an Access Denied error message when deployed through PDQ. I've even used a script that just does Write-Host with the same result.
Both scrips run fine when run as the deployment user manually. I have tried copying the script into the PDQ console and supplying the PS1 file.
I've noticed when testing that our script is deployed with our digital signature, the Error handling Wrapper has the PDQ signature on, however the user.ps1 script has nothing on it. I'm guessing the powershell execution policy is blocking it as we require signatures on our network. This seams to occur even though PDQ deploy is using powershell with the -bypass parameter.
Has any one else come across this/ knows a solution?
Edit: Below is the error message.
Invoke-Expression : File C:\windows\AdminArsenal\PDQDeployRunner\service-1\exec\user.ps1 cannot be loaded. The file C:\windows\AdminArsenal\PDQDeployRunner\service-1\exec\user.ps1 is not digitally signed. You cannot run this script on the current
system. For more information about running scripts and setting execution policy, see about_Execution_Policies at http://go.microsoft.com/fwlink/?LinkID=135170.
At C:\windows\AdminArsenal\PDQDeployRunner\service-1\exec\Error Handling Wrapper.ps1:39 char:1
+ Invoke-Expression "& '.\$($Parameters[0])' $($Parameters[1])"
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : SecurityError: (:) [Invoke-Expression], PSSecurityException
+ FullyQualifiedErrorId : UnauthorizedAccess,Microsoft.PowerShell.Commands.InvokeExpressionCommand
Comments
I managed to find a way to work around this, I added -file "Scriptname.ps1" to the command line that pointed to by signed script and it skipped the unsigned user.ps1 script. The user.ps1 only seams to point at it anyway.
It seams to work, the only strange behaviour with this is that PDQ adds its own -file afterwords, but that doesn't appear to run.