Group policy doesn't work with Vista?

[Guest]

I have setup a group policy on our DC server that runs a VB script at logon
to map some network drives for client workstaions. it works great with our
XP workstations but not with Vista Workstations. i've coded the script to
notify user with a dialog prompt indicating drives are mapped. when i log in
vista, i do get the dialog prompt saying that the drives are mapped
succesfully, but none of the drive shows. what's interesting is that when i
run the actual script from the local pc after logged in, it maps all the
drives. so i know there is nothing wrong with the script.
does anybody have any idea whats going on?

 

[Guest]

This is just a thought, but try enabling the group policy setting to "Always
wait for the network at computer startup and logon". It will increase the
logon time a little bit. Also, how does your VB script determine that the
drives were mapped successfully before displaying this message?

 

[Guest]

thank you very much for the advise Sam. unfortunetly, it didn't work.
as for the script, i'm using an if else statement to check the drive letter
availability. if the drive letters are available, it will map the drives and
notify the user that all drives are mapped successfully. if drive letters
are taken, it will remove mapped drives and remap whats indicated in the
script, and notify user that drives are mapped. however, i did make sure in
the script that mapped drive letters are not conflicting with the local
drives.
any other suggestions? thanks.

 

[Guest]

I did some searching and came across this link, not sure if it applies in
your case but still interesting reading.

http://technet2.microsoft.com/Windo...878e-48db-a3c1-4be6ac7cf7631033.mspx?mfr=true

Look in the section " Group Policy Scripts can fail due to User Account
Control"

I am beginning to think vista is more trouble than what it is worth.

 

[Guest]

as you mentioned, this is really more trouble than what it's worth. MS is
great at messing things up.
i did find that disabling UAC worked, eventhough it's not prefered by MS.

 

[Guest]

There are a few ways to try and resolve some of these issues that you having.

I would create a .bat or .vbs script to remove all mapped drives at logoff
--> through GPO's of course

Also using the recommendation of Sam Yost, ensure that you set the a GPO to
ensure network connectivity prior to logon.

Third, ensure that you have your scripts to run Synchronous (one by one).
Issues can occur if mutliple scripts are running ASynchronous.. especially if
one depends on the setting of another.

Just my 2.5 cents..

 

[Gautam Anand]

See this -
http://technet2.microsoft.com/Windo...878e-48db-a3c1-4be6ac7cf7631033.mspx?mfr=true
<snip> UAC may prevent Group Policy logon scripts from appearing to work
properly. For example, a domain environment contains a Group Policy object
that includes a logon script to map network drives. A nonadministrative user
logs on to the domain from a Windows Vista computer. After Windows Vista
loads the desktop, the nonadministrative user starts Windows Explorer. The
user sees their mapped drives. Under the same environment, an administrative
user logs on to the domain from a Windows Vista computer. After Windows
Vista loads the desktop, the administrative user starts Windows Explorer.
The user does not see their mapped drives. </snip>

And further down below it shows how to fix it.

Now dont go about just disabling UAC - thats now the answer. The answer is
to alter the scripts.

- Gautam