You can sign it, but it's not necessary for home use. Execution Policies in PowerShell are more about stopping users that don't know what they are doing then any real security - since if you launch .ps1 from Task Scheduler for example, then it runs even if the execution policy is set to restricted.pjknibbs wrote:You would also need to change the Powershell default setting which means it won't run an unsigned script, since there's no way you can sign the script yourself AFAIK.jack775544 wrote: Save that above code as SomeName.ps1. The only extra step you would have to do is change the Windows file association of ps1 files to be powershell instead of the default of notepad.
-RemoteSigned is best practice, but it's not the end of the world if Unrestricted for a home user.