Yeah. No joke. That isn't a typo.
Let me repeat that because it bears repeating.
You can run Powershell v4, 64bit, natively in Orchestrator 2012.
NO TUNNELING.
NO SESSIONS.
NO MORE RETURN VARIABLES AS OBJECTS FROM A REMOTE SESSION NONSENSE.
How? Lies you say?!
Will Udovich (of Cireson) and his finding of a SINGLE blog on the internet from "TechGuy" Michael Seidel mention this little registry hack. One blog? ONE BLOG?!?! Grab anything you can that makes loud noises and make sure EVERYONE knows about this.
That's it! ONE FREAKING REGISTRY KEY!!! Now Run .NET Script will let you execute things like "Get-ADUser" natively!!!
I could not believe what I was reading until I fired up my development environment, added this registry key and watched it work exactly like any one would expect it to.
Also, in the event it wasn't clear...my reaction to all of this can be summarized by the opening gif.
Thank you for re-sharing! My heart just freaking leaped out reading this. So much pain and suffering... no longer. Come Powershell we have work to do.
ReplyDeleteThis allows you to run the latest Powershell version but doesn't change the architecture to x64
ReplyDeleteI know this is late, but of course M$ said "They do not support this change". From everything I have seen by others that are doing this, there have been zero issues. And even better you can implement this via powershell script...
ReplyDelete