locked
Tried Migrating DFSR namespace from 2000 to 2008 RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I added a new DFSE Member and ran into an issue that led me to Follow along on this article to fix a connection issue: Migrate a Domain-based Namespace to Windows Server 2008 Mode - https://technet.microsoft.com/en-us/library/cc753875.aspx

    I've run into an issue where the replication group is intact, the name space seems to be intact, though they don't know about each other's stuff. 

    Within the Namespace, I select a shared folder, then I can see the folder Targets. Though under Replication, nothing is listed. Clicking the 'Folder Replication Wizard' link gives me an Error saying 'The Followinf targets cannot be added to DFS Replication Members, then lists each target with the error: the shared folder path D:\<Path> is already replicated on the server using replication group (Repl-GroupName)

    The Replication Group says its 'Not Published'.  If I go to publish it, it says that there already exists a folder called \\domain\namespace\share

    I can Access the Namespace with \\domain\<NameSpace>\Share with no issues.

    The Replication group is replicating. 

    Monday, March 23, 2015 6:35 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Actually the migrate to 2008 Mode is a process for backup existing namespace, delete and import with an updated namespace.

    From the description, both "the shared folder is already replicated" and "there already exists a folder" could be caused that the "remove" part is not done yet or it is not finished correctly, which causes some information still exists in AD.

    Here is a thread which related to check DFSR configuration in AD. Please refer the steps to see if any old DFSR configuration could be found. Delete them to redo the import step in the article you mentioned. 

    a. Open ADSIedit.msc.
    b. Connect to Default Naming Context (the domain name)
    c. Expand and locate the container, which show the DFS root information
    CN=<name_of_the_DFS replication group>,CN=DFSR-GlobalSettings,CN=System,DC=<name_of_your_domain>


    http://social.technet.microsoft.com/Forums/en-US/winserverfiles/thread/a7724837-b80a-436b-89df-97bb189bcecc

    Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Tuesday, March 24, 2015 3:18 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I so went though the delete and re-add procedure, 

    When doing the root adddom I get the Following:

    PS C:\Users\Scott Townsend> Dfsutil root adddom \\domain.name.com\DFSShare

    Could not complete the command successfully.
    SYSTEM ERROR - The object identifier does not represent a valid object.
    PS C:\Users\Scott Townsend> Dfsutil root adddom \\SVR-DFSFileServer.domain.name.com\DFSShare
    Could not complete the command successfully.
    SYSTEM ERROR - Access is denied.

    So I went into DFS Management and Created the Namespace in the GUI.

    Then I ran the Import

    PS C:\Windows\system32> Dfsutil root import merge  c:\scripts\dfsr\DFSShare\vmnamrspace-v2.xml  \\domain.name.com\DFSShare
    Backup of \\HAYDON-MILL\DT before modifications being written to domain.name.DFSShare.dfsutil.backup.03.25.2015.16.51.17.666
    NetDfsSetInfo Priority <Class SiteCostNormal, Rank 1> failed for \\domain.name\DFSShare (SVR-DFSFileServer, DFSShare), Status 490
    Update Statistics: Number of Apis 26
    Links: Added 5 Deleted 0 Modified 5
    Targets: Added 14 Deleted 0 Modified 0
    Root: Attributes Modified 1Done processing this command.

    I'm still getting the same results.   Under Namespace Replication folders don't show up and adding says they already exist. 

    under Replication, Publish, it says namespace is already there.  Should I not be doing the Import?

    Thursday, March 26, 2015 12:07 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    So you can find some information inside ADSIedit, you deleted them but still cannot recreate DFS namespace?

    Let's breakdown these steps.

    1. Find and delete any old information left in ADSIedit.

    2. Perform an AD replication or just reboot.

    Force AD Replication with:
    REPADMIN /syncall /Aed

    3. I noticed that you received an Access Denied error in Powershell. Are you using an Domain Admin account in running that cmdlet?

    Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Thursday, March 26, 2015 8:36 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Form the top, here is what I did:

    Delete Namespace

       I delete the Namespace using the GUI, No Errors. 
       Add Namespace to Display, it does not show deleted namespace. 
       In ADSIEdit - CN=Dfs-Configuration,CN=System,DC=DOMAIN.NAME,DC=com - Namespace is not listed

    Replicate
    I had been using my repadmin scripts to do replication, though they were from 2003, I really like the /Aed option! Sweet!


    Recreate Namespace. 
    Using Domain Admin account in a Admin Command prompt on a AD DC Server I tried:
    Dfsutil root adddom \\AD_DomainName.com\DFSShare  (this is what the KB said to use)
    Could not complete the command successfully.
                    SYSTEM ERROR - The object identifier does not represent a valid object.

    Dfsutil root adddom \\SVR-AD-DC-Name.DoaminName.com\DFSShare   (tried with DC Server Name)
    Could not complete the command successfully.
    SYSTEM ERROR - There is no such object on the server.

    Dfsutil root adddom \\SVR-DFSServer-Name.DoaminName.com\DFSShare   (tried with DFS Replica Server Name)
    Could not complete the command successfully.
    SYSTEM ERROR - This shared resource does not exist.

    Using DFS Management on SVR-DFSServer-Name.DoaminName.com

    Review Namespace Settins
    Namespace name: \\AD_DomainName.com\DFSShare
    Namespace type:  Domain (Windows Server 2008 mode)
    Namespace server: SVR-DFSServer-Name
    Root shared folder:  A shared folder will be created if one does not exist.
    Local path of namespace shared folder: C:\DFSRoots\DFSShare
    Permissions for namespace shared folder: Custom permissions
    Status = Success - No Errors


    There are no Folders in the Namespace in DFS Management

    Import DFS Namespace settings. 
    Using Domain Admin account in a Admin Command prompt on a DFA Replica Server I tried:
    Dfsutil root import merge  c:\scripts\dfsr\DDFShare\namespace.xml  \\AD_DomainName.com\DFSShare

    Backup of \\AD_DomainName\DFSShare before modifications being written to AD_DomainName.DFSShare.dfsutil.backup.03.26.2015.10.11.08.227
    NetDfsSetInfo Priority <Class SiteCostNormal, Rank 1> failed for \\AD_DomainName\DFSShare (\SVR-DFSServer, DFSShare), Status 490

    Update Statistics: Number of Apis 26
    Links: Added 5 Deleted 0 Modified 5
    Targets: Added 14 Deleted 0 Modified 0
    Root: Attributes Modified 1

    Done processing this command.


    In DFS Management GUI
    Namespace
    Select Folder Name,
    Select 'Folder Targets' Tab
    All Targets Present
    Select Replication Tab
    Replication Status: Not Confgured
    Click 'Replicate Folder Wizard'
    \\server1\share - the shared folder path (c:\path) is already replicated pm tje server using replication group (DFSShare)
    \\server2\share - the shared folder path (c:\path) is already replicated pm tje server using replication group (DFSShare)
    \\server3\share - the shared folder path (c:\path) is already replicated pm tje server using replication group (DFSShare)
    Replication
    Select Replication
    Select 'Replication Folders' tab
    Publication status: Not Published
    Right Click Folder, select 'Share and Publish in Namespace'
    Select Share and Publish
    Servers with replicas are listed, each with Existing Share
    Enter Parente Namespace: \\AD_DomainName.com\DFSShare

    Publishing Method:
    Share and publish the replicated folder in a namespace. 

    Shared Folder Names:
    server1 : Use existing shared folder: share
    server2 : Use existing shared folder: share
    server3 : Use existing shared folder: share

    Publish Using Namespace Path:
    \\AD_DomainName.com\DFSShare\share

    Create Folder Targets(3):
    \\server\share
    \\server2\share
    \\server3\share
    Create Folder Error:
    \\AD_DomainName.com\DFSShare\share cannot be created om the namespace the folder already exists in the namespace
    \\AD_DomainName.com\DFSShare\share cannot be created om the namespace the folder already exists in the namespace
    \\AD_DomainName.com\DFSShare\share cannot be created om the namespace the folder already exists in the namespace


    Thursday, March 26, 2015 10:48 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I had the same issue when I upgraded my DFS to 2008 from 2000.

    The error "SYSTEM ERROR - The object identifier does not represent a valid" kept happening when I tried to add the DFS back.

    To fix it, first make sure it is removed using ADSIEDIT.  Here's the path:

      Default naming context [domain.xxx.com]
        DC=xxx, DC=com
          CN-System
            CN=Dfs-Configuration
              CN=DFSRootThatYouAreTryingToRecreate

    If you see the DFS root that you are trying to create under Dfs-Configuration, delete it and replicate your domain controllers.  Close ADSIEdit.

    Now, add the DFS Root using the DFS Management utility.  When you point it at your DFS root share, it will say "the folder already exists, do you want to keep the existing permissions?"  Go ahead and keep the permissions of the existing folder.

    After the DFS creation wizard has finished, you should see a healthy DFS root.  Now you can use DFSUtil to import merge the DFS xml file that you exported earlier.  Don't forget to manually add your other DFS namespace servers.  Again, you'll get the same message about the DFS root folder already existing for each server you add.


    • Edited by Brain2000 Thursday, June 11, 2015 11:12 PM
    • Proposed as answer by Brain2000 Thursday, June 11, 2015 11:12 PM
    Thursday, June 11, 2015 11:09 PM