asked on

Migrating from FRS to DFS Replication after raising domain/forest levels to 2008 from 2003

Hi,
We have are having an issue with SYSVOL replication, we believe that it is related to a couple of things:

- domain/forest functional levels were set to 2003 even though there are NO 2003 servers/DC's in the environment
- using FRS versus DFS replication as it should be

I have raised the domain/forest functional levels from "Windows Server 2003" to "Windows Server 2008"

I am now looking at migrating from FRS to DFS Replication.

It should be mentioned that both DC's are running Server 2012 and Server 2012 R2 Standard editions

Thoughts on this as I have never attempted this before...

Mike

SOLUTION

Cliff Galiher

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Michael W

ASKER

I am seeing the following when running 'dcdiag', any thoughts on this or other things that I can check?

C:\Users\xxxxxxadmin.xxxxxx>dcdiag

Directory Server Diagnosis

Performing initial setup:
Trying to find home server...
Home Server = xxxxxx2
* Identified AD Forest.
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\xxxxxx2
Starting test: Connectivity
......................... xxxxxx2 passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\xxxxxx2
Starting test: Advertising
......................... xxxxxx2 passed 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.
......................... xxxxxx2 failed test FrsEvent

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

An error event occurred. EventID: 0x0000272C
Time Generated: 01/10/2018 15:45:13
Event String:
DCOM was unable to communicate with the computer x.x.x.x using
any of the configured protocols; requested by PID 2530 (C:\Windows\system32\dcdiag.exe).
An error event occurred. EventID: 0x0000272C
Time Generated: 01/10/2018 15:45:34
Event String:
DCOM was unable to communicate with the computer x.x.x.x using
any of the configured protocols; requested by PID 2530 (C:\Windows\system32\dcdiag.exe).
......................... xxxxxx2 failed test SystemLog

ASKER CERTIFIED SOLUTION

Pber