Access denied error, seen here in its natural habitat.
This is easily solved using the old right-click -> Run as Administrator routine, but what if you need a script to run a command, or an entire script as administrator? In this post I go through the three scenarios I’ve come across for running some Powershell commands as an administrator; a single command, an entire .ps1 or batch file, and a entire script from within the script calling it.
So the other day I was presented with the issue of converting a Julian Date (YYYYDDD) to a Gregorian Date (MMDDYYYY). After a few minutes in Powershell I realized that there was no built in way to do this. A few minutes a Googling yielded a few long, bloated scripts. I knew there had to be a better way, and there is!
Windows Server 2012 / Windows 8 and above include some nifty Powershell cmdlets for working with scheduled tasks. However, when the need arises to programmatically work with them on older OS versions, mainly Windows Server 2008 , try out the code below.