Ned Pyle, a Senior Escalation Support Engineer with the Directory Services team at Microsoft, has just started a new blog series focusing on DFS Replication.

 

Here’s how he introduces it:

 

Hello folks, Ned here again to kick off a new five-part series on DFSR. With the release of Windows Server 2008 R2, the warming of economies, and the timing of hardware leases, we have started seeing more questions around replacing servers within existing DFSR Replication Groups. Through the series I will discuss the various options and techniques around taking an existing DFSR replica and replacing some or all of its servers. Depending on your configuration and budget, this can range from a very seamless operation that users will never notice to a planned outage where even their local server may not be available for a period of time. I leave it to you and your accountants to figure out which matters most. This series also gives updated steps on validated pre-seeding to avoid any conflicts and maximize your initial sync performance. I will also speak about new options you have in this replacement cycle for clusters and read-only replication.

 

Here’s the series index:

  • Replacing DFSR Member Hardware or OS (Part 1: Planning)
  • Replacing DFSR Member Hardware or OS (Part 2: Pre-seeding)
  • Replacing DFSR Member Hardware or OS (Part 3: N+1 Method)
  • Replacing DFSR Member Hardware or OS (Part 4: Disk Swap)
  • Replacing DFSR Member Hardware or OS (Part 5: Reinstall and Upgrade)

 

You can read Part 1 right now at http://blogs.technet.com/b/askds/archive/2010/09/03/replacing-dfsr-member-hardware-or-os-part-1-planning.aspx