Sign up for the ITPro Today newsletter
Stay on top of the IT universe with commentary, news analysis, how-to's, and tips delivered to your inbox daily.
Assessing your organization’s DFS deployment
Although the setup looks the same and the topology options remain familiar for those that have deployed DFS with Windows Server 2003, there have been substantial improvements with DFS with the releases of Windows Server 2008, Windows Server 2008 R2, Windows Server 2012 and Windows Server 2012 R2.
Orin Thomas
March 3, 2015
1 Min Read
Although the setup looks the same and the topology options remain familiar for those that have deployed DFS with Windows Server 2003, there have been substantial improvements with DFS with the releases of Windows Server 2008, Windows Server 2008 R2, Windows Server 2012 and Windows Server 2012 R2.
Improvements in DFS include:
Failover cluster support
Read-only replicated folders
Scale improvements, up to 100 TB of data
Windows PowerShell module for DFS Replication
Database cloning for initial sync
Database corruption recovery
Cross-file RDC disable.
Restore files from the ConflictAndDeleted and PreExisting folders
Unexpected shutdown database recovery
DFS Management support for enabling access-based enumeration
Performance improvements for large namespaces
Prior to migrating a Windows Server 2003 DFS deployment to Windows Server 2012 R2, ensure that you have documented your organization’s current DFS deployment. This involves making note of:
DFS replica locations
Approximate DFS replica content
DFS topology
DFS namespaces
When looking at your organization’s DFS deployment, also start thinking about whether some of the data that is currently stored in DFS can be moved into an archive location, rather than being replicated around your organization.
In the next post, I’ll discuss methods of migrating your DFS deployment from Server 2003 to Server 2012 R2.
About the Author
You May Also Like
.jpg?width=700&auto=webp&quality=80&disable=upscale)
