Transferring FSMO roles to additional domain controller in exchange environment

Transferring FSMO roles to additional domain controller in exchange environment (Full Version)

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

Message

kakarla -> Transferring FSMO roles to additional domain controller in exchange environment (12.Nov.2008 1:10:44 AM)
Dear Techies, I has an Active directory 2003 & Exchange server 2003 in our Environment, Recently we purchased new hardware for Active Directory so I installed win 2003 in new hard ware and promoted it as an additional domain controller, now I need to remove the old active directory machine so I am planning to transfer the roles to new active directory and demote the old active directory. I have an exchange 2003 in this environment if I transfer the roles to new Active directory what preliminary steps we have to take from exchange side, I tried it on test environment after transferring roles exchange is not working. Can anybody please explain the procedure how to transfer the roles and demote the primary domain controller in clustered exchange 2003 environment? Any Immediate help will be Highly Appreciated. Thanks in Advance…… Thanks & Regards Phani Kumar .B

ismail.mohammed -> RE: Transferring FSMO roles to additional domain controller in exchange environment (12.Nov.2008 2:28:13 AM)
hi mate, First you promote your new server as a DC and GC Transfer the FSMO role Shutdown 2 DC's and even exchange server Restart the new GC(new server where you have FSMO) then restart the exchange server and see the progress.. Probably you need to run Exbpa tool, after the restart of exchange server. you can download it from www.exbpa.com

Sembee -> RE: Transferring FSMO roles to additional domain controller in exchange environment (12.Nov.2008 11:14:12 AM)
Exchange doesn't care about the FSMO roles. The only thing it is worried about is GC. Therefore what i would do is add the new server/s as GCs. Wait 24 hours for that to replicate everywhere. Then take the GC role off your existing domain controllers and restart the Exchange services. Exchange should then start using the new domain controllers. Move the FSMO roles as required. Simon.

consultOz -> RE: Transferring FSMO roles to additional domain controller in exchange environment (16.Nov.2008 8:42:11 PM)
I am curious, what exactly is not working as it was said the FSMO roles pretty much has nothing to do with the functionality of exchange server, did you make the new DC a GC? (Global catalog server), DCPromo won't make windows 2003 DC a GC unlike windows 2008 server this is option at the beginning on windows 2008 DCPromo, you will have to go to site and services, find the DC, drill down to NTDS object, properties and make it GC and give some time for the DC become a GC. Did you verify the existing exchange server start using? new DC/GC (you need to verify this from ESM, DSAccess tab) http://www.msexchange.org/tutorials/Closer-Look-Directory-Service-Access-DSAccess-Part1.html Make sure property decommissioned your domain controller, move all the required services to the new DC, such as DNS, DHCP etc http://technet.microsoft.com/en-us/library/cc755937.aspx You most likely would not want put all the eggs into one basket, or if you do and if the basket falls down don't be so upset about all eggs broken and you have nothing left off. So install another domain controller for redundancy --oz

ratishnair -> RE: Transferring FSMO roles to additional domain controller in exchange environment (9.Dec.2008 8:25:34 AM)
I'd do this. 1. Dcpromo the new BOX and make it a DC. 2. Go to start-->Run--> dssites.msc and make the new DC a GC. 3. Go to cmd--> repadmin /syncall to replicate the changes. 4. Transfer all the FIZMO Roles. Refer: Using Ntdsutil.exe to transfer or seize FSMO roles to a domain controller: http://support.microsoft.com/kb/255504 Now comes Exchange: Think what all in exchange will be pointing to a DC. 1. Directory Access in properties of your server name in ESM. 2. Recipient Update Services 3. OAB What else ?? If you need to know that, dont just demote the server, rather shut it down and monitor for at least 1 week for any possible errors. Regard's Ratish Sekhar

Sembee -> RE: Transferring FSMO roles to additional domain controller in exchange environment (10.Dec.2008 7:44:44 PM)
If you like errors in your event logs then go ahead and shutdown a domain controller for a week. It isn't something I would do. An AD domain either expects the DC to be there or not. If it is not there then DCPROMO it out. Simon.

Page: [1]