Also remember this http://support.microsoft.com/kb/947222
One user at a time would mean a GPO filtered by group membership I would also recommend DFS, so you never have to do this again :). Convert to DFS, then change it in one go (e.g \\newserver\fldredir\%username%\my documents points to new DFS share called \\dfsroot\fldredir\%username%\my documents Then change policy for all to go to the \\dfsroot namespace. Set DFS replication to new server, then remove oldserver On Sat, Jul 12, 2014 at 12:00 PM, Jeff Steward <[email protected]> wrote: > Look into DFS would be my suggestion. You don't need the replication as > much as the namespace since if I understand your scenario correctly it > looks like you down the old server and bring up the new server after > restoring the folder structure. In that scenario, you then only need to > update the DFS link to point to the new server share - the DFS UNC path > doesn't change for the clients. > > -Jeff > > > On Thu, Jul 10, 2014 at 12:21 PM, David Mazzaccaro < > [email protected]> wrote: > >> Howdy all! >> >> >> >> Looking for some guidance on how to migrate My docs redirection from 2003 >> server to 2008 R2. >> >> Google tells me there is a lot of headache with this, but I am hoping >> this is a fairly common problem that some of you have dealt with. >> >> >> >> My thought process thus far is this: >> >> >> >> *For my local users:* >> >> * Create new GPO "My documents redirection to newserver" >> >> This GPO will redirect "my documents" to: >> >> \\newserver\fldredir\%username%\my documents >> >> >> >> New GPO settings: >> >> Redirect everone’s folder to the same location: >> \\newserver\fldredir\%username%\my documents >> >> Grant user exclusive rights to Documents (Enabled) >> >> Move the contents of Documents to the new location (Disabled) >> >> Also apply redirection policy to Windows 2000, 2003 (Enabled) >> >> Policy removal (Leave contents) >> >> Music: follow the documents folder >> >> Pictures: follow the documents folder >> >> Videos: follow the documents folder >> >> >> >> * Create AD group called "My Docs redirected to newserver" >> >> This is the only group that gets the new GPO "my documents redirection to >> newserver" applied to it. >> >> And will also be DENIED read permissions on the original GPO (not sure if >> I need to do this – my thinking is it will block the old GPO?) >> >> >> >> * Restoring from BackupExec will keep all existing folder structures and >> NTFS permissions >> >> >> >> * Restore oldserver\d\fldredir\%username% TO newserver\d\fldredir >> >> >> >> * Add the user to new group "My Docs redirected to newserver", so that >> they get the new GPO applied at logon, and will also be denied READ to the >> original GPO (just in case). >> >> >> >> * Have the use log on to get new GPO (verify new GPO applies, and my >> documents is redirected to \\newserver\fldredir\%username%\my documents >> >> >> >> >> >> *For my remote office citrix users: * >> >> * Do the same as above (to redirect their local PC My docs), but adding >> this step should also change their redirection when they are connected to a >> citrix server: >> >> >> >> * I already have an existing GPO that is redirecting My Docs to >> \\oldserver\fldredir\%username%\my documents >> >> So I will have to copy the existing GPO and change it to >> \\newserver\fldredir\%username%\my documents >> >> I can then use the same AD group mentioned above and deny read to >> original citrix GPO, and allow read to the new citrix GPO. >> >> >> >> >> >> *Thoughts:* >> >> * I need to restore from BackupExec because I need to avoid the computers >> dragging the contents of my docs from the original (oldserver\fldredir) >> across slow wan links back to their local PC, then back to >> (newserver\fldredir). >> >> * I need to create the new GPOs so that I can move one user at a time >> >> * How are offline files going to be affected for my laptop users? Will >> their laptops automatically configure the new >> \\newserver\fldredir\%username%\my documents to be offline? Will that >> cause an initial sync? >> >> >> >> >> >> Anyone have documentation on what has worked for them? >> >> Thx! >> >> >> >> . >> > >
