If you users are not admins on the box, then your first bullet is moot, which lends to DonJ’s comment regarding alternate creds as well.
.Ps1 files are only seen as text files on the system by default, for the reason DonJ points out. Sure, you could reassign all .ps1 extenuation to powershell.exe, but don’t, it will become and issue for you long term from a risk management (security) perspective.
You could send the script with a shortcut to the user, then double-clicking the shortcut, if properly configured (using the runas setup) would execute the script. Yet, again, if you are installing , stuff, that requires admin, and the user is not and admin, then you have an issue anyway.
You could use GPO and make it a run once thing on logon.
Yep, Sapien, PSS is a good tool, been using it for years now, but you can create PS .exe without it, especially if you are strapped for cash yourself, or your company is unwilling to pay the annual subscription for it.
Use the MS powershellgallery.com tools or stuff on TechNet.
PS2EXE-GUI: "Convert" PowerShell Scripts to EXE Files with GUI
Overworking of the great script of Ingo Karstein with GUI support. The GUI output and input is activated with one switch, real windows executables are generated. With Powershell 5.x support.
Create-EXEFrom.ps1: Create EXE from PowerShell script (with supplementary files)
Takes one PowerShell script and any number of supplementary files or even a directory and creates an exe using Windows’s built in iexpress program. The exe will run on any machine with PowerShell 2.0+.
Wrap your PowerShell scripts as Executables
In order to do this I am leveraging the awesome capabilities of PowerShell, allowing me to locate the compiler at runtime and compiling my wrapper code into an executable. So let’s examine this step by step.
PowerShell Executable Generator
See this discussion on the .exe thing as well. Just so you know.