"Old" style relies still on FRS.
SYSVOL Replication with DFS-R
Windows Server 2003 R2 featured a revamped Distributed File Service (DFS)
that incorporated a brand-new file replication mechanism called DFS-R. It
uses remote differential compression, which substantially reduces file replication
traffic by determining which blocks of a target file need to be replicated
to bring it into sync with the source file. However, Windows Server 2003
R2 still uses File Replication Service (not DFS-R) to replicate SYSVOL between
domain controllers. Because of this, SYSVOL replication continued to be a
source of problems for Active Directory administrators.
When running at the Windows Server 2008 domain functional level, Windows
Server 2008 can replicate SYSVOL using DFS-R, improving the speed and robustness
of SYSVOL replication. And this makes it reasonable to place large files
in SYSVOL to make them available on all DCs. To use DFS-R for SYSVOL, you
must first migrate the old SYSVOL data to DFS-R using the DFSRMIG utility.
This process has four steps:
Create the Active Directory objects required by DFS-R.
Create the new file structure for SYSVOL on each domain controller.
Switch over all domain controllers to use the new SYSVOL.
Remove the old SYSVOL.
Depending on the size of your SYSVOL and the number of domain controllers
you have, this process may take a while, but the improved performance and
reliability make the effort well worth your while.
Also see here:
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
Post by Brandon McCombs
Isn't the SYSVOL already accessed through DFS? If a server doesn't
have it's DFS Client service running it can't access a DC's SYSVOL
share. I've run into that recently at work. Or do you mean something