migrate exchnage server 2003
- Want to migrate exchange server 2003 to new hardware and server ...your assistance is required ..
2 scenerio 1st keep the name same or 2nd different name so how to update the clent side ..we have 700 users
Answers
- Hi,
In the second scenerio the only downtime would be during mailbox movement, user will not be able to access the mailbox. You can also move users in batches or in night.
Have you decided which scenerio you will be going for. Becuase if you are going for second scenerio, you will have to install new exchange server and move all mailboxes and then only you can think about following the links I have shared. You can use this one as it also has screenshots.
http://www.msexchange.org/tutorials/Removing-First-Exchange-2003-Server-Part2.html
As far as rollback is concerned, you will be testing the mailbox move with test mailboxes first then no issues, also you can move the mailbox back to the old server till the time it is live. After move mailbox is done, follow the steps mentioned in above link and there should not be any issue.
Also, if you are feeling uncomfortable with this activity and are good with backup/restore and want to use 1st scenerio, use the following link. Moreover, you can achieve what you want with this scenerio over the weekend. Rolling back in this scenerio also should not be a big issue. Am not confirmed of the exact rollback steps right now but by looking at the process I think you can bring back the old server if excercise fails by resetting the computer acocunt in AD and then rejoining the domain. See if you can simulate the current setup in lab (may be on virtual machines) and do the testing to get more comfort level.
Additional steps will be required it this server is also a DC as mentioned in this link.
http://technet.microsoft.com/en-us/library/aa997176(EXCHG.65).aspx
Choose what you feel is more comfortable and easy for you.
-V- Proposed As Answer byv-beta Tuesday, February 02, 2010 6:16 PM
- Marked As Answer byElvis Wei -MSFTMSFT, ModeratorFriday, February 05, 2010 8:58 AM
All Replies
- Hi,
In 2nd scenerio also, client side will be automatically updated if you are using MAPI (Exchange account not POP3 or IMAP).
First scenerio looks quite simple as described here.
http://technet.microsoft.com/en-us/library/aa997176(EXCHG.65).aspx
However, I would personally use Second scenerio as I am not a big fan of doing recovey unless it is absolutely required. The high-level steps would be.
1. Introduce new Exchange server in the environment. Configure it as per your requirements.
2. Move Mailboxes.
3. Move Public Folders inclusing system folders, OAB, Connector etc and decomission the old server, You can follow the following links.
http://support.microsoft.com/default.aspx/kb/822931
http://www.msexchange.org/tutorials/Removing-First-Exchange-2003-Server-Part1.html#
-V - Thanks v-beta
But still confusion how client automatically update ..? Hi
how version clients do you have? If you clients have Outlook version 2003 and higher and use Exchange accounts, after move client mailbox, in properties exchange mailbox automated changed name exchange server. Clients didn't see nothing.name automatically updated in 2nd scenerio also ..isn't that
- Yes, In Second scenerio also name will be automatically updated, if you are using MAPI (Exchange accounts) with Outlook.
User will have to just close and open outlook after move mailbox is completed. Also, it amy take 5-10 for the outlook to point to the new server. This is becuase of AD replication. Again depends upon your setup.
In a single site, small setup, it can be instant.
-V - i have single site and front end (edge) and backhand excange ..want to move backhand to new hardware..
- Don't worry....You are good!
Just to add, do testing also.
Before moving production mail boxes move test mailboxes to the new server, then move your's/IT mailbox, check all the functionality and then proceed.
Follow all the documentation carefully. All the best! - Thanks beta
you have provided two different documents .can you please tell me which one to follow or if both follow in which order? - We will take the downtime for this , if unfortunately activity will be unsucessfull how to revert back .?is this option wil be available
- Hi,
In the second scenerio the only downtime would be during mailbox movement, user will not be able to access the mailbox. You can also move users in batches or in night.
Have you decided which scenerio you will be going for. Becuase if you are going for second scenerio, you will have to install new exchange server and move all mailboxes and then only you can think about following the links I have shared. You can use this one as it also has screenshots.
http://www.msexchange.org/tutorials/Removing-First-Exchange-2003-Server-Part2.html
As far as rollback is concerned, you will be testing the mailbox move with test mailboxes first then no issues, also you can move the mailbox back to the old server till the time it is live. After move mailbox is done, follow the steps mentioned in above link and there should not be any issue.
Also, if you are feeling uncomfortable with this activity and are good with backup/restore and want to use 1st scenerio, use the following link. Moreover, you can achieve what you want with this scenerio over the weekend. Rolling back in this scenerio also should not be a big issue. Am not confirmed of the exact rollback steps right now but by looking at the process I think you can bring back the old server if excercise fails by resetting the computer acocunt in AD and then rejoining the domain. See if you can simulate the current setup in lab (may be on virtual machines) and do the testing to get more comfort level.
Additional steps will be required it this server is also a DC as mentioned in this link.
http://technet.microsoft.com/en-us/library/aa997176(EXCHG.65).aspx
Choose what you feel is more comfortable and easy for you.
-V- Proposed As Answer byv-beta Tuesday, February 02, 2010 6:16 PM
- Marked As Answer byElvis Wei -MSFTMSFT, ModeratorFriday, February 05, 2010 8:58 AM
Thanks V.i have tried second scenerio in VM as per specified but unfortunately it was failed ..the client couldn't automatically update the new server ,when open the outlook its prompt the credentiall of old server and cannot be verified because of old server unavailable..when try to another client manually update the new its worked fine..can you please tell me some idea..
thanks
- im also prefer the second scenerio to implement.
- If you hv configured the servers/env correctly, it should not be an issue. Like I said you can also wait for few minutes and then check, it should automatically redirect.
Make sure your AD/DNS is working fine. If you still face issue and after the move outlook is not redirecting,
Check that AD is updated, on the user account properties, Exchange general tab check the home server name,
Check by logging to owa.
also, which version of outlook you are using and also service pack. - we using outlook 2003..
- if AD/DNS is not working fine then it shouldn't be manually also ...what you think.
- if AD/DNS is not working fine then it shouldn't be UPDATED manually also ...what you think.
- i have check in AD the user account properties show new server name ...but still outlook point to old server name and goes to offline and when come oline require credentiall os old server..
I don't think of any specific reason,
can you check if it is happening in both cached mode & online mode
and also are you trying with a single mailbox or have you tried multiple mailboxes.
check on another machine also, it can be a issue with outlook or outlook profile or the machine where outlook is running.
-V- Proposed As Answer byv-beta Wednesday, February 03, 2010 7:43 PM
- i have created two clients..one of which automatically update and 2nd one is i manually update the 2nd one working fine
Beta
Above issue has been resolved in my test environment and worked properly ,when i follow these steps in my live environment ,public folder replication issue occur ,when i see the status if replication tab in detail shows
Local modified instead of IN SYNC
i m stuck here ,can any budy help me outHi,
for the automatic update of the Outlook client to work, the old Exchange server must still be online the first time the client connect after the move of its mailbox.
Check that your old Exchange Server is still reachable by the client.Regards
hi all
there is issue left which is Schedule free /busy folder could not migrate to new server ,in the replication tab shows local modified ...i had shutdown the old server but no sub folder of SF/B are shown in new server ,in the event viewer continuos error shows
Error updating public folder with free-busy information on virtual machine LNHEXCHBE. The error number is 0x8004010f.
help me out plz
