Comments on: Exchange 2003, 2007 & 2010 Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC)

By: MUsh

MUsh — Wed, 16 May 2012 16:54:18 +0000

Hi David,
I’m on the same situation as you, hanging on reboot and services not starting. And in adittion, I cant connect trhu TS.
I have the default domain controller policy correctly.
The only thing that I did on the servers, was to remove a NLB Cluster…

By: David

David — Sat, 03 Mar 2012 19:22:26 +0000

Yep, this fixed my situation too. Thanks for posting as M$ leads you down a bunch of different paths to resolve this issue. I had the issue on a reboot “applying computer settings” hang. No matter what I tried, the server would not give me the login screen Your suggestions fixed the issue within seconds. Services started and the server gave the login screen. Hurray!

By: Mitch

Mitch — Sat, 01 Oct 2011 01:40:50 +0000

I found out the hard way that you have to add this to EVERY policy for it to ‘take affect’. Go figure – the best tool for testing is the policytest.exe which comes on the 2003 exchange disk (it should be in the support folder). I had trouble for 2 hours before finding this post. Thanks so much!

By: Juan Machado

Juan Machado — Wed, 31 Aug 2011 18:28:09 +0000

2 days trying to figure out what the problem was after promoting our domain from 2008 Functional level to 2008R2. Every 24 hours the Exchange services didn’t start with ” Topology” errors. Only thing to fix it was to run Exchange 2003 SP2 command ” update /DomainPrep ”

24 hours later, same problem. Exchange broken.

Exchange Domain Servers was missing from that group policy. Not sure if the promotion to 2008R2 deleted that, or if it was not necessary for Exchange 2003 SP2 to live in a Windows 2008 domain…

Thanks a lot for your blog.

By: Juan Machado

Juan Machado — Wed, 31 Aug 2011 15:31:01 +0000

Just wanted to add that the policy is located at:

Computer Configuration
Windows Settings
Security Settings
+Local Policies
User Rights Assignment
Mange auditing and security log

By: Peter Wilson

Peter Wilson — Sat, 18 Jun 2011 12:14:35 +0000

Thanks for the tip (Tim helped too)

By: Rich

Rich — Wed, 06 Apr 2011 10:52:42 +0000

Thanks for the info, I can never remember where the changes need to be made when I hit this problem.

By: joze

joze — Sun, 27 Mar 2011 21:19:51 +0000

The next time I read a weblog, I hope that it doesnt disappoint me as much as this one. I mean, I know it was my option to read, however I truly thought youd have something fascinating to say. All I hear is a bunch of whining about something that you could repair when you werent too busy looking for attention.

By: Tim

Tim — Tue, 26 Oct 2010 02:46:03 +0000

Make sure IP6 is enabled in the NIC.

By: bibomaria

bibomaria — Mon, 09 Aug 2010 07:03:48 +0000

Hi !

This is very nice article about topology issues in exchange server. Few days ago i have faced such types issues with my exchange server. these days i was very frustrated about this. i just go for a software that resolve my problems easily. i found a software over Google that works really good and it was very effectively at :: http://www.exchange-recovery.org