We are removing FRS from Windows Server
Today I’ll talk about what this means and how to get ready. We want this to be as easy as possible and I welcome any conversations that help you move forward with migrating to DFSR for SYSVOL replication.
Deprecation? Speak plainly!
FRS and DFSR both asynchronously replicate content sets of file data, and are included with Windows Server at no extra cost. Microsoft introduced the File Replication Service in Windows 2000 Server. We later replaced it with the Distributed File System Replication in Windows Server 2003 R2. Starting in Windows Server 2008, DFSR gained the ability to replicate SYSVOL on domain controllers and became the preferred engine.
With Windows Server 2008 R2, we deprecated FRS and reduced its replication capability to SYSVOL alone. You got FRS only if you created a new domain with a Windows Server 2003 or Windows 2000 domain functional level.
We also ensured that starting in Windows Server 2012, the default domain functional level for new domains was Windows Server 2012, to ensure that you never setup FRS in the first place. In Windows Server 2012 R2, you cannot even selecta functional level that uses FRS anymore when creating a domain through Server Manager or Windows PowerShell.
Why would you want a 2003 DFL? You miss so much other goodness!
Furthermore, TechNet states our FRS position for each OS:
- File Replication Service (FRS) Is Deprecated in Windows Server 2008 R2
- File and Storage Services Overview in Windows Server 2012 (Removed or Deprecated Functionality)
- Features Removed or Deprecated in Windows Server 2012 R2
We published the first article five years ago.
Deprecation simply means a product has reached obsolescence, often with a superseding feature. You should stop relying on it to exist in the future, stop expecting functionality changes, and stop expecting non-security bug fixes. After deprecation and enough warning time – at least one full OS release – we reserve the right to remove the feature.
Long before I became a Program Manager, I wrote an explanation of why FRS was inadequate and why you should shift to its replacement, DFSR. Those justifications are just as true today. Nevertheless, the biggest reason is the implicit one: why do you think Microsoft spent years and money writing a no-extra-charge replacement to its predecessor, unless the predecessor was fundamentally flawed?
We have finally reached the phase where continuing to “support” FRS is impossible; it’s a bit of a stretch to even say we’re supporting it now, as you cannot get bug fixes for it. DFSR is vastly more capable, reliable, and scalable. Most importantly, there is only one OS that requires FRS – and that OS is going away in 2015.
With the end of support Windows Server 2003 in July 2015, there will no longer be any technical requirement to keep FRS around. All supported OSes will happily replicate SYSVOL with DFSR. Thus ends the legacy. Whatever server operating system we ship afterJuly 2015 may no longer include the FRS binaries. You will not be able to promote that OS to be a domain controller in a domain that is still running FRS for SYSVOL, thereby blocking upgrades until you migrate to DFSR.
This is not an assurance that we are removing FRS from the next version of Windows Server. Some OS we release afterJuly 2015 will not have FRS. Just plan for the inside timeline and you cannot go wrong – migrate to DFSR before end of Windows Server 2003 support.
So now what?
Fortunately, moving from FRS to DFSR is a simple process that most customers perform in minutes. This migration procedure has been around for six years and after all that time, you only need to review oneKB article. Our process is solid and tested, with no migration bugs found in DFSR itself after Windows Server 2008.
In a separate blog post, I’ve outlined a DFSR “streamlined migration” that should remove some of the angst you might have from staring at a 52-page mega-super-complete migration guide. It’s possible to perform the entire migration with a single command – really!
Thousands of customers have migrated already and thousands more have deployed new domains with DFSR. Get your team onboard and knock this out – it won’t take long.
Until next time,