We now have a KB article that we are keeping up to date with the latest files we recommend running for DFSR: KB 958802 – List of currently available hotfixes for Distributed File System (DFS) technologies in Windows Server 2003 R2KB 968429 – List of currently available hotfixes for Distributed File System (DFS) technologies in Windows Server 2008 and in Windows Server 2008 R2 3.

Out-of-date Network Card and Storage drivers You would never run Windows Server 2003 with no Service Packs and no security updates, right?

Has it always been too slow for your needs and now you’ve just gotten fed up? Check out the Windows Server 2003 Technical Reference for plenty of detail on Perfmon and visit our sister Ask Perf blog. EXE Propagation Test and Propagation Report By running DFSRDIAG.

officescan server not updating-41

Officescan server not updating video

Trust me when I say that vendors don’t release new binaries at heavy cost to themselves unless there’s a reason for them.

Check your vendor web pages at least once a quarter and test test test.

Dfsrdiag is installed when you install DFSR on the server. The time stamp is in FILETIME format which we can convert with the W32tm tool included in Windows Server 2003.

So for example: Backlog File Names (first 10 files) 1. Incidentally, this is something you can do in the GUI on Windows Server 2008 and it even gives you the replication time in a format designed for human beings!

Important note: If you are in the middle of an , you should not be rebooting your server! Wait it out, or assume the risk that you may need to run through initial sync again. DFSR Staging directory is too small for the amount of data being modified DFSR lives and dies by its inbound/outbound Staging directory (stored under \dfsrprivate\staging in R2).

By default, it has a 4GB elastic quota set that controls the size of files stored there for further replication. Because experience with FRS showed us having a hard-limit quota that prevented replication was A Bad Idea™. Because if Staging is below quota – 90% by default – it will replicate at the maximum rate of 9 files (5 outbound, 4 inbound) for the entire server.Missing Windows Server 2003 Network QFE Hotfixes or Service Pack 2 Over the course of its lifetime there have been a few hotfixes for Windows Server 2003 that resolved intermittent issues with network connectivity.Those issues generally affected RPC and led to DFSR (which relies heavily on RPC) to be a casualty. Today I’d like to talk about troubleshooting DFS Replication (i.e.the DFSR service included with Windows Server 2003 R2, not to be confused with the File Replication Service).Since there is a maximum of four (15 in Win2008) concurrent tasks, no further inbound replication can take place for the entire system.