none
problems with migration of FRS to DFSR SYSVOL

    Question

  •  

    Hi,

    just promoted new 2016 server to DC and it mentioned that we need to migrate FRS to DFSR replication.

    so I started to follow these instructions

    https://blogs.technet.microsoft.com/filecab/2014/06/25/streamlined-migration-of-frs-to-dfsr-sysvol/

    I started with "Quick" migration

    1. Ensure free disk space - OK

    2. Ensure correct security policy - OK

    3. Ensure AD replication is working - OK

     - there were few errors with Active Directory Replication Status Tool but after I rebooted all the DC server (three of them) and our Exchange those erros went away. probably something to do with the dcpromo and schema changes. but eventually no errors there

    4. Ensure SYSVOL is shared - OK

    5. Migrate to Prepared State

    - I thought that this went ok and I'm pretty sure that all dc's were in consistent state, so I moved forward. probably shouldn't as it seems that everything was not yet replicated

    6. Migrate to Redirected State 

    I ran DFSRMIG /setglobalstate 2 and then the problems begun

    - our PDC somehow "dropped" itself and problems with Intranet, Exchange and Lync begun. I could't logon on all the servers and couldn't contact PDC server with aduc etc. so we rebooted the PDC server and after that everything went back to normal user wise.

    but now we are in state of sysvol replication not working correctly

    dfsrmig /getglobalstate :Current DFSR global state: 'Redirected'

    Succeeded.

    and

    Dfsrmig /getmigrationstate

    The following domain controllers have not reached Global state ('Redirected'):

    Domain Controller (Local Migration State) - DC Type
    ===================================================

    dc2 ('Start') - Writable DC
    dc3 ('Start') - Writable DC

    Migration has not yet reached a consistent state on all domain controllers.
    State information might be stale due to Active Directory Domain Services latency
    so no PDC server here at all?!?

    And

    Dcdiag /e /test:sysvolcheck /test:advertising

    I get these errors

    Doing primary tests

       Testing server: domain\dc2
          Starting test: Advertising
             Warning: DsGetDcName returned information for \\PDC
             when we were trying to reach DC2.
             SERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.
             ......................... dc2 failed test Advertising
          Starting test: SysVolCheck
             ......................... dc2 passed test SysVolCheck

       Testing server: domain\pdc
          Starting test: Advertising
             ......................... PDC passed test Advertising
          Starting test: SysVolCheck
             ......................... PDC passed test SysVolCheck

       Testing server: domain\dc3
          Starting test: Advertising
             Warning: DsGetDcName returned information for \\PDC,
             when we were trying to reach DC3
             SERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.
             ......................... DC3 failed test Advertising
          Starting test: SysVolCheck
             ......................... DC3 passed test SysVolCheck

    If I check with Net Share PDC is the only server showing these shares

    NETLOGON     C:\Windows\SYSVOL_DFSR\sysvol\domainl\SCRIPTS
                                                 Logon server share
    SYSVOL       C:\Windows\SYSVOL_DFSR\sysvol   Logon server share

    dc2 and dc3 are not showing them at all but the folders and data is there and synced

    C:\Windows\SYSVOL

    C:\Windows\SYSVOL_DFSR

    Repadmin /syncall /force /APed
    Syncing all NC's held on dc2
    Syncing partition: DC=ForestDnsZones,DC=finnexpo,DC=local
    CALLBACK MESSAGE: The following replication is in progress:

    and lot of stuff here... ending with

    CALLBACK MESSAGE: SyncAll Finished.
    SyncAll terminated with no errors.

    Active Directory Replication Status Tool is not showing any errors
    what should I try next to get. Can I try rolling back to Dfsrmig /setglobalstate 1?

    I need all the help you can give!

    BR

    J


    • Edited by JPartonen Friday, February 10, 2017 12:24 PM
    Friday, February 10, 2017 11:25 AM

All replies

  • checked this

    https://blogs.technet.microsoft.com/askds/2009/01/05/dfsr-sysvol-migration-faq-useful-trivia-that-may-save-your-follicles/

    DC2,DC3

    HKLMSystemCurrentControlSetServicesDFSRParametersSysvolsMigrating Sysvols
    Local State = 4
     [REG_DWORD]

    PDC

    HKLMSystemCurrentControlSetServicesDFSRParametersSysvolsMigrating Sysvols
    Local State =
    2 [REG_DWORD]

    Friday, February 10, 2017 11:54 AM
  • dcdiag gives me these errors

    PDC
        Starting test: DFSREvent
           There are warning or error events within the last 24 hours after the
           SYSVOL has been shared.  Failing SYSVOL replication problems may cause
           Group Policy problems.

    DC2
     Starting test: Advertising
        Warning: DsGetDcName returned information for \\PDC,
        when we were trying to reach DC2.
        SERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.
        ......................... DC2failed test Advertising

      Starting test: NetLogons
         Unable to connect to the NETLOGON share! (\\DC2\netlogon)
         [DC2] An net use or LsaPolicy operation failed with error 67,
         The network name cannot be found..

    DC3
     Starting test: Advertising
             Warning: DsGetDcName returned information for \\PDC, when we were trying to reach DC3.
             SERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.
             ......................... DC3 failed test Advertising

          Starting test: FrsEvent
             There are warning or error events within the last 24 hours after the SYSVOL has been shared.  Failing SYSVOL
             replication problems may cause Group Policy problems.
             ......................... DC3 passed test FrsEvent

     Starting test: NetLogons
             Unable to connect to the NETLOGON share! (\\DC3\netlogon)
             [DC3] An net use or LsaPolicy operation failed with error 67, The network name cannot be found..
             ......................... DC3failed test NetLogons
    Friday, February 10, 2017 1:37 PM
  • and here is the full info on 

    Repadmin /syncall /force /APed

    so there is something going on ?

    Syncing all NC's held on DC3.
    Syncing partition: DC=ForestDnsZones,DC=domain,DC=local
    CALLBACK MESSAGE: The following replication is in progress:
        From: CN=NTDS Settings,CN=DC3,CN=Servers,CN=domain,CN=Sites,CN=Configuration,DC=domain,DC=local
        To  : CN=NTDS Settings,CN=DC2,CN=Servers,CN=domain,CN=Sites,CN=Configuration,DC=domain,DC=local
    CALLBACK MESSAGE: The following replication is in progress:
        From: CN=NTDS Settings,CN=DC3,CN=Servers,CN=domain,CN=Sites,CN=Configuration,DC=domain,DC=local
        To  : CN=NTDS Settings,CN=PDC,CN=Servers,CN=domain,CN=Sites,CN=Configuration,DC=domain,DC=local
    CALLBACK MESSAGE: The following replication completed successfully:
        From: CN=NTDS Settings,CN=DC3,CN=Servers,CN=domain,CN=Sites,CN=Configuration,DC=domain,DC=local
        To  : CN=NTDS Settings,CN=DC2,CN=Servers,CN=domain,CN=Sites,CN=Configuration,DC=domain,DC=local
    CALLBACK MESSAGE: The following replication completed successfully:
        From: CN=NTDS Settings,CN=DC3,CN=Servers,CN=domain,CN=Sites,CN=Configuration,DC=domain,DC=local
        To  : CN=NTDS Settings,CN=PDC,CN=Servers,CN=domain,CN=Sites,CN=Configuration,DC=domain,DC=local
    CALLBACK MESSAGE: SyncAll Finished.
    SyncAll terminated with no errors.

    Syncing partition: DC=DomainDnsZones,DC=domain,DC=local
    CALLBACK MESSAGE: The following replication is in progress:
        From: CN=NTDS Settings,CN=DC3,CN=Servers,CN=domain,CN=Sites,CN=Configuration,DC=domain,DC=local
        To  : CN=NTDS Settings,CN=DC2,CN=Servers,CN=domain,CN=Sites,CN=Configuration,DC=domain,DC=local
    CALLBACK MESSAGE: The following replication is in progress:
        From: CN=NTDS Settings,CN=DC3,CN=Servers,CN=domain,CN=Sites,CN=Configuration,DC=domain,DC=local
        To  : CN=NTDS Settings,CN=PDC,CN=Servers,CN=domain,CN=Sites,CN=Configuration,DC=domain,DC=local
    CALLBACK MESSAGE: The following replication completed successfully:
        From: CN=NTDS Settings,CN=DC3,CN=Servers,CN=domain,CN=Sites,CN=Configuration,DC=domain,DC=local
        To  : CN=NTDS Settings,CN=PDC,CN=Servers,CN=domain,CN=Sites,CN=Configuration,DC=domain,DC=local
    CALLBACK MESSAGE: The following replication completed successfully:
        From: CN=NTDS Settings,CN=DC3,CN=Servers,CN=domain,CN=Sites,CN=Configuration,DC=domain,DC=local
        To  : CN=NTDS Settings,CN=DC2,CN=Servers,CN=domain,CN=Sites,CN=Configuration,DC=domain,DC=local
    CALLBACK MESSAGE: SyncAll Finished.
    SyncAll terminated with no errors.

    Syncing partition: CN=Schema,CN=Configuration,DC=domain,DC=local
    CALLBACK MESSAGE: The following replication is in progress:
        From: CN=NTDS Settings,CN=DC3,CN=Servers,CN=domain,CN=Sites,CN=Configuration,DC=domain,DC=local
        To  : CN=NTDS Settings,CN=DC2,CN=Servers,CN=domain,CN=Sites,CN=Configuration,DC=domain,DC=local
    CALLBACK MESSAGE: The following replication is in progress:
        From: CN=NTDS Settings,CN=DC3,CN=Servers,CN=domain,CN=Sites,CN=Configuration,DC=domain,DC=local
        To  : CN=NTDS Settings,CN=PDC,CN=Servers,CN=domain,CN=Sites,CN=Configuration,DC=domain,DC=local
    CALLBACK MESSAGE: The following replication completed successfully:
        From: CN=NTDS Settings,CN=DC3,CN=Servers,CN=domain,CN=Sites,CN=Configuration,DC=domain,DC=local
        To  : CN=NTDS Settings,CN=PDC,CN=Servers,CN=domain,CN=Sites,CN=Configuration,DC=domain,DC=local
    CALLBACK MESSAGE: The following replication completed successfully:
        From: CN=NTDS Settings,CN=DC3,CN=Servers,CN=domain,CN=Sites,CN=Configuration,DC=domain,DC=local
        To  : CN=NTDS Settings,CN=DC2,CN=Servers,CN=domain,CN=Sites,CN=Configuration,DC=domain,DC=local
    CALLBACK MESSAGE: SyncAll Finished.
    SyncAll terminated with no errors.

    Syncing partition: CN=Configuration,DC=domain,DC=local
    CALLBACK MESSAGE: The following replication is in progress:
        From: CN=NTDS Settings,CN=DC3,CN=Servers,CN=domain,CN=Sites,CN=Configuration,DC=domain,DC=local
        To  : CN=NTDS Settings,CN=PDC,CN=Servers,CN=domain,CN=Sites,CN=Configuration,DC=domain,DC=local
    CALLBACK MESSAGE: The following replication is in progress:
        From: CN=NTDS Settings,CN=DC3,CN=Servers,CN=domain,CN=Sites,CN=Configuration,DC=domain,DC=local
        To  : CN=NTDS Settings,CN=DC2,CN=Servers,CN=domain,CN=Sites,CN=Configuration,DC=domain,DC=local
    CALLBACK MESSAGE: The following replication completed successfully:
        From: CN=NTDS Settings,CN=DC3,CN=Servers,CN=domain,CN=Sites,CN=Configuration,DC=domain,DC=local
        To  : CN=NTDS Settings,CN=PDC,CN=Servers,CN=domain,CN=Sites,CN=Configuration,DC=domain,DC=local
    CALLBACK MESSAGE: The following replication completed successfully:
        From: CN=NTDS Settings,CN=DC3,CN=Servers,CN=domain,CN=Sites,CN=Configuration,DC=domain,DC=local
        To  : CN=NTDS Settings,CN=DC2,CN=Servers,CN=domain,CN=Sites,CN=Configuration,DC=domain,DC=local
    CALLBACK MESSAGE: SyncAll Finished.
    SyncAll terminated with no errors.

    Syncing partition: DC=domain,DC=local
    CALLBACK MESSAGE: The following replication is in progress:
        From: CN=NTDS Settings,CN=DC3,CN=Servers,CN=domain,CN=Sites,CN=Configuration,DC=domain,DC=local
        To  : CN=NTDS Settings,CN=DC2,CN=Servers,CN=domain,CN=Sites,CN=Configuration,DC=domain,DC=local
    CALLBACK MESSAGE: The following replication is in progress:
        From: CN=NTDS Settings,CN=DC3,CN=Servers,CN=domain,CN=Sites,CN=Configuration,DC=domain,DC=local
        To  : CN=NTDS Settings,CN=PDC,CN=Servers,CN=domain,CN=Sites,CN=Configuration,DC=domain,DC=local
    CALLBACK MESSAGE: The following replication completed successfully:
        From: CN=NTDS Settings,CN=DC3,CN=Servers,CN=domain,CN=Sites,CN=Configuration,DC=domain,DC=local
        To  : CN=NTDS Settings,CN=PDC,CN=Servers,CN=domain,CN=Sites,CN=Configuration,DC=domain,DC=local
    CALLBACK MESSAGE: The following replication completed successfully:
        From: CN=NTDS Settings,CN=DC3,CN=Servers,CN=domain,CN=Sites,CN=Configuration,DC=domain,DC=local
        To  : CN=NTDS Settings,CN=DC2,CN=Servers,CN=domain,CN=Sites,CN=Configuration,DC=domain,DC=local
    CALLBACK MESSAGE: SyncAll Finished.
    SyncAll terminated with no errors.

    Friday, February 10, 2017 1:41 PM
  • and I can also include FRSDIAG logs from all DC's if that is any help. seeing quite a few errors there also
    Friday, February 10, 2017 2:05 PM
  • Hi,
    If you have any related event logs found in the event viewer, please share them out.
    Based on my experience, maybe, something is wrong with the DFSR replication after you migrated from FRS, if that is the case, please follow the article to diagnose:
    http://windowsitpro.com/windows-server-2012/fixing-broken-sysvol-replication
    Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
    Or you might need to force an authoritative/non-authoritative synchronization for DFSR-replicated SYSVOL: https://support.microsoft.com/en-us/help/2218556/how-to-force-an-authoritative-and-non-authoritative-synchronization-for-dfsr-replicated-sysvol-like-d4-d2-for-frs
    Best regards,
    Wendy

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Monday, February 13, 2017 8:50 AM
    Moderator
  • these errors/warnings are from PDC's DFS Replication log. about this about from that moment when i drove command DFSRMIG /setglobalstate 1
    and then sam error when I drove DFSRMIG /setglobalstate 2
    ***
    Event 8028, DFSR
    DFSR Migration was unable to transition to the 'PREPARED' state for Domain Controller PDC. DFSR will retry the next time it polls the Active Directory. To force an immediate retry, execute the command 'dfsrdiag /pollad'. 
     
    Additional Information: 
    Domain Controller: PDC
    Error: 1816 (Not enough quota is available to process this command.)
    ***

    and after that several times
    ***
    Event 6804, DFSR
    The DFS Replication service has detected that no connections are configured for replication group Domain System Volume. No data is being replicated for this replication group. 
     
    Additional Information: 
    Replication Group ID: F2623AE8-C766-4FC2-B839-70496A1F081B 
    Member ID: 54FFA884-551D-449B-8434-DADA589C2A9D
    ***

    same event 8028 errors also in DC1 and DC2 Logs

    this is interesting
    Error: 1816 (Not enough quota is available to process this command.)
    what quota are we taling about and how to make it bigger?

    and there are also a lot of information entrys like this on DC1, DC2
    ***
    DFSR has started preparing the Domain Controller DC2 for migration. DFSR will now create the SYSVOL_DFSR folder, create objects in the local Active Directory and create DFSR member objects for the Domain Controller DC2. 
     
    Additional Information: 
    Domain Controller: DC2


    Monday, February 13, 2017 1:38 PM
  • Hi,
    >> Error: 1816 (Not enough quota is available to process this command.)
    Regarding this error, please check:
    “Close some applications and try again. If you still get this message, choose System from Control Panel, then choose Virtual Memory and increase the size of your paging file.”
    You could go to Control Panel, Sync Center, Offline Files, Manage Offline Files (left hand side), Disk Usage tab, Change Limits
    https://msdn.microsoft.com/en-us/library/ms820778.aspx
    Best regards,
    Wendy

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Thursday, February 16, 2017 8:59 AM
    Moderator
  • Hi,

    Just checking in to see if the information provided was helpful. And if the replies as above are helpful, we would appreciate you to mark them as answers, please let us know if you would like further assistance.

    Best Regards,

    Wendy


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Monday, February 20, 2017 10:04 AM
    Moderator