locked
Error when applying new changes RRS feed

  • Question

  • Hey guys,

    We have been running DirectAccess 2012 successfully for several years now. We have implemented a new domain controller in the environment and decommissioned our old domain controller. When we did that, DirectAccess stopped working. I noticed the old domain controller was listed in both Step 1 and Step 3 in DirectAccess. I changed both settings and hit Apply. Unfortunately, directly after the "Opening the client GPO's" step, it fails with "Element not found" (see screenshot below).

    Just in case it was a stray DNS issue, I changed the primary DNS on the NIC on the DirectAccess server to point at the new DC, I added the old DC's IP4 address as a secondary IP on the new DC's NIC, I created a CNAME in DNS for the old DC name to point at the new DC name and manually created an A record for the new DC name with the old DC's IPv4 (and PTR record). Everything should now be pointing at the new DC, no matter what. Still no joy.

    I suspect that when we setup DirectAccess, the old DC is hardwired in somewhere - but I cannot figure out where. Any help is appreciated.


    -Brad

    Monday, August 22, 2016 8:48 PM