asked on

dcdiag DFSR and other errors after migrating windows server 2008 R2 to windows server 2012 Active directory

Hi all,

After migrated Windows Server 2008 R2 to Windows server 2012 R2 AD, I demoted the Windows server 2008 R2 and change the server name and ip address to something else. From the new Windows Server 2012 R2 AD, I changed the new Windows Server 2012 R2 AD back to the old Windows server 2008 R2 server name and ip address. But when I ran dcdiag /v /q to check any error.. I got the DFSREvent and other errors from below. Can someone look at the DFSR and other errors and possible to fix it?

Regarding the DFSREvent... I found another post below of how to correct FRS\DFSR object. However, I was not able to do it and not sure if it is related to my error...

Also you need to follow steps in below article on 2012 DC post successful rename operation to correct FRS \ DFSR object references
http://technet.microsoft.com/library/cc794759(v=ws.10).aspx

C:\Windows\system32>dcdiag /v /q
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.
......................... SERVER1 failed test DFSREvent
An error event occurred. EventID: 0x0000272C
Time Generated: 02/26/2015 17:02:36
Event String:
DCOM was unable to communicate with the computer 192.168.0.1 using
any of the configured protocols; requested by PID a58 (C:\Windows\system32\
dcdiag.exe).
An error event occurred. EventID: 0x0000272C
Time Generated: 02/26/2015 17:02:37
Event String:
DCOM was unable to communicate with the computer 192.168.0.1 using
any of the configured protocols; requested by PID a58 (C:\Windows\system32\
dcdiag.exe).
An error event occurred. EventID: 0x0000272C
Time Generated: 02/26/2015 17:03:45
Event String:
DCOM was unable to communicate with the computer 192.168.0.1 using
any of the configured protocols; requested by PID 3bc (C:\Windows\system32\
dcdiag.exe).
An error event occurred. EventID: 0x0000272C
Time Generated: 02/26/2015 17:03:46
Event String:
DCOM was unable to communicate with the computer 192.168.0.1 using
any of the configured protocols; requested by PID 3bc (C:\Windows\system32\
dcdiag.exe).
An error event occurred. EventID: 0x0000272C
Time Generated: 02/26/2015 17:19:53
Event String:
DCOM was unable to communicate with the computer 192.168.0.1 using
any of the configured protocols; requested by PID bcc (C:\Windows\system32\
dcdiag.exe).
An error event occurred. EventID: 0x0000272C
Time Generated: 02/26/2015 17:19:55
Event String:
DCOM was unable to communicate with the computer 192.168.0.1 using
any of the configured protocols; requested by PID bcc (C:\Windows\system32\
dcdiag.exe).
......................... SERVER1 failed test SystemLog

ASKER CERTIFIED 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

m4power

ASKER

"Renaming DCs never ends well. You'll have to spend a lot of time in DNS, ADUC, ADSS, and NTDSUtilncleaning up orophaned entries. "

Thanks but if you can give me more insight what would be the issue by renaming DC. I just wanted to clarify that I renamed the server name not the Domain name from SERVER1.domain.com to SERVER2.domain.com of the DC by running "Netdom computername" command and it seems all complete successfully.

I ran the dcdiag command today all other errors are gone but except the DFSREvent is still here...

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.
......................... SERVER1 failed test DFSREvent

Thanks.

m4power

ASKER

Is there any command or utility I can double check the old server name is removed completely and not causing any issue? I manually checked DNS, ADUC and ADSS, all seems updated to the new server name successfully.

Cliff Galiher

Not really. Hence the reason renames never go well.

Seth Simmons

This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.