I came across a DFS replication problem between 2 Win2K8 servers recently and while searching about it on the net, i found several pages mentioning a "Temporary" file attribute. Apparently, this can be turned ON/OFF via Powershell (here's a related link). TC does not seem to have such a capability. It may be useful to some people if such capabilities (for "advanced" / rarely used attributes - i don't know if there are others) could be added.
Christian, do you think it's worth the trouble?
DFS: how handle "Temporary" file attribute?
Moderators: Hacker, petermad, Stefan2, white
DFS: how handle "Temporary" file attribute?
- Wanderer -
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
Normally using latest TC on:
x32: WinXPx32 SP3 (very rarely nowadays).
x64: Clients/Servers - Win10/Win11 and Win2K16 to Win2K22, mainly Win10 though.
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
Normally using latest TC on:
x32: WinXPx32 SP3 (very rarely nowadays).
x64: Clients/Servers - Win10/Win11 and Win2K16 to Win2K22, mainly Win10 though.
I think it may be easilly changed via content plugin that supports such attribute:) I think function SetFileAttributes should do it.
However since only opened files may have such attribute, there may be some problems with removing it if file is opened with exclusive write access...
However since only opened files may have such attribute, there may be some problems with removing it if file is opened with exclusive write access...
Perhaps. It would be nice if it was somehow supported.MVV wrote:I think it may be easilly changed via content plugin that supports such attribute:) I think function SetFileAttributes should do it.
I don't think so. I have a closed file that DFS Replication process reports as "temporary" (even after restarting both servers).MVV wrote:However since only opened files may have such attribute
- Wanderer -
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
Normally using latest TC on:
x32: WinXPx32 SP3 (very rarely nowadays).
x64: Clients/Servers - Win10/Win11 and Win2K16 to Win2K22, mainly Win10 though.
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
Normally using latest TC on:
x32: WinXPx32 SP3 (very rarely nowadays).
x64: Clients/Servers - Win10/Win11 and Win2K16 to Win2K22, mainly Win10 though.
I have the same problem here and the reason is also related to DFS troubles.
Is there already a way to identify files with temporary attribute set
See possible attributes here: https://blogs.technet.microsoft.com/askds/2008/11/11/dfsr-does-not-replicate-temporary-files/
Thanks Wolle
Is there already a way to identify files with temporary attribute set

See possible attributes here: https://blogs.technet.microsoft.com/askds/2008/11/11/dfsr-does-not-replicate-temporary-files/
Thanks Wolle