Forum Discussion
reinstall server2016 - what happens to client machine profiles
i have server2016 running for years i cloned my HD to an SSD 2-3 years ago my SSD got very corrupted, running, but not allowing any windows updates for the past 2 years i tried a lot of things to ...
The steps I provided assumes a healthy functional domain source. You can check this with dcdiag, repadmin tools so I don't think the cloning should need to be a part of this process.
dcdiag - this was the only failure
Starting test: SystemLog
An error event occurred. EventID: 0x0000272C
Time Generated: 12/10/2023 09:56:02
Event String: DCOM was unable to communicate with the computer 192.168.13.1 using any of the configured protocols; requested by PID a9c (C:\Windows\system32\dcdiag.exe).
An error event occurred. EventID: 0x0000272C
Time Generated: 12/10/2023 10:01:20
Event String: DCOM was unable to communicate with the computer 192.168.13.187 using any of the configured protocols; requested by PID 3df4 (C:\Windows\system32\dcdiag.exe).
An error event occurred. EventID: 0x0000272C
Time Generated: 12/10/2023 10:01:41
Event String: DCOM was unable to communicate with the computer 1.1.1.1 using any of the configured protocols; requested by PID 3df4 (C:\Windows\system32\dcdiag.exe).
An error event occurred. EventID: 0x0000272C
Time Generated: 12/10/2023 10:01:42
Event String: DCOM was unable to communicate with the computer 192.168.13.1 using any of the configured protocols; requested by PID 3df4 (C:\Windows\system32\dcdiag.exe).
An error event occurred. EventID: 0x0000272C
Time Generated: 12/10/2023 10:03:01
Event String: DCOM was unable to communicate with the computer 1.1.1.1 using any of the configured protocols; requested by PID 3768 (C:\Windows\system32\dcdiag.exe).
An error event occurred. EventID: 0x0000272C
Time Generated: 12/10/2023 10:03:34
Event String: DCOM was unable to communicate with the computer 8.8.8.8 using any of the configured protocols; requested by PID 3768 (C:\Windows\system32\dcdiag.exe).
An error event occurred. EventID: 0x0000272C
Time Generated: 12/10/2023 10:03:47
Event String: DCOM was unable to communicate with the computer 192.168.13.1 using any of the configured protocols; requested by PID 3768 (C:\Windows\system32\dcdiag.exe).
......................... SERVER2016 failed test SystemLog
Starting test: SystemLog
An error event occurred. EventID: 0x0000272C
Time Generated: 12/10/2023 09:56:02
Event String: DCOM was unable to communicate with the computer 192.168.13.1 using any of the configured protocols; requested by PID a9c (C:\Windows\system32\dcdiag.exe).
An error event occurred. EventID: 0x0000272C
Time Generated: 12/10/2023 10:01:20
Event String: DCOM was unable to communicate with the computer 192.168.13.187 using any of the configured protocols; requested by PID 3df4 (C:\Windows\system32\dcdiag.exe).
An error event occurred. EventID: 0x0000272C
Time Generated: 12/10/2023 10:01:41
Event String: DCOM was unable to communicate with the computer 1.1.1.1 using any of the configured protocols; requested by PID 3df4 (C:\Windows\system32\dcdiag.exe).
An error event occurred. EventID: 0x0000272C
Time Generated: 12/10/2023 10:01:42
Event String: DCOM was unable to communicate with the computer 192.168.13.1 using any of the configured protocols; requested by PID 3df4 (C:\Windows\system32\dcdiag.exe).
An error event occurred. EventID: 0x0000272C
Time Generated: 12/10/2023 10:03:01
Event String: DCOM was unable to communicate with the computer 1.1.1.1 using any of the configured protocols; requested by PID 3768 (C:\Windows\system32\dcdiag.exe).
An error event occurred. EventID: 0x0000272C
Time Generated: 12/10/2023 10:03:34
Event String: DCOM was unable to communicate with the computer 8.8.8.8 using any of the configured protocols; requested by PID 3768 (C:\Windows\system32\dcdiag.exe).
An error event occurred. EventID: 0x0000272C
Time Generated: 12/10/2023 10:03:47
Event String: DCOM was unable to communicate with the computer 192.168.13.1 using any of the configured protocols; requested by PID 3768 (C:\Windows\system32\dcdiag.exe).
......................... SERVER2016 failed test SystemLog
Please close this one by marking best response then open a new thread to discuss the domain health issue.