You’ve probably noticed that when you double-click on a PowerShell script, it is opened for editing rather than being run. This is useful from a security standpoint, and while administrators have no problem opening up the shell and running the script, you’ve probably made something useful that you want to share with users, and users always need a bit more hand-holding.
Assuming that your PowerShell installation is in the default location, you need to append the path to your script in the shortcut path like so:
If you are wanting to run a PowerCLI (VI Toolkit) script, you also need to add
Add-PSSnapin VMware.VimAutomation.Core to your script, as the VMware Cmdlets are not loaded by default unless you run it from the VMware Toolkit Shortcut.