Sometimes you want to be able to just double click your powershell scripts and see them work….putting this code at the top of your script will do just that by detecting if the script is running as administrator with administrative priviledges. If not, the script will launch a new instance of itself with an elevation prompt.<\/p>\n
$scriptPath = split-path -parent $MyInvocation.MyCommand.Definition\nIf (-NOT ([Security.Principal.WindowsPrincipal][Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole([Security.Principal.WindowsBuiltInRole] \"Administrator\"))\n{\n $arguments = \"& '\" + $myinvocation.mycommand.definition + \"'\"\n Start-Process powershell -Verb runAs -ArgumentList $arguments\n Break\n }\n cd $scriptPath\n<\/pre>\n","protected":false},"excerpt":{"rendered":"Sometimes you want to be able to just double click your powershell scripts and see them work….putting this code at the top of your script will do just that by detecting if the script is running as administrator with administrative priviledges. If not, the script will launch a new instance of itself with an elevation … Continue reading Elevating powershell scripts, and staying in the script folder<\/span>