new GPO settings conflict?

Quick question about publishing new group policy on Server 2008 Standard R2, and SBS 2003:
I need to create group policy objects that map network drives, and publish shortcuts to users desktops.  I see how to do this, however, many existing users already have the drive mapped.  Some may even have it mapped to a different drive letter.
If I force this group policy out, what will happen on users computers who already have the drive mapped, either to the same or different drive letter?  Is it safe to implement the policy with these preexisting user settings?
AE_JBAsked:
Who is Participating?
 
jeorgeConnect With a Mentor Commented:
0
 
smckeown777Connect With a Mentor Commented:
My understanding is the existing mappings from the old policy will not connect(i.e. if you are mapping a drive using old policy that will disconnect) and the new policy will map to the new drive

Now, if the drive mappings were similar letters then you shouldn't see any issue
If they are different letters then the clients will be affected(obviously), but the mappings will take place during login, so its not a big thing I wouldn't think...

But to do this correctly here's what I would do(always test prior to a full push to all clients)

Put a machine into a seperate OU in AD
Link the new policy to that OU
Run gpupdate /force on the client machine, logout the user, login the user...

Does the drive map?
If so you are good to go, if not you can then start the troubleshooting process...

Can you do that?
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.