none
Server 2003 upgrade to 2012 R2 SYSVOL and NETLOGON not shared!

    Question

  • I was tasked with replacing our 2003 R2 DCs with 2012 R2 DCs. The 2012 R2 servers must use the same name and IP address as the 2003 Servers.

    I successfully demoted and removed one of the 2003 DCs and made sure all metadata was cleaned up. This server does not hold any FSMO roles. To clean up the metadata I checked AD UC, AD SS and DNS. After confirming metadata was clean, I then configured and promoted the 2012 R2 Server with the computer name and IP of the decommissioned 2003 DC.

    The issue is that on the 2012 DC the Sysvol and Netlogon folders are not shared but are present on the DC. I left it overnight thinking it just needed time to replicate...

    Here is the Dcdiag on the 2003 DC:

    Starting test: FrsEvent

             * The File Replication Service Event log test
             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.
             A warning event occurred.  EventID: 0x800034C4

                Time Generated: 01/04/2017   21:12:32

                Event String:

                The File Replication Service is having trouble

                enabling replication from 2012 DC to 2003 DC

                for c:\windows\sysvol\domain using the DNS name

                2012 DC.local. FRS will keep retrying.

                 Following are some of the reasons you would see

                this warning.

                

                 [1] FRS can not correctly resolve the DNS name

                2012 DC.local from this computer.

                 [2] FRS is not running on 2012 DC.local.

                 [3] The topology information in the Active

                Directory Domain Services for this replica has

                not yet replicated to all the Domain Controllers.

               

                

                 This event log message will appear once per

                connection, After the problem is fixed you will

                see another event log message indicating that the

                connection has been established.

             A warning event occurred.  EventID: 0x800034C5

                Time Generated: 01/05/2017   08:28:39

                Event String:

                The File Replication Service has enabled

                replication from 2012 DC to 2003 DC for

                c:\windows\sysvol\domain after repeated retries.

             ......................... 2003 DC passed test FrsEvent

    Starting test: Services

             * Checking Service: EventSystem
             * Checking Service: RpcSs
                Invalid service type: RpcSs on 2003 DC, current value

                WIN32_OWN_PROCESS, expected value WIN32_SHARE_PROCESS

             * Checking Service: DnsCache
             * Checking Service: NtFrs
             * Checking Service: IsmServ
             * Checking Service: kdc
             * Checking Service: SamSs
             * Checking Service: LanmanServer
             * Checking Service: LanmanWorkstation
             * Checking Service: w32time
             * Checking Service: NETLOGON
             ......................... 2003 DC failed test Services

    --------------------------------------------------------------------------------------------------------------------------------

    Dcdiag on 2012 DC

      Starting test: FrsEvent

             * The File Replication Service Event log test
             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.
             A warning event occurred.  EventID: 0x800034FD

                Time Generated: 01/04/2017   15:48:24

                Event String:

                File Replication Service is initializing the system volume with data from another domain controller. Computer 2012 DC cannot become a domain controller until this process is complete. The system volume will then be shared as SYSVOL.

                

                To check for the SYSVOL share, at the command prompt, type:

                net share

                

                When File Replication Service completes the initialization process, the SYSVOL share will appear.

                

                The initialization of the system volume can take some time. The time is dependent on the amount of data in the system volume, the availability of other domain controllers, and the replication interval between domain controllers.

             A warning event occurred.  EventID: 0x800034FD

                Time Generated: 01/04/2017   17:55:36

                Event String:

                File Replication Service is initializing the system volume with data from another domain controller. Computer 2012 DC cannot become a domain controller until this process is complete. The system volume will then be shared as SYSVOL.

                

                To check for the SYSVOL share, at the command prompt, type:

                net share

                

                When File Replication Service completes the initialization process, the SYSVOL share will appear.

                

                The initialization of the system volume can take some time. The time is dependent on the amount of data in the system volume, the availability of other domain controllers, and the replication interval between domain controllers.

             A warning event occurred.  EventID: 0x800034C4

                Time Generated: 01/04/2017   20:13:38

                Event String:

                The File Replication Service is having trouble enabling replication from 2003 DC to 2012 DCfor c:\windows\sysvol\domain using the DNS name 2003 DC.local. FRS will keep retrying.

                 Following are some of the reasons you would see this warning.

                

                 [1] FRS can not correctly resolve the DNS name 2003 DC.local from this computer.

                 [2] FRS is not running on 2003 DC.local.

                 [3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers.

                

                 This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.

             A warning event occurred.  EventID: 0x800034FD

                Time Generated: 01/04/2017   20:35:29

                Event String:

                File Replication Service is initializing the system volume with data from another domain controller. Computer 2012 DC cannot become a domain controller until this process is complete. The system volume will then be shared as SYSVOL.

                

                To check for the SYSVOL share, at the command prompt, type:

                net share

                

                When File Replication Service completes the initialization process, the SYSVOL share will appear.

                

                The initialization of the system volume can take some time. The time is dependent on the amount of data in the system volume, the availability of other domain controllers, and the replication interval between domain controllers.

             A warning event occurred.  EventID: 0x800034FD

                Time Generated: 01/04/2017   21:23:02

                Event String:

                File Replication Service is initializing the system volume with data from another domain controller. Computer 2012 DC cannot become a domain controller until this process is complete. The system volume will then be shared as SYSVOL.

                

                To check for the SYSVOL share, at the command prompt, type:

                net share

                

                When File Replication Service completes the initialization process, the SYSVOL share will appear.

                

                The initialization of the system volume can take some time. The time is dependent on the amount of data in the system volume, the availability of other domain controllers, and the replication interval between domain controllers.

             ......................... 2012 R2 passed test FrsEvent

    This is my first big project any help would be appreciated!

    Thursday, January 5, 2017 2:17 PM

Answers

  • Well it looks like I should have waited longer. I can see the shares now after 12 hrs...
    • Marked as answer by Zeonxo Thursday, January 5, 2017 2:25 PM
    Thursday, January 5, 2017 2:25 PM

All replies

  • Well it looks like I should have waited longer. I can see the shares now after 12 hrs...
    • Marked as answer by Zeonxo Thursday, January 5, 2017 2:25 PM
    Thursday, January 5, 2017 2:25 PM
  • Hi,
    Thank you for the share, it will be greatly helpful to others who have the same question.
    Appreciate for your feedback.
    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

    Friday, January 6, 2017 6:49 AM
    Moderator