Exchange 2003 on domain controller

Exchange 2003 on domain controller (Full Version)

All Forums >> [Microsoft Exchange 2003] >> General

Message

rjsetford -> Exchange 2003 on domain controller (17.Oct.2007 4:43:48 AM)
hello, Looking at a client who is running Exchange 2003 on Windows Server 2003. The server is also a domain controller. [:@] Is it okay/safe to run dcpromo and demote the Exchange 2003 box to a member server therefore just leaving Exchange 2003 running? Are there any steps I should follow before hand? Thanks Richard

ismail.mohammed -> RE: Exchange 2003 on domain controller (17.Oct.2007 5:22:37 AM)
hi, When you are demoting the DC... you need to see that FSMO and GC role should exist on other server. Take the backup of the database First you take the GC role from the server during off peak hours and if possible reboot it. Then you can demote dc

megs -> RE: Exchange 2003 on domain controller (17.Oct.2007 8:27:37 AM)
As ismail stated, this shouldn't be an issue. However, before removing the GC role from your DC/Exchange server make sure you have another GC in the domain or you're fubar'd. Also, check to make sure that you are still discovering the domain controllers and GCs for the directory access and don't have them hard coded, otherwise it won't look for the new domain controllers. This section is found in the Directory Access tab of the properties of the Exchagne server in ESM. Prior to doing anything make sure you do a full backup of the database as well as AD. Better safe than sorry.

consultOz -> RE: Exchange 2003 on domain controller (17.Oct.2007 11:58:04 PM)
Do NOT change the DC status on the server , if you do you will have issues. While installing Exchange Server 2003 on a domain controller is a supported operation, it is not a best practice or a generally recommended practice. As well, once Exchange Server 2003 is installed, it is not supported to change the domain controller status of the server. That is, if the server is already a domain controller, that's fine. Do not change the server to a member server. The opposite is also true - if you install Exchange Server 2003 on a member server, do not then dcpromo the server up to a domain controller. If you do either of these, you will lose functionality in Exchange. Furthermore, this change is not supported by Microsoft (see KB 822179). For an example of one specific thing that stops working - if you demote a DC with Exchange Server install to a member server, the DS2MB service (which copies Active Directory data from A/D to the IIS metabase) stops working throughout an Exchange organization (see KB 822575). There are others. http://blogs.brnets.com/michael/archive/2005/01/24/319.aspx best oz

choppol -> RE: Exchange 2003 on domain controller (18.Oct.2007 12:27:05 AM)
I agree with Oz, It's never wise to install exchange on a DC. Imagine a DR situation. Rebuild O/S, restore System State and then Reinstall exchange. that's not counting mailboxes/public folders restore and reconnect. When I started at my current company it was that setup. I made it known it will be a nightmare and will not guarrantee how long it will take to fix the problem.

ismail.mohammed -> RE: Exchange 2003 on domain controller (18.Oct.2007 3:11:31 AM)
Yeah even i agree with consultOz view. It is never recommended to do promote or demote.

consultOz -> RE: Exchange 2003 on domain controller (18.Oct.2007 6:16:09 AM)
I recommend performing a little more research before recommending solutions to others if not sure about the answers. This will prevent one of us getting in trouble. It is also noticable most of you have great energy and eager to help others which is noticable, and I personally support it more than anyone out here in our community, and giving extra credits to those, Ismail is one of them In small environment, exchange admin should be able to survive with DC/DNS/Exchange, it is fine. If there is extra budged, build another exchange and move mailboxes over (exchange 2007 would be great). If there is multiple domain controllers and we don’t want this DC/Exchange to provide authentication services, than lift the SRV record, by this way DC/Exchange will be used by exchange if it is GC as well. The same policy can be achieved by local policy http://smtp25.blogspot.com/2007/09/enterprise-exchange-dedicated-gc-design_28.html Best regards Oz

Page: [1]