As long as you know they aren't in use that sounds about right. I generally use disable when I'm cutting someone over from one server to another, ie bring the second server online, disable referral immediately, wait for replication to complete, enable new server referral, disable old server referral, wait for all user connections to disappear before deleting old server.
If you do have any replication on there, you might want to stop that first by removing the replication group. Wait until each member server logs an event in the DFSR log that indicates the replication has stopped/been removed before moving to the next step, so you don't have a DFSR mess & open files to deal with. Before you tear down the root namespace, you might also check where everything has been shared from. Older iterations of DFS started from shares all created by hand (even the root), and it won't necessarily remove shares/folders when you're all done, so you'll want to check on those as well. -Bonnie -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Michael Leone Sent: Monday, April 20, 2015 7:34 AM To: [email protected] Subject: [NTSysADM] Starting with DFS OK, so I am trying to understand the mechanics of DFS. I get the theory -I define a namespace, and make new shared folder(s) in said namespace; I then add shared folders of servers into this DFS shared folder name. This way, DFS will replicate the new share contents into each of the shared server folders listed. Eventually, the idea is to create a "UserFolders" namespace and share; add in servers at each site to it; and change all the user profiles in AD to point to this DFS share. This way, when my users move job positions between sites [as they do more often than you might think], I don't have to go moving their home folders from one server to another in different sites; DFS will make sure it's available. Yes, it means having enough storage at each site. (that's simplified, and specific to my wants, I grant you) Anyway, one of our other admins who is since gone created a test namespace (in a specific site), folder, and added some server shares to it. And my boss wants it gone. (not that it's generating traffic, because we're not using it, but more as housekeeping cleanup). I am finding lots of webpages and articles on how to remove failed servers, ect, but not for doing this gracefully. Would the proper sequence to remove the folder targets, share and namespace be: Stop replicating each of the folder targets first Delete each folder target from DFS management Delete the DFS share Delete the namespace itself (in my case, I have a namespace "\\<domain>\Public"; a shared folder "DFSTest", which has 2 folder targets, which are server shares that are in different sites) Have I missed something? Should I be disabling things first, etc? Thanks. Sorry if it seems like such a n00b question, but I have very little experience with DFS (yet ...).
