Discussion Locked

Active Directory Holding Exchange Re-installation problem.

0 helpful
19 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
One of the administrators in the company i work with restored an image of a windows 2000 domain controller holding all 5 fsmo roles. Another domain controller exist in my domain. Both domain controllers hold the global catalog. After 60 days (tombstone time) we started having issues with the domain. Replication is not working anymore although when i created an account somehow it replicated on the other domain controller. The domain controller which now holds a corrupt active directory also has exchange installed on it so i cannot demote it before moving exchange. I was not able to move the FSMO roles so i can only sieze them at this point after the exchange move. One of my concerns is that on the domain controller which does not hold exchange the exchange attributes in active directory do not exist. I am assuming that the exchange data is there since it holds a global catalog. How do i get these attributes in the second domain controller. (i think this is the first step i need to do before i move exchange). Once i learn how to move exchange i will sieze all roles and demote the domain controller. Then i will install a new windows server 2003 domain controller and move back the roles. Any expert help and comments on these complex tasks would be highly appreciated.

19 replies

by p.j.hutchison

To install the Exchange attributes, insert the Exchange CD on the Schema master DC.
Run Setup.exe /ForestPrep the Setup /DomainPrep.

If the attributes are already there, then the commands will not do very much otherwise it will add the missing attributes.

by geoffrey.grima

Thanks for your reply p.j. On my corrupted damain controller which is the schema master the attributes where installed by the previous admin. On the replica dc which i installed before when everything was working fine the attributes are not there. Should i run the cd on the 2 nd domain controller even if it is not the schema master yet? I also have a language problem. My exchange media is in German and this dc is in english. I assume i have to get the media in english first to be sure that i have everything comaptible. Another question is why didn't the ad schema replicate the exchange attributes aswell once the 2nd domain controller was installed? Any ideas?

by p.j.hutchison

Schema attributes only need to be installed once in any forest. If the old server is in a seperate forest, then do so, otherwise it should get replicated across from the Schema Master automatically.

by big ole jack

You will have to reboot another DC into AD Restore Mode and use NTDSUTIL to seize the role of the Schema Master and transfer it to another DC. Do a search on MS Knowledgebase on the exact commands, but the Schema Master must be fixed or else you will have all sorts of issues with adding objects or modifying attribute values. Also, Exchange won't install properly if it can't modify the schema with its own object classes and attributes, which get written to the DC holding the Schema Master role.

by geoffrey.grima

Thats what i have read. Do u have any idea why the attributes are not showing in my second domain controller (english version). When i open users & computers i dont have the tabs Exchange-Features, Exchange-General, Email address. On the DC server which holds the schema these three tabs show in the user properties in active directory. The DC on which the tabs are not showing computer is part of the same domain so i assume that these tabs should have been installed automatically when the schema master was conatacted in the installation. Am i correct?...Could it be that this problem is due to the fact that I have one domain controller in German and one in English. Thanks again.

by p.j.hutchison

Ah! Now, you need to install the Exchange MAnagement tools to get those extra tabs.
Insert the Exchange CD, and click Install Management tools only, select Custom install and select the tools from the component list.

by geoffrey.grima

Thanks alot. Will post the results as soon as i get hold of the media in english. Once that is complete i will try and do the exchange move onto another server. I hope u keep following this thread. I am sure I will learn alot from this complex exercise. Hope I manage in the end. Thanks again.

by geoffrey.grima

I cannot move the Schema master so my only option is to sieze it. Exchange is working perfectly at the moment. It is installed on the DC which has the corrupted AD (which also holds all 5 FSMO roles). My only concern about siezing the roles is that Exchange will not function properly anymore and i cant afford that at the moment. Do u think I will have issues if I sieze all five roles and move them to the other DC but not demote the DC. Will exchange still function?

by big ole jack

Normally, you would move the Schema Master FSMO role by using the Schema Management MMC console, but since you have a corrupt DC, the proper procedure is to pull the plug on it and seize the role on another DC with a clean copy of the AD database. It's not wise nor recommended to seize a FSMO role and still have the bad DC online. You will not have any issues moving all 5 FSMO roles to another box, but be certain that you permanently decommission the bad DC and remove it from the network. You can then blow it away, rebuild it as a member server, and then repromote it back to a DC once you join it back to your domain. After that, you can move the FSMO roles back once you confirm that the rebuilt DC is replicating correctly. Your Exchange install won't be affected because the Schema has already been extended and your AD database is already Exchange aware and knows about the classes and attributes, but it is critical to have the FSMO roles running on a DC with a clean bill of health.

by geoffrey.grima

Thats exactly my plan as regards to active directory. I read that it is not advicable to demote it from a DC if exchange is running on it. So i will sieze the roles and hope that it works (i have already done this procedure and was lucky in another network) have to make sure that exchange is installed on another computer so then i can demote the dc. I will then install the same machine with windows server 2003 and install exchange back on it (For this computer ideally i will use the same name but it will remain a member server holding only exchange) I guess i should not have any problems even if in the future it becomes a dc again...right? I will then install a new windows 2003 server as a domain controller only. And it should replicate fine with the current windows 2000 AD. This will be the first time i upgrade AD to 2003. Kindly let me know if there are things that i should be aware to prepare my AD 2000 for the 2003 upgrade. Thanks alot.

by big ole jack

Once you confirm that you don't have anything funky going on in terms of replication, set some time after business hours to update the domain(s) and forest to Windows 2003 version by running adprep /forestprep and adprep /domainprep from the files located in the i386 folder of the Windows 2003 Server CD. I suggest you install the Windows 2003 Resource kit tools and use Replmon to monitor your AD partitions and replication traffic. Afterwards, upgrade your Windows 2000 servers to Windows 2003 or replace them altogether with Windows 2003 servers (don't forget about the FSMO role holders). Once everything looks good, you can then decide whether you are ready to raise the domain/forest functional level to Windows 2003 native mode if you are no longer running Windows 2000 servers in your forest. Afterwards, you can start the Exchange install, which will have you run another forestprep and domainprep to extend the schema for Exchange classes and attributes. Afterwards, you can start creating your first Exchange server to host your information store and mailboxes. It's really quite simple to do (except if you are clustering it) and shouldn't be too difficult. Also, it's not advisable to install Exchange on a DC because of the added load Exchange put on the CPU and disk controller.

by geoffrey.grima

Something else seems to have come up. I talked with some local IT people and I was told that SBS server was built to be the sole server in a network. Thus replication of AD is unlikely to be functioning properly and they suggest I should just reinstall my network from scratch. Its the first time i hear this about SBS. Replication was functioning ok as far as i know and I have 8 other member servers in my domain. Wind 2003 serv and Windows 2000 serv. At this point I am unsure if to start from scratch or carry on with my plan to experiment with AD. I have two days to complete this task once i start and i will travel abroad to fix this problem so I have not many chances to experiment once i'm there. 99% i will just reinstall the domain from scratch.

by big ole jack

I assumed you were running the standard or enterprise edition of W2K3, not SBS. SBS is crap for what you're trying to do. Go at least with W2K3 R2 Standard Edition.

by geoffrey.grima

I never assumed that active directory on Windows 2000 SBS would be different than on Windows 2000 srv. Unfortunatly its something i just found out. I'm MCSE certified and I never in my studies I encountered that SBS is different. I will eliminate it from my network. The SBS was bought from the administrator before me. I will reinstall everything on Windows Server 2003 Standard R2. What i want to know from u now is this :)...Is there a way I can use the exchange and Sql on the SBS on a new Windows 2000 srv. I assume not ej?...By the way thanks alot for your interest in my thread. I appreciate it alot.

by p.j.hutchison

You can run Exchange 2003 and SQL 2000 SP4 or SQL 2005 on Windows 2003. You cannot run Exchange 2000 on Windows 2003.
SBS is different from other windows in that you cannot have multiple DCs, you are restricted to one DC.

by p.j.hutchison

You can run Exchange 2003 and SQL 2000 SP4 or SQL 2005 on Windows 2003. You cannot run Exchange 2000 on Windows 2003.
SBS is different from other windows in that you cannot have multiple DCs, you are restricted to one DC.

by geoffrey.grima

Thanks alot. With your help, I am now ready to start my network reinstallation. I am confident that the steps i will follow, are the most appropiate for upgrading and fixing my AD problem. In case I have any problems I will update this thread. Thanks again.

by big ole jack

A broken Exchange installation is just a monster in hiding. It aint pretty to administer if all you get are error messages and strange error codes.

This discussion is closed to new replies.