How to Run PowerShell Scripts from a Shared Directory

re: How to Run PowerShell Scripts from a Shared Directory

Roderick McBan — Mon, 13 May 2013 05:51:55 GMT

I found a different workaround for this issue.

On the server where I wanted to run the powershell script, I created a directory link pointing to the unc path containing my PS1 file.

Running powershell -f [dir_link]\myScript.ps1 went through with no problems.

It appears to work on several of my servers.

RMcB

re: How to Run PowerShell Scripts from a Shared Directory

Ed Wilson — Sat, 17 Nov 2012 10:44:01 GMT

@K_Schulte One thing you may want to see is where your shared scripts are stored. For instance if they are on \\webserver1\shared but on your computer \\webserver1 is NOT listed in Trusted Sites in Internet Explorer, then you will still be prompted with warnings when you try to run the script -- EVEN if you have the Script Execution Policy set to Unrestricted. This is because PowerShell trusts Internet Explorer to set the security zones. NOW, if you ADD \\WebServer1 to the Trusted Sites in Internet Explorer, if your settings are set to Unrestricted, then you will not be prompted for a warning. It is possible that when you ended up in a different OU, then you have a different Group Policy. Often in a corporate environment Trusted Sites is set via Group Policy (but it is a registry setting). If you cannot make these changes, start powershell with the execution policy of BYPASS and you will not be prompted.

re: How to Run PowerShell Scripts from a Shared Directory

K_Schulte — Tue, 30 Oct 2012 07:46:43 GMT

Hi Judith, Hi June

thank you very much for this interesting blog article!

But first of all, I'd like to tell you, That we all cross our fingers here ... hoping that "Sandy" will not do too much harm to the (east of the) United States!!!

I thought that we have the problem which you are presenting here, too!

Since I have received my new company workstation running WIN7 x64 Enterprise, I couldn't run scripts from an intranet network share. My old PC running WIN7 x64 Pro, still doesn't complain when I try to run my scripts.

So it must have something to do with the workstation settings itself.

I had been told, that the new PC has been put into another new AD OU and will reveive some different group policies.

So I already asked people in the forum here, what I could do to prevent my PowerShell scripts from being blocked,

because I always received the error message telling me, that my files are not digitally signed.

The proposed final solution was: Sign your scripts! Which is not a bad idea of course, but nearly impossibe here.

I did relax the execution policy to unrestricted which is not a good idea, but it still was accompanied with warnings, telling me that it may be dangerous to run my scripts.

So I tried to set the registry key UNCasIntranet now, which is an option that I can still change on my own,

But this is still no solution to the problem, because I can't recognize any different behaviour by now. In fact the "local intranet options" are grayed out and always show " Include all network paths (UNCs)" to be checked regardless of any changes to the registry key. This seems to be preset by GPOs and if I got you right, this should be the correct setting anyway.

It would be great, if you can help me out ... if you still have any ideas, what might solve the riddle here ...

Klaus.