Every now and them I get to a customer where they want me to write some code that will be executed at desktops.
However, most of the times I’m part of a team that’s responsible for managing servers and not desktops.
Desktops are managed by another team, sometimes it’s even outsourced.
…and they have the execution policy for desktop set to anything but Unrestricted, or even Bypass.
There are quite a few ways to work around this, but here comes one of my favorites:
This script assumes you’re allowed to execute *.cmd files and have access to the *.ps1 file you want to execute. Also, if the *.ps1 file performs tasks that you’re user account doen’t have the permissions to, it will fail. Well duuhh, but I still want to mention it 😉
Note that this is not a security leak, it completely works as designed… as described in the ExecutionPolicy help
A few weeks ago I started writing a PowerShell module for the SCRUM methodology supporting online service named Trello.
To give you an idea, here’s a screenshot 3 days into this project:
I’m happy to announce that I’ll be releasing this module during the PowerShell Conference EU 2016 event.
If you’re into Windows PowerShell and haven’t registered for the event yet, I strongly suggest you take a look at the website and decide accordingly 😉
Hope to see you there!