Anyone running Windows Server 2003 may find interest in a recent post from Microsoft’s Ask the Directory Services Team blog. It walks through the top 10 reasons why DFS Replication has performance problems and what you can do about them (meaning the DFSR service included with Windows Server 2003 R2, not the File Replication Service). The blog is involved, but the 10 reasons are:
1. Missing Windows Server 2003 Network QFE Hotfixes or Service Pack 2
2. Missing DFSR Service’s latest binary
3. Out-of-date Network Card and Storage drivers
4. DFSR Staging directory is too small for the amount of data being modified
5. Bandwidth Throttling or Schedule windows are too aggressive
6. Large amounts of sharing violations
7. RDC has been disabled over a WAN link
8. Incompatible Anti-Virus software or other file system filter drivers
9. File Server Resource Manager (FSRM) configured with quotas/screens that block replication
10. Un-staged or improperly pre-staged data leading to slow initial replication.
The blog seems to be a cool resource for server admins, offering Microsoft’s point of view on how to manage its server software.
If you know of other Windows Server resources, please feel free to share.
Go to Microsoft Subnet for more news, blogs, opinion.
More Micronet blog posts:
Exchange 2007 and WS2008 unhappy together
Bill Gates: Internet censorship just won’t work
Life at Microsoft … funniest video!
Windows Server 2008 new Migration/Editing utility
Windows Server 2008 Management and Maintenance tips
Fabulous giveaways from Microsoft Subnet and Cisco SubnetAll Micronet blog posts
Sign up for the bi-weekly Microsoft newsletter. (Click on News/Microsoft News Alert.)
