This is more of a rant than anything, but I feel that its very cheap of Cisco to have left the CLI out of their CE500 line. I know that the switch is marketed to the SMB, but common places with 50-250 users still might want the CLI for remote/automated management. Not everyone in the SMB IT dept is a GUI only nut.
Some of us dont feel the need to purchase a $2000+ switch for PoE, and dont need L3 routing forced on us to get PoE. The CE500 does a fine job at switching, and PoE. Just put the darn CLI in the CE500. OK Cisco!
Thursday, December 20, 2007
Sunday, December 9, 2007
Fixing DFSR after an AD domian rename
After renaming an Active Directory domain DFS Namespace Folders no longer recognize their Replication Groups. The Replication Groups are not updated during the normal domain rename process, and replication fails between members.
In the DFS Management tool the Namespace Folders will not display as having replication configured, and the Replication Groups will display old DFS Namespaces. To resolve this issue the DFS Replication Groups must be manually updated to reflect the domain name changes made. This can be accomplished using ADSIEdit tool found in the Windows 2003 Support Tools.
1. Open ADSIEdit.msc.
2. Locate the DFS Replication Group settings “Domain\DC=domain,DC=com\CN=System\CN=DFSR-GlobalSettings”.
3. Rename each of the effected Replication Groups using double slashes between sections of the Replication Group Name. “CN=domain.com\\{DFSRNamespace}\\{DFSRFolder” the double slashes will automatically be removed after you refresh “Domain\DC=domain,DC=com\CN=System\CN=DFSR-GlobalSettings”, but are required for some of the calculated values for the DFS Replication Group to be correct.
4. For each Replication Group correct the “msDFSR-DfsPath” value to reflect the correct DFS Namespace Folder for this Replication Group. This is located in “Domain\DC=domain,DC=com\CN=System\CN=DFSR-GlobalSettings\{DFSRNamespace}\{DFSRFolder}\CN=Content\ CN={DFSRFolder}” This value should reflect the new DFS Namespace, and Folder. Example “\\domain.com\{DFSRNamespace}\{DFSRFolder}”
Now when you open DFS Management tool all your Namespace Folders should be correctly linked to their proper Replication Group.
In the DFS Management tool the Namespace Folders will not display as having replication configured, and the Replication Groups will display old DFS Namespaces. To resolve this issue the DFS Replication Groups must be manually updated to reflect the domain name changes made. This can be accomplished using ADSIEdit tool found in the Windows 2003 Support Tools.
1. Open ADSIEdit.msc.
2. Locate the DFS Replication Group settings “Domain\DC=domain,DC=com\CN=System\CN=DFSR-GlobalSettings”.
3. Rename each of the effected Replication Groups using double slashes between sections of the Replication Group Name. “CN=domain.com\\{DFSRNamespace}\\{DFSRFolder” the double slashes will automatically be removed after you refresh “Domain\DC=domain,DC=com\CN=System\CN=DFSR-GlobalSettings”, but are required for some of the calculated values for the DFS Replication Group to be correct.
4. For each Replication Group correct the “msDFSR-DfsPath” value to reflect the correct DFS Namespace Folder for this Replication Group. This is located in “Domain\DC=domain,DC=com\CN=System\CN=DFSR-GlobalSettings\{DFSRNamespace}\{DFSRFolder}\CN=Content\ CN={DFSRFolder}” This value should reflect the new DFS Namespace, and Folder. Example “\\domain.com\{DFSRNamespace}\{DFSRFolder}”
Now when you open DFS Management tool all your Namespace Folders should be correctly linked to their proper Replication Group.
Subscribe to:
Posts (Atom)