I am in the middle of a transition from windows server 2003 to 2008, and am trying to redirect users' network drives from the old 2003 server to the 2008. Users have a U: drive which points to their personal folder on the server. I have made the change redirecting to the folder on the new server in the logon script, and applied it thru group policy.
All users are running vista SP1.
For some users this has worked OK, and their U: drive now points to the new server, but for a particular user the drive insists on pointing to the folder on the old server. I have run gpupdate /force on the workstation, no luck, also tried manually deleting the old mapping and creating a new one to the new folder. I've also enabled more aggressive processing in the site GPO by enabling computer configuration | admin templates | system | group policy | folder redirection / network shares policy processing | process even if no changes were made. Still maps to folder on the old server. Also if I set a local policy on her machine redirecting to the new folder, still no go.
By the way, folder redirection works for this user. Her desktop and documents open from the folder on the new server. Just that her U: drive keeps mapping to the old location.
Any suggestions much appreciated... thanks.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
OK, I think this has to do with group policy replication... I made the changes to the GPO on the new server, and think now that it may not have had a chance to replicate to the other, older DC in the site. So possibly there was a new logon GPO script stored on the new server, and the old GPO still on the old server.
I noticed also that problems were also occuring for other users.
How can I force replication of GPO info, including the logon script, between DC's? How does it normally happen, at what intervals?
Thanks.
hhmmmm, Not a good option I guess.. Nobody wants to do that...i mean...adding a DNS alias which will point to new server...
Lets Say, the server name is Test1
and Test1 is mapped as X:
And the new server name is Test1 & ip adress is also the same as old server.. And lets imagine old server is dead..
Still, you need to use.. Net use X: /delete..
and then, only you can map...
Logic is Simple.. If X Drive Exists in a Machine... no matter what ... you cannot map the drive X again...untill we delete it and add...
I can't really use the DNS option since I would like the old and new servers to both still be around for a coexistence phase, during which I'd make sure everything is working properly.
Instead of using the text command net use /delete, I just disconnected the drive from the GUI in Computer... should be the same, no?
In the meantime I'm reading up on group policy replication here: http://www.windowsnetworki
And will come back to this after I have a better grasp.
In the meantime, thanks all for the responses.
Just open the Sysvol folder to see the New Login Scirpts once.. Login Script is Pushed from SysVol and
not from Group Policy.. you may be refering to Group policy becuase of the complete process of desktop redietcion..
But network maping... in a Startup script is pushed from Sysvol folder ...while a machine starts and not htru any GP
SystemRoot\SYSVOL\Sysvol\D
Business Accounts
Answer for Membership
by: ShakerBrownPosted on 2009-10-08 at 02:13:43ID: 25523347
In your login script, add this line...just before the line, which maps the drive...
Net use U: /delete
after a month, once your are happy that all users are prompting to the new server...remove this line