Tuesday, July 17, 2012 2:01 AM
We have two sites that are in a DFS Namespace/Replication Group. All data is replicating except the created date isn't replicating resulting in OSX machines not being able to access the files. The OSX believes a file is in progress until it has a created date, so since DFS doesn't replicate the created date the user is unable to open the file. If the directory is copied locally from the server and the OSX machine is rebooted the files work fine. So all the data is getting replicated, it just has a date of 1946 as the created date.
If a utility is used to update the created date, all files are accessible by all sites and all end users.
Local data has a created date, its just the copy of the data replicated to the other site.
Thursday, July 19, 2012 1:54 AMModerator
Whether this issue occurs on new created file? For example, you could create a test file on one site and check the created date of the file which repliated to the other site.
In my test Created Date will be replicated correctly. So if new files are working fine, you could workaround this with running a command like this to update the time stamp:
robocopy <source> <target> /copy:T
TechNet Subscriber Support in forum |If you have any feedback on our support, please contact email@example.com.
- Marked As Answer by Shaon ShanMicrosoft Contingent Staff, Moderator Thursday, August 09, 2012 3:42 AM