Check this post from Lee's blog: http://www.leeholmes.com/blog/PowerS...ardImages.aspx
"One way to fix this is by adding the source server to Internet Explorer’s
Trusted Sites, or
changing the “UncAsIntranet” configuration property (http://technet.microsoft.com/en-us/l.../bb457150.aspx
This is also covered on page 341 of the (my) PowerShell Cookbook."
Windows PowerShell MVP http://blogs.microsoft.co.il/blogs/ScriptFanatic
PowerShell Toolbar: http://tinyurl.com/PSToolbar
JR> i've been lazy about figuring out how to do the script signing,
JR> really need to do that. mostly im curious as to why this acts as it
JR> i run this script on all my servers (which is why i run it from the
JR> UNC, no deployment needed if changed) and it works fine on every
JR> other system.
JR> "Vadims Podans [MVP]" <vpodans> wrote in message
>> you have 2 ways:
>> 1) sign scripts
>> 2) schedule batch file which should contain something like this:
>> copy \\server\share\file.ps1 %temp%
>> %SystemRoot%\system32\WindowsPowerShell\v1.0\powershell.exe -command
>> del %temp%\file.ps1
>> WBR, Vadims Podans
>> MVP: PowerShell
>> PowerShell blog - www.sysadmins.lv
>> "Justin Rich" <jrich523@xxxxxx> rakstija zinojuma
>>> i RDPed in to a 2k3R2 SP2 server with my AD account, set the
>>> execution policy to unrestricted and ran my script hosted on a UNC
>>> path, worked great. i created a schedule task under a different
>>> account (local with admin rights) and i ran it, and it hung. after
>>> some troubleshooting i created a shortcut to cmd, changed the run as
>>> to that account and ran the commandline syntax for the schedule task
>>> (powershell \\server\file.ps1)
>>> when i did that, i got the security warning again. did a check on
>>> the execution policy and it was still listed as unrestricted....
>>> what am i missing?