Making a PowerShell Launch Pad Script

Making a PowerShell Launch Pad Script

One of the challenges that I have come across while trying to share PowerShell scripting tools was the fact that each person that you go to share the tool with needs to become familiar with the location of the new script, and the method of launching it. As you add more and more useful tools, the need for each person to remember how to access them becomes an issue. Consider that most people will use browser bookmarks or start menu shortcuts to access most of the sites or applications they use frequently, and access to a library of PowerShell scripts is no different.

Another issue I encountered was that a script might work fine on my test machines or my main workstation, but when it was launched on other systems there could be issues with execution policy.

So instead of dealing individually with each person and workstation each and every time a new tool was created, I thought up an idea to use a "launch pad" script as a starting point for all of the scripting tools. This way, a person only had to setup a shortcut one time, and then would have immediate and seamless access to each and every tool even as modifications or additions were made. 

Then instead of having to configure access to them, a simple notification email to inform them of the new functionality is all that is needed.

In case you might find something like that useful, check out the post I have here and let me know what you think...

https://gregbesso.wordpress.com/projects/powershell-launchpad-script/

To view or add a comment, sign in

More articles by Greg Besso

Explore content categories