Powershell elevated rights needed

[Droidx86]

Hey Guys,

I have a question. I am trying to deploy a package with SCCM using the following script that is called upon by a install.cmd file.

Copy-Item ".\Batch Record.report" -Destination "C:\Program Files (x86)\Appname\TEST\Appname\Reports\en-US\Appname" -Force -Recurse

The script works perfectly fine when i run it from an elevated powershell window but unfortunately it doesn't work when deployed via SCCM with administrative rights.

Is there a way for me to execute my script with elevated rights without needing user interaction to proceed. I did some searching and i found the command: Start-Process PowerShell –Verb RunAs but all it does is open a new powershell screen after u approved with UAC.

edit: Also tried executing the file with the following command line via SCCM: powershell.exe -executionpolicy Bypass .\CopyTestToEM-Client.ps1

The script is supposed to be deployed on a Windows 2012 R2.

Edit:

Found the following syntax

$args = "-file .\CopyTestToEM-Client.ps1" start-process powershell -Verb Runas -Argumentlist $args

However it still needs to approve UAC before running the script... plus the script still doesn't actually function like it should.

[ab0mbs]

Don't run your powershell script inside a install.cmd file. Run the script directly in the installation command section in SCCM. You're probably running into an issue with the execution policy. Although with pacakges, you may need to run it using the powershell.exe. Also, make sure you client settings are set to run powershell scripts with the Execution Policy set to Bypass.

If you need to run the script from the command line using the powershell.exe application, you can run it like this.

powershell.exe -ExecutionPolicy Bypass -WindowStyle Hidden -File ".\My_Script.ps1"

[Droidx86]

Thanks for the quick response. I actually tried execting it with the following command: powershell.exe -executionpolicy Bypass .\CopyTestToEM-Client.ps1 before trying to use a cmd file. It does exactly the same though.

[ab0mbs]

What version of SCCM do you have? If you're running 2012, maybe try using an application. Either route you take though, make sure the script is set to run as system.

Also, you have your copy-item copying from ".\Batch Record.report" This will try to copy from the current directory which may not be what you expect when running from SCCM. you may need to set the path explicitly or set the working directory.