Link to home
Start Free TrialLog in
Avatar of justinmoore14
justinmoore14Flag for United States of America

asked on

GPO Not Applying Correctly To New Folder Path

Good Afternoon,

We have a 2008 R2 File Server that we are retiring and replacing with a 2012 R2 File Server. We will call the Server 2008 R2 (Server 1) and the 2012 R2 (Server 2).

There is a GPO setup to redirect the Documents, Desktop, and Favorites for each user to the following path. \\Server1\Users\....All users have logged off and I have changed the GPO Path for the Folder Redirection to the new server \\Server2\Users\  I have also manually already copied all the users files from Server1\Users to Server2\Users

However, when a user logs in they get an error they they can't find the \\Server1\Users\username\Documents, Desktop, Favorites path (I shut that server down so I could test). If I look in the event log there is a folder redirection error "Failed to apply policy and redirect folder "Documents" to \\Server1\users\username\My Documents.....redirection options = 0X9001 The following error occurred "Can not create folder \\Server1\users\username\My Documents....Error Details: "The network path was not found" ??

It can't find the path because the server is shut down....However, it is not supposed to be looking in there because it is supposed to be changing the path to \\Server2\users\username\My Documents....Any ideas why this is not applying?
ASKER CERTIFIED SOLUTION
Avatar of arnold
arnold
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
When transitioning from 2003 to 2008,2012 the issue deals with making sure to include features/services for fileserver that include the ntfrs service which is the file replication technology.
On 2008, I think it was services for Windows 2003.

If you did include these and sysvol/netlogon were not auto created, the burflags d2/d4 deals with jrnl_ related issue on the Existing DC that would have prevented the replication.

As to dfs (sharing based on ad domain name) which existed for some time, the issue mainly dealt with how one synchronizes data between locations, servers. Ntfrs is somewhat tolerable with small files. Often one had to use external scheduled tasks, etc such as robocopy to copy data from one to another...

Since 2003 R2, a completely new component was added to for dfs, dfs-replication which is a more robust, consistent file replication.
This simplifies local transition from target to target.. Setup replication between existing server and the new one. The top level security settings must be set on the folder before replication for simplicity. The replication process copies files, preserving ownership, attributes, etc.

There are different setup options.
Hub and spoke, I.e. Some shares can be peer to peer, data only available in HQ and on a branch.
Another can be a shared  folder that has data from all branches and HQ.
Dfs is a referral server such that it can be configured in layers meaning users at branches will access the local fileserver hosting, target of a dfs share and in the absence of this share, a next "lower cost" dfs target.....or the one in the HQ.
Avatar of justinmoore14

ASKER

Thank You! Also, appreciate you going into even more details in your last post. Hope you have a great rest of your week.