we have just set up dfsr replication. after the replication was completed we noticed that the new server did not have all the files. after some research we learned that files that have the attribute temporary can not be replicated. we found the tool to change the attribute but it concerns me that we may create future files that have the "t" attribute. there was no pattern to the file type, adobe, office and cad files randomly had the attribute "t". what could be causing the attribute to change? thanks for your help.

Are they just normal, expected temp files used by applications? In that case you don't want them replicated because they won't be used by anything when they are copied to another server because they are only used locally by whatever application created them. If these are definitely not temp files created as expected by applications, possibly some application is scanning through that location and inadvertantly marking them as temporary. In that case you'd have to set up some type of auditing or monitor to determine what application is setting the temporary attribute. You may have seen this: http://blogs.technet.com/b/askds/archive/2008/11/11/dfsr-does-not-replicate-temporary-files.aspx This is a PowerShell command to display all the files with the temporary attribute. Change the "D:\Data" to be the path you want to inspect. Get-childitem D:\Data -recurse -force | where {$_.attributes -match "temporary"} | ft fullname,lastwritetime,attributes -autosize Or you can export the list to CSV to view in Excel. Get-childitem D:\Data -recurse -force | where {$_.attributes -match "temporary"} | Export-Csv tempfiles.csv Once you can easily see what they all are, it may become apparent that they are in fact just temp files for applications and therefore you don't want them replicated, or they are not, and you need to find out what is setting the temp attribute.

thanks for input. the files are not supposed to be temporary files. i have found files associated with adobe, office and microstation (cad) that have the temporary attribute assigned to them. we have used the powershell command to correct the attribute and then they replicate fine....but i am concerned moving forward with this process. i need to know why these files attributes were changed.brian nilson