AD issues with 2008 & 2003 and 2012 Server running Exchange 2013

Have a network with a 2003 DC that the roles were moved to a 2008 Server... and the 2003 was never removed (and apparently something never synced completely) .. have 2012 Server running Exchange 2013.

The client got a version of crypt that infected 3 PCs and some files on the Windows 2003 server.

Had to restore the 2003 and 2008 server (or at least thought so) since there was a syncing issue of DC stuff between the 2.

Now the Exchange Server can't find the DC, get errors when attempting DC stuff on the 2008 server.

Not sure which way to go... thinking forcing all the roles to the 2008 server and forcing a removal of the 2003 server, and hoping we can get the Exchange server to like it.

Or worst case, we'll be exporting all the Exchange emails and starting the whole mess from scratch.

any tips ?
ASSIST-INCAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

timgreen7077Exchange EngineerCommented:
You can force exchange to use a static domain controller while you try to resolve your issue. See the below link to assist you with this:

https://blogs.technet.microsoft.com/shekhar37k/2014/06/11/hard-coding-multiple-domain-controllers-in-exchange-20102013/
Aaron GuilmetteTechnology Solutions ProfessionalCommented:
Typically, AD (and, by extension, Exchange) problems are caused by name resolution issues.

In your case, I'd recommend picking a DC that you think is good.  I'd probably select the 2008, since it's also not EOL.

Transfer all the FSMO roles to it, and ensure that DNS is working correctly on it (ie, you can ping servers by NetBIOS name and FQDN, resolve names on the internet, etc).

Commands that you will probably find useful:

DCDIAG /V
NETDIAG /V
REPADMIN /REPLSUMMARY

  1. Set all of your servers manually to point to the server with the PDCE role (and all other roles) as their primary DNS server.
  2. Run Ipconfig /registerdns on all servers.
  3. Launch DNS management console and clear DNS cache.
  4. If you are running WINS, clear the entries and force WINS replication.
  5. Restart your Exchange server.

Exchange only picks up new servers on a reboot (or if you set static DCs).  Things are designed to work dynamically (especially in smaller environments), so I would recommend we figure out why things aren't working as designed.

You may want to give your DCs a restart as well to ensure that they have re-registered.  NETLOGON typically registers at boot, so sometimes it may be beneficial to restart your DCs as well.
MaheshArchitectCommented:
If you could move FSMO to 2008 dc
Point everything to 2008 dcs including dhcp, other servers
Then shutdown 2003 for while
Restart exchange and see how it goes
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

timgreen7077Exchange EngineerCommented:
@ASSIST-INC before this ticket is closed can you confirm if any of the solutions or recommendation helped you resolve your issue?
ASSIST-INCAuthor Commented:
Sorry, I submitted this on behalf of the tech on the case, I figured they'd update it.

Ended up being some time sync issue between the 2 DCs


Doug Rhea

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
timgreen7077Exchange EngineerCommented:
Oh ok thanks. please complete the ticket by accepting your own solution.
ASSIST-INCAuthor Commented:
Thanks to those that took the time to submit tips, I am sure they would have come in handy if that had been the problem.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.