Hi,
I have posted the following onto the Office forums as well, but I think as the issue is very specific to DFS I'm not convinced that forum is necessarily the best place.
System setup.
We have two servers, in two separate sites. Both sites work on the same set of data, with the data replicated between the two servers using DFS.
The customer recently migrated to using Office 365 for email and at the same time to Office 2013.
The issue
The user at "site a" opens email attachments within Outlook 2013. Lets say its a photo, from the Windows Photo viewer program the user then saves the attachment to a location within the DFS share. This issue wasn't seen in Outlook 2007.
Then, a user at "site b" goes to the folder where the user at "site a" saved the photo and sees nothing there.
As IT admin we then look at the DFS queues and do not see the file queued, we look on the server at "site a" and can see the file is present and check on the server ate "site b" and the file is missing.
Moving the file out of the folder and back in the file then replicates.
Trying to fix it
After a lot of investigation determined that the files have a temporary file attribute (seeMSDN Blog) . DFS does not replicate files with this attribute (this is by design, see Technet blog).
Now when opening an attachment Outlook saves the attachment to the Outlook Secure Temp folder it sets the file with this temporary attribute. This attribute appears to be transferred by the application (including Microsoft programs eg the Windows Photo viewer) when saving the file.
Can Outlook be prevented from created files with this attribute? Has anyone else seen this issue, what can I do to prevent it?
Thanks