Developer Forum

Power Shell RC1 doesn't seem to play nice with network $home directories. I
was not able to get a $home/My Documents/PSConfiguration/profile.ps1 script
to run when $home is located on a network share. It runs fine when logged
into a local-machine account (vs. logging into corporate domain), where $home
is defined as directory on the local drive.

Brandon Hamm
Sr. Software Engineer
Rogue Wave Software

What your execution policy?

In message < XXXX@XXXXX.COM >, Brandon
Hamm <lastname_at_roguewave_dot_com@?.?.invalid> writes

For reasons I still don't understand, remote scripts are not apparently
obeying Execution Policy. This is broken in RC1, IMHO, although no doubt
some MS marketing slug will try to justify it on the grounds of better
security.
--
Thomas Lee
XXXX@XXXXX.COM
MVP - Admin Frameworks and Security

In message < XXXX@XXXXX.COM >, The
Other Nice Man < XXXX@XXXXX.COM > writes

Mine is UNRESTRICTED (but it still fails).

--
Thomas Lee
XXXX@XXXXX.COM
MVP - Admin Frameworks and Security

RemoteSigned. I had also tried it with "set-executionpolicy unrestricted"
but it still failed.

Thanks,
Brandon

Brandon Hamm
Sr. Software Engineer
Rogue Wave Software

What error message are you getting?

Also, is the UNC path to the network share using a short netbios name or a
fully-qualified DNS name?

--
Jonathan White [MSFT]
Windows PowerShell Test Team
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.

No error message at all, the script just does not get executed. It's a
short netbios name, I have not attempted it with an FQDN.

-Brandon


Brandon Hamm
Sr. Software Engineer
Rogue Wave Software