AD issue after VM restore

We are running a mixed 2008R2 / 2012R2 / 2016 network.

We have unfortunately experienced a massive hardware failure, losing in effect many servers.

We have 3 domain controllers:

ad03 - thankfully unaffected - server 2016
ad02 - crashed - restored from backup - server 2012R2
ad01 - crashed - restored from backup - server 2008R2

Unfortunately the restores have not been "AD aware" but "simple" VM restores from image backups. As such AD1 and AD2 are now out of sync.

FSMO / PDC roles were on ad01 and I have seized them on ad03 to insure minimal services. But we have to put back ad02 and ad01 into production.

I typically see this from DCDIAG (which is expected)


Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\admin>dcdiag

Directory Server Diagnosis

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

Doing initial required tests

   Testing server: Default-First-Site-Name\AD-AU-01
      Starting test: Connectivity
         ......................... AD-AU-01 passed test Connectivity

Doing primary tests

   Testing server: Default-First-Site-Name\AD-AU-01
      Starting test: Advertising
         Warning: DsGetDcName returned information for \\ad-au-03.do
         when we were trying to reach AD-AU-01.
         SERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.

Select allOpen in new window

What you be your advices to restore full functionality ?