Question Locked

Freeing Exchange 2000 from a Domain Controller

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

First off, I'm not highly proficient in managing Exchange. I've been doing it for a few months, but know that I still have tons to learn.

I'm trying to replace a existing Windows 2000 DC with a new 2003 R2 DC. Everything seems to be working correctly through the new DC just fine except exchange. The only symptom is slow (5min+) mail exchange. This doesn't start till aprox 15min after I unplug the old DC. Exchange seems to be working still, just extremely slowly. All mail gets stuck in the Advanced Queue before it's sent or received.

I seem to have made all the correct changes I can find. The directory access tab on the exchange server in Exchange System Manager are all pointing to the correct Domain Controllers (no references to the old one I'm trying to put down).

I have, however, found a few references through registry searches (on the exchange box). There are several references to the old DC in places similar to this:

HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\Install\Software\Microsoft\WINDOWS NT\CURRENTVERSION\Windows Messaging Subsystem\Profiles\ExchangeAdmin EXCHANGE 0x######

But there are two others that seem more likely problem-causing:

HKLM\SOFTWARE\Microsoft\MSLicensing\Parameters\DomainLicenseServerMulti

HKLM\SOFTWARE\Micorsoft\ADs\Providers\LDAP\CN=Aggregate,CN=Schema,CN=Configuration,DC=DOMAIN\File (SchCache file)

Will editing these registry keys solve my problem? If so, how should I go about doing so? If not, any additional ideas on steps I may have missed or troubleshooting I can pursue?

Please help me kill this old server. Any and all help would be greatly appreciated.

Thanks,
Nick

6 replies

by oh smeg

Isn't available on the new unit. Hence after a short time of the old unit being disconnected the problems start.

So start with the obvious what was running on the old server? How was it demoted from DC and eventually removed and how was the new one promoted to DC?

You really need to provide a lot more information here and tell us what you have attempted so that people here don't suggest things already tried.

Col

by nsnoonan

I'm finally getting enough time to make this a priority again.

To get NewDC up and running, I built it, joined the domain, dcpromo, and transfered all the FSMO roles over to it from OldDC. I have yet to demote OldDC, mainly for fear of the exchange problem to happen again.

Everything else seems to be working correctly, just not exchange.

I'm currently trying to find differences, program/install-wise, from the two DC's. But for some reason, OldDC's add-remove programs applet will not open. I'm working on that right now. Really need to put her down :)

To try to get things working correctly on the exchange box side of things, I've manually changed the "directory access" tab in exchange system manager (properties of the server) too all point to NewDC instead of OldDC. That's the only thing, other than the registry entries in the OP, that I've found pointing to OldDC. I have yet to modify anything to do with those registry entries. I'd like to try a few more things before I result to that.

I'll continue working on getting the software information.

by cg it

you didn't mention DNS and Exchange does use DNS.

If the same DNS server is on the network, then it's not DNS, however if the old DC ran DNS and you made a new DNS server on the new DC, it's possible DNS isn't configured properly for your Exchange Server.

Would account for slow mail without the old DC and old DNS and fast mail once it's back on the network.

by nsnoonan

I had thought about this, since I had resolved this problem in the past. I did build a new DNS server into NewDC. The static IPs were set to the wrong DNS server and I had switched it to resolve the problem, temporarily. Then we had these additional issues a few days later, with basically the same symptoms.

However, I actually MAY have found the current problem, which is oddly enough also related to DNS.

We use GFI for mail filtering. It's installed on the same box as exchange. I found that GFI has a seperate DNS setting that was still pointed to OldDC.

When I get brave enough, and have enough time to monitor it closely, I'll turn off OldDC and see if there are any changes in Exchange performance.

by dumphrey

AD and Exchange are both very, very DNS dependent. We had a spma filter that we changed the dns server from our default isp dns to a faster dns server and almost doubled performance (no need for a local dns server since the exchange is the only host it needed).
But that was an appliance not a program on the exchange server. But the point is, DNS is the root of a network, healthy DNS == working network. I would be interested to hear if an nslookup of your domain controller (from the exchange server) was different prior to changing the GFI dns settings and after changing them...
I would also assume that replication between the old and new DC's has taken place fully? So that schema objects from Exchange are now in the 2003 schema?

This discussion is closed to new replies.