I have had discussions with MS CSC about the correct way to preseed a DFSR folder before initial replication and I have come to the conclusion that in Windows Server 2008 there is no viable option that actually works in every case. And in many cases there is no workable option for preseeding a DFSR folder.
I have read many suggestion on these forums that MS folk have said will work and I can tell you from trying them they don't.
Firstly, the reason that preseeding is so difficult to get right, the the fact the two identical files with the same date and time stamps will be considered 'different' if the internal USN journal number (excuse me if I've got the name a bit wrong) has changed. They usually blame your Anti-Virus product for this.
Initial replication should do a bit more work and not rely on this very fallible method. Alternatively, Microsoft should recognise how fallible DFSR initial replication is and provide a tool for preseeding that actually works all the time.
So what are the recommended methods?
1. Use NTBackup to backup and restore the folder - works perfectly all the time in W2K3R2 - in W2K8 you're screwed (W2K8 doesn't have a USEFUL backup tool anymore, only windows backup).
2. Use ROBOCOPY - has a known bug if you need be copy the security descriptors - you're screwed. The bug has been known for ages and yet MS folk still recommend this method without warning of the limitations. Why has this bug not been fixed ages ago? Who doesn't need to copy the security descriptors on user data?
3. Use XCOPY instead of ROBOCOPY if you have to copy the security descriptors - unless you don't have access to the files (it has no backup mode) like redirected desktops and documents where the user has exclusive access (or the general manager who doesn't want the administrator geeks snooping his stuff) - you're screwed
4. Use the DFSR Preseeding tool that has none of the problems of the other methods above. Hasn't been written yet - you're screwed.
Any hope for W2K8R2 ?
Desperately preseeding,
Mark.
I have read many suggestion on these forums that MS folk have said will work and I can tell you from trying them they don't.
Firstly, the reason that preseeding is so difficult to get right, the the fact the two identical files with the same date and time stamps will be considered 'different' if the internal USN journal number (excuse me if I've got the name a bit wrong) has changed. They usually blame your Anti-Virus product for this.
Initial replication should do a bit more work and not rely on this very fallible method. Alternatively, Microsoft should recognise how fallible DFSR initial replication is and provide a tool for preseeding that actually works all the time.
So what are the recommended methods?
1. Use NTBackup to backup and restore the folder - works perfectly all the time in W2K3R2 - in W2K8 you're screwed (W2K8 doesn't have a USEFUL backup tool anymore, only windows backup).
2. Use ROBOCOPY - has a known bug if you need be copy the security descriptors - you're screwed. The bug has been known for ages and yet MS folk still recommend this method without warning of the limitations. Why has this bug not been fixed ages ago? Who doesn't need to copy the security descriptors on user data?
3. Use XCOPY instead of ROBOCOPY if you have to copy the security descriptors - unless you don't have access to the files (it has no backup mode) like redirected desktops and documents where the user has exclusive access (or the general manager who doesn't want the administrator geeks snooping his stuff) - you're screwed
4. Use the DFSR Preseeding tool that has none of the problems of the other methods above. Hasn't been written yet - you're screwed.
Any hope for W2K8R2 ?
Desperately preseeding,
Mark.