Currently I've got a few sites running mostly Windows Server 2003 R2 SP2 boxes. We have recently begun deploying quite a few 2008 boxes to retire these 2003 boxes. We have a domain-based DFS namespace (\\domain.local\Shares) that is replicating about 30GB worth of data between two file servers at two different sites. One of these file servers is gonna die so I need to move everything off of it and shut 'er down. I have a few questions:
1) The file server that is dying is the DFS root. I'd like to establish two of my domain controllers as the DFS roots for resiliency. Can I add the DFS role to these two DC's, add them as roots, and then remove the root from the dying file server without causing any downtime??
2) Are there any gotchas with having one of the replication targets a 2008 server and one of the replication targets a 2003 server??
3) Should I use DFSUtil to do this or the snap-in??
4) Any other adivce??
Thanks ahead of time.
I hate all Uppercase... I don't want my groups to seem angry at me all the time! =)
- ColdFlame (vbscript forum)
1) The file server that is dying is the DFS root. I'd like to establish two of my domain controllers as the DFS roots for resiliency. Can I add the DFS role to these two DC's, add them as roots, and then remove the root from the dying file server without causing any downtime??
2) Are there any gotchas with having one of the replication targets a 2008 server and one of the replication targets a 2003 server??
3) Should I use DFSUtil to do this or the snap-in??
4) Any other adivce??
Thanks ahead of time.
I hate all Uppercase... I don't want my groups to seem angry at me all the time! =)
- ColdFlame (vbscript forum)
