Changed Group Policy Login Script Doesn't Map New Drives

Changed Group Policy Login Script Doesn't Map New Drives

Post by TmF0aGF » Mon, 13 Nov 2006 11:40:01



I moved our public share to another server and updated the Group Policy
login script map to the "public" drive to the new share. When users login,
however, it is still mapping to the OLD share. I suspect that the Windows XP
Client has cached this old login script because if I log in to a machine on
which the user would be a new profile, the mapping is correct. However, if I
log into a machine where my user profile previously exists, the old (and
wrong) drive mapping is used. Is there something I need to do to
"synchronize" the domain so my new Login script is executed? BTW, here is my
script:

net use * /del
net use K: \\server3\Public /persistent:no
 
 
 

Changed Group Policy Login Script Doesn't Map New Drives

Post by TWFyY3VzIF » Tue, 14 Nov 2006 18:47:01

On the machine that you are having problems with try the following;

1. Log on as normal, disconnect the mapped drive and make sure that the
reconnect at logon check box is unticked.
2. Start a commnad prompt and run "GPUPDATE /FORCE /LOGOFF"
3. Log back in to the machine.

MW

 
 
 

Changed Group Policy Login Script Doesn't Map New Drives

Post by TmF0aGF » Wed, 22 Nov 2006 00:41:01

Thanks Marcus for the comment. But I thought the whole point of Group Policy
is that I didn't have to go to each and every box on the network to do this
sort of thing--why wouldn't logging out and logging back in refresh the group
policy?