|English: This is a photo of a room full of computers all showing the same windows error message at the Nanyang Technological University in Singapore (Photo credit: Wikipedia)|
Many would agree that the self service portal is a bit restricted and we needed a method for our Apps group to submit Change Requests that would comply with SOX.
I found a few examples around the net regarding the power of SMLets and PowerShell and eventually found that there are classes available in .Net for leveraging this.
My first major hurdle was determining why I kept getting a strange error message "Unable to access Windows PowerShell PowerShellEngine registry information." when trying to replicate these efforts.
My errors seemed to stem from trying to use assemblies built with prior versions of the .Net library, and instead of writing a wrapper of some sort to deal with this, I installed PowerShell 3 and all my problems went away. (Small clue here)
The caveat to this is that this new flavor is known to cause issues with Sharepoint, Exchange, Configuration Manager and SBS to name a few so read up on the known issues before you create an unresolvable issue.
I chose to deploy my solution into our DEV SCSM environment in same IIS Portal Site area, using our service account application pool created for this purpose. Windows Authentication is also Enabled for this site so we can pick up the users name in the application and use it in the Created By field in the ticket.
You can grab a copy of this project here.