Is it a bug in the DFS Management MMC or is it me?
OK, lets say you are using the new DFS Management console and you create a new DFS namespace (old name: DFS root) assign DFS namespace servers (old name: DFS root servers). After that you create a DFS folder (old name: DFS link) below the DFS namespace and configure DFS folder targets (old name: DFS link targets).
With the old "Distributed File System' MMC you were done ans NTFRS replication was auto configured after choosing the replication topology and its primary member.
With the new replication mechanism, after the creation of the DFS folder the system ask you if you want to setup replication using a replication group. Of course, we do! You assign a name for the replication group and the name of the replicated folder is entered automagically. Just a before you need to choose the primary member and the type of the replication topology. Additionally you need configure the schedule and the bandwidth used during replication.
OK, so far so good!
Now here it comes...
That was not the only DFS folder you wanted to configure. You want another DFS folder in the DFS namespace. As you a daredevil you just do that! Let's live dangerously! ;-))
Again: create a new DFS folder and configure DFS folder targets.
When ready, the system again asks if you want to create a replication group. Heck no, I want to use the previous replication group. Looking at the DFS folder configuration it says replication is not configured. Well, that's true... Lets click on the link to start the "Replicate Folder Wizard" and add the new DFS folder to the existing replication group. Damn, an error... it says: "the replication group already exists". Well, yeah.. I want to add a new DFS folder to an existing replication group...OK, canceling.
Lets try it another way...
Right clicking the replication group lets add a new replicated DFS folder. I assign the primary member, choose the folders to replicate, choose available replication group member servers and the path of the folder to replicate. Done!!!
So lets see if everything works...
* Accessing the DFS namespace --> works great!
* Accessing a DFS folder in the DFS namespace --> works great!
* Seeing the properties of a DFS folder in the DFS namespace using Explorer --> looking good!
* Checking if replication works --> works great!
* Checking the namespace configuration and folder referrals --> everything OK and all referral status is enabled for all referrals
* Checking the replication status of the DFS folder through the namespace node --> for the first DFS folder it is configured and for the second DFS folder it is not configured??? (replication is working as I just configured the stuff!)
* Checking the replicated folders through the replication group node and the existing replication group --> for the first DFS folder it says "published to the namespace" while the namespace path is showed and for the second DFS folder it says: "not published" while no namespace path is shown. Hmmm...
OK, right clicking the replicated folder and choosing "share and publish in namespace". Two possible options: "share and publish...." and "share....". Hmmm, I just want to publish as everything is already working. OK, lets use the first... All information entered and at the end it says something like: the DFS folder already exists in the namespace... ;-(( Yes, that is true, it already exists because I configure it so.
OK, opening LDP and navigating to "CN=Content,CN=ReplGroup001,CN=DFSR-GlobalSettings,CN=System,DC=ADCORP,DC=LAN". To child objects exist with their attibutes:
CN=FolderDocs,CN=Content,CN=ReplGroup001,CN=DFSR-GlobalSettings,CN=System,DC=ADCORP,DC=LAN
CN=FolderDocs,CN=Content,CN=ReplGroup001,CN=DFSR-GlobalSettings,CN=System,DC=ADCORP,DC=LAN
2> objectClass: top; msDFSR-ContentSet;
1> cn: FolderDocs;
1> distinguishedName: CN=FolderDocs,CN=Content,CN=ReplGroup001,CN=DFSR-GlobalSettings,CN=System,DC=ADCORP,DC=LAN;
1> instanceType: 0x4 = ( IT_WRITE );
1> whenCreated: 12/08/2005 15:05:19 W. Europe Standard Time W. Europe Daylight Time;
1> whenChanged: 12/08/2005 15:05:19 W. Europe Standard Time W. Europe Daylight Time;
1> uSNCreated: 42297;
1> uSNChanged: 42297;
1> showInAdvancedViewOnly: TRUE;
1> name: FolderDocs;
1> objectGUID: 9c978b45-5f41-4dfa-94f0-7b278b792029;
1> objectCategory: CN=ms-DFSR-ContentSet,CN=Schema,CN=Configuration,DC=ADCORP,DC=LAN;
1> msDFSR-FileFilter: ~*, *.bak, *.tmp;
1> msDFSR-DfsPath: \\ADCORP.LAN\DFSnamespace$\FolderDocs;
CN=FolderToolies,CN=Content,CN=ReplGroup001,CN=DFSR-GlobalSettings,CN=System,DC=ADCORP,DC=LAN
CN=FolderToolies,CN=Content,CN=ReplGroup001,CN=DFSR-GlobalSettings,CN=System,DC=ADCORP,DC=LAN
2> objectClass: top; msDFSR-ContentSet;
1> cn: FolderToolies;
1> distinguishedName: CN=FolderToolies,CN=Content,CN=ReplGroup001,CN=DFSR-GlobalSettings,CN=System,DC=ADCORP,DC=LAN;
1> instanceType: 0x4 = ( IT_WRITE );
1> whenCreated: 12/08/2005 15:23:54 W. Europe Standard Time W. Europe Daylight Time;
1> whenChanged: 12/08/2005 15:23:54 W. Europe Standard Time W. Europe Daylight Time;
1> uSNCreated: 42335;
1> uSNChanged: 42335;
1> showInAdvancedViewOnly: TRUE;
1> name: FolderToolies;
1> objectGUID: 04b94303-8f61-4adb-908a-9e16c785f9d1;
1> objectCategory: CN=ms-DFSR-ContentSet,CN=Schema,CN=Configuration,DC=ADCORP,DC=LAN;
1> msDFSR-FileFilter: ~*, *.bak, *.tmp;
For some reason the SECOND DFS folder does not have the "msDFSR-DfsPath" attribute populated. For the second DFS folder it should be: msDFSR-DfsPath: \\ADCORP.LAN\DFSnamespace$\FolderToolies;
So ,using LDP (ADSIEDIT will also work) I populated the attribute. OK, going back to the DFS Management console and kicking the refresh button.
The replication status now says: "Replicated using DFS replication" where it first said "not configured"
The publication status now says: "Published to the namespace" where it first said "not published"
As you can see by just changing the attribute everything is OK again. However, I would prefer to have the possibilty to:
* Assign a replicated folder to an existing replication group
AND/OR
* Besides the two options an additional option like: "Publish..."
Besides this...Working with DFS namespaces and replication in R2 is so much better and easier!!! I must say it: great work guys!
DFS-N and DFS-R = cool!