Ask Question Forum:
C
O
M
P
U
T
E
R
2
8
- Underline
- Bold
- Italic
- Indent
- Step
- Bullet
- Quote
- Cut
- Copy
- Paste
- Table
- Spelling
- Find & Replace
- Undo
- Redo
- Link
- Attach
- Clear
- Code
Y-position of the mouse cursor
Attachment:===
Exchange 2003 Migration Challenge
ModifyI will try to lay this out properly so you see the challenge.
Company A was sold to Company B.
Company A has 3 seperate Exchange 2003 servers (MBX1, MBX2, and MBX3) each of which is in a seperate geographic location. These mail servers on a seperate NW and seperate AD/DNS structure (belongs to Company A) that I can not touch.
I am standing up 3 new Exchange 2003 servers (New-MBX1, New-MBX2, New-MBX3) in the same location as the existing servers. However, these servers will be on the new network and AD/DNS structure belonging to Company B.
In essence, I am replicating the exchange structure on a seperate NW. The big challenge is that at no time can our networks touch. At cutover time, the old NW and AD/DNS goes away and I will have access to these three old servers. At this point, I 'could' join them to my new nw & AD/DNS env but I'm not sure if that's the best choice for migrating the mailboxes from the old servers to the new.
Can we use exchange migration tools to export these mailboxes from the old servers (just prior to cutover while they are still on the old network) and then import them into the new mail servers?
What do you think would be the best approach to this?
The question is simple, the solution I suspect is difficult, I need to migrate all of the mailboxes from MBX1, MBX2, and MBX3 to New-MBX1, New-MBX2, New-MBX3.
Try This
http://support.microsoft.com/default.aspx?scid=kb;en-us;328871
http://www.msexchange.org/tutorials/Exchange-Migration-Wizard.html
If You cant make it with this then exmerge is your best choice
Using the ExMerge utility
When you use the ExMerge upgrade method, you must:
* Export all your users' mailbox data to .pst files by using the ExMerge utility, and then export Public Folder data to .pst files on a Microsoft Outlook (MAPI) client.
* Remove Exchange Server from the existing server (if you are using the same server).
* Install Exchange 2000 or Exchange 2003.
* Import your mailbox and public folder data from .pst files.
Some advantages of the ExMerge method include:
* It offers a different recovery method, if an in-place upgrade is unsuccessful.
* It offers a way to help secure data from a failing server and run a clean installation of Exchange 2000 or Exchange 2003.
Some disadvantages to the ExMerge method include:
* You have to create new mailboxes for all users before the import.
* You have to re-create all permissions on Public Folders.
* You cannot reply to old e-mail messages from users on this server.
* You have to reconfigure all connectors.
* You have to re-create distribution lists.
* You have to re-create Custom Recipients.
* You have to create new Exchange Client Profiles at each user desktop. If the server name does not change, new Client Profiles may not be required.
* Any users with Offline Storage files (.OSTs) have to export them to .pst files before they connect to the new server.
Try This
http://support.microsoft.com/default.aspx?scid=kb;en-us;328871
http://www.msexchange.org/tutorials/Exchange-Migration-Wizard.html
If You cant make it with this then exmerge is your best choice
Using the ExMerge utility
When you use the ExMerge upgrade method, you must:
* Export all your users' mailbox data to .pst files by using the ExMerge utility, and then export Public Folder data to .pst files on a Microsoft Outlook (MAPI) client.
* Remove Exchange Server from the existing server (if you are using the same server).
* Install Exchange 2000 or Exchange 2003.
* Import your mailbox and public folder data from .pst files.
Some advantages of the ExMerge method include:
* It offers a different recovery method, if an in-place upgrade is unsuccessful.
* It offers a way to help secure data from a failing server and run a clean installation of Exchange 2000 or Exchange 2003.
Some disadvantages to the ExMerge method include:
* You have to create new mailboxes for all users before the import.
* You have to re-create all permissions on Public Folders.
* You cannot reply to old e-mail messages from users on this server.
* You have to reconfigure all connectors.
* You have to re-create distribution lists.
* You have to re-create Custom Recipients.
* You have to create new Exchange Client Profiles at each user desktop. If the server name does not change, new Client Profiles may not be required.
* Any users with Offline Storage files (.OSTs) have to export them to .pst files before they connect to the new server.
Try This
http://support.microsoft.com/default.aspx?scid=kb;en-us;328871
http://www.msexchange.org/tutorials/Exchange-Migration-Wizard.html
If You cant make it with this then exmerge is your best choice
Using the ExMerge utility
When you use the ExMerge upgrade method, you must:
* Export all your users' mailbox data to .pst files by using the ExMerge utility, and then export Public Folder data to .pst files on a Microsoft Outlook (MAPI) client.
* Remove Exchange Server from the existing server (if you are using the same server).
* Install Exchange 2000 or Exchange 2003.
* Import your mailbox and public folder data from .pst files.
Some advantages of the ExMerge method include:
* It offers a different recovery method, if an in-place upgrade is unsuccessful.
* It offers a way to help secure data from a failing server and run a clean installation of Exchange 2000 or Exchange 2003.
Some disadvantages to the ExMerge method include:
* You have to create new mailboxes for all users before the import.
* You have to re-create all permissions on Public Folders.
* You cannot reply to old e-mail messages from users on this server.
* You have to reconfigure all connectors.
* You have to re-create distribution lists.
* You have to re-create Custom Recipients.
* You have to create new Exchange Client Profiles at each user desktop. If the server name does not change, new Client Profiles may not be required.
* Any users with Offline Storage files (.OSTs) have to export them to .pst files before they connect to the new server.
Try This
http://support.microsoft.com/default.aspx?scid=kb;en-us;328871
http://www.msexchange.org/tutorials/Exchange-Migration-Wizard.html
If You cant make it with this then exmerge is your best choice
Using the ExMerge utility
When you use the ExMerge upgrade method, you must:
* Export all your users' mailbox data to .pst files by using the ExMerge utility, and then export Public Folder data to .pst files on a Microsoft Outlook (MAPI) client.
* Remove Exchange Server from the existing server (if you are using the same server).
* Install Exchange 2000 or Exchange 2003.
* Import your mailbox and public folder data from .pst files.
Some advantages of the ExMerge method include:
* It offers a different recovery method, if an in-place upgrade is unsuccessful.
* It offers a way to help secure data from a failing server and run a clean installation of Exchange 2000 or Exchange 2003.
Some disadvantages to the ExMerge method include:
* You have to create new mailboxes for all users before the import.
* You have to re-create all permissions on Public Folders.
* You cannot reply to old e-mail messages from users on this server.
* You have to reconfigure all connectors.
* You have to re-create distribution lists.
* You have to re-create Custom Recipients.
* You have to create new Exchange Client Profiles at each user desktop. If the server name does not change, new Client Profiles may not be required.
* Any users with Offline Storage files (.OSTs) have to export them to .pst files before they connect to the new server.
Try This
http://support.microsoft.com/default.aspx?scid=kb;en-us;328871
http://www.msexchange.org/tutorials/Exchange-Migration-Wizard.html
If You cant make it with this then exmerge is your best choice
Using the ExMerge utility
When you use the ExMerge upgrade method, you must:
* Export all your users' mailbox data to .pst files by using the ExMerge utility, and then export Public Folder data to .pst files on a Microsoft Outlook (MAPI) client.
* Remove Exchange Server from the existing server (if you are using the same server).
* Install Exchange 2000 or Exchange 2003.
* Import your mailbox and public folder data from .pst files.
Some advantages of the ExMerge method include:
* It offers a different recovery method, if an in-place upgrade is unsuccessful.
* It offers a way to help secure data from a failing server and run a clean installation of Exchange 2000 or Exchange 2003.
Some disadvantages to the ExMerge method include:
* You have to create new mailboxes for all users before the import.
* You have to re-create all permissions on Public Folders.
* You cannot reply to old e-mail messages from users on this server.
* You have to reconfigure all connectors.
* You have to re-create distribution lists.
* You have to re-create Custom Recipients.
* You have to create new Exchange Client Profiles at each user desktop. If the server name does not change, new Client Profiles may not be required.
* Any users with Offline Storage files (.OSTs) have to export them to .pst files before they connect to the new server.
Try This
http://support.microsoft.com/default.aspx?scid=kb;en-us;328871
http://www.msexchange.org/tutorials/Exchange-Migration-Wizard.html
If You cant make it with this then exmerge is your best choice
Using the ExMerge utility
When you use the ExMerge upgrade method, you must:
* Export all your users' mailbox data to .pst files by using the ExMerge utility, and then export Public Folder data to .pst files on a Microsoft Outlook (MAPI) client.
* Remove Exchange Server from the existing server (if you are using the same server).
* Install Exchange 2000 or Exchange 2003.
* Import your mailbox and public folder data from .pst files.
Some advantages of the ExMerge method include:
* It offers a different recovery method, if an in-place upgrade is unsuccessful.
* It offers a way to help secure data from a failing server and run a clean installation of Exchange 2000 or Exchange 2003.
Some disadvantages to the ExMerge method include:
* You have to create new mailboxes for all users before the import.
* You have to re-create all permissions on Public Folders.
* You cannot reply to old e-mail messages from users on this server.
* You have to reconfigure all connectors.
* You have to re-create distribution lists.
* You have to re-create Custom Recipients.
* You have to create new Exchange Client Profiles at each user desktop. If the server name does not change, new Client Profiles may not be required.
* Any users with Offline Storage files (.OSTs) have to export them to .pst files before they connect to the new server.
Try This
http://support.microsoft.com/default.aspx?scid=kb;en-us;328871
http://www.msexchange.org/tutorials/Exchange-Migration-Wizard.html
If You cant make it with this then exmerge is your best choice
Using the ExMerge utility
When you use the ExMerge upgrade method, you must:
* Export all your users' mailbox data to .pst files by using the ExMerge utility, and then export Public Folder data to .pst files on a Microsoft Outlook (MAPI) client.
* Remove Exchange Server from the existing server (if you are using the same server).
* Install Exchange 2000 or Exchange 2003.
* Import your mailbox and public folder data from .pst files.
Some advantages of the ExMerge method include:
* It offers a different recovery method, if an in-place upgrade is unsuccessful.
* It offers a way to help secure data from a failing server and run a clean installation of Exchange 2000 or Exchange 2003.
Some disadvantages to the ExMerge method include:
* You have to create new mailboxes for all users before the import.
* You have to re-create all permissions on Public Folders.
* You cannot reply to old e-mail messages from users on this server.
* You have to reconfigure all connectors.
* You have to re-create distribution lists.
* You have to re-create Custom Recipients.
* You have to create new Exchange Client Profiles at each user desktop. If the server name does not change, new Client Profiles may not be required.
* Any users with Offline Storage files (.OSTs) have to export them to .pst files before they connect to the new server.
Try This
http://support.microsoft.com/default.aspx?scid=kb;en-us;328871
http://www.msexchange.org/tutorials/Exchange-Migration-Wizard.html
If You cant make it with this then exmerge is your best choice
Using the ExMerge utility
When you use the ExMerge upgrade method, you must:
* Export all your users' mailbox data to .pst files by using the ExMerge utility, and then export Public Folder data to .pst files on a Microsoft Outlook (MAPI) client.
* Remove Exchange Server from the existing server (if you are using the same server).
* Install Exchange 2000 or Exchange 2003.
* Import your mailbox and public folder data from .pst files.
Some advantages of the ExMerge method include:
* It offers a different recovery method, if an in-place upgrade is unsuccessful.
* It offers a way to help secure data from a failing server and run a clean installation of Exchange 2000 or Exchange 2003.
Some disadvantages to the ExMerge method include:
* You have to create new mailboxes for all users before the import.
* You have to re-create all permissions on Public Folders.
* You cannot reply to old e-mail messages from users on this server.
* You have to reconfigure all connectors.
* You have to re-create distribution lists.
* You have to re-create Custom Recipients.
* You have to create new Exchange Client Profiles at each user desktop. If the server name does not change, new Client Profiles may not be required.
* Any users with Offline Storage files (.OSTs) have to export them to .pst files before they connect to the new server.
Try This
http://support.microsoft.com/default.aspx?scid=kb;en-us;328871
http://www.msexchange.org/tutorials/Exchange-Migration-Wizard.html
If You cant make it with this then exmerge is your best choice
Using the ExMerge utility
When you use the ExMerge upgrade method, you must:
* Export all your users' mailbox data to .pst files by using the ExMerge utility, and then export Public Folder data to .pst files on a Microsoft Outlook (MAPI) client.
* Remove Exchange Server from the existing server (if you are using the same server).
* Install Exchange 2000 or Exchange 2003.
* Import your mailbox and public folder data from .pst files.
Some advantages of the ExMerge method include:
* It offers a different recovery method, if an in-place upgrade is unsuccessful.
* It offers a way to help secure data from a failing server and run a clean installation of Exchange 2000 or Exchange 2003.
Some disadvantages to the ExMerge method include:
* You have to create new mailboxes for all users before the import.
* You have to re-create all permissions on Public Folders.
* You cannot reply to old e-mail messages from users on this server.
* You have to reconfigure all connectors.
* You have to re-create distribution lists.
* You have to re-create Custom Recipients.
* You have to create new Exchange Client Profiles at each user desktop. If the server name does not change, new Client Profiles may not be required.
* Any users with Offline Storage files (.OSTs) have to export them to .pst files before they connect to the new server.
Try This
http://support.microsoft.com/default.aspx?scid=kb;en-us;328871
http://www.msexchange.org/tutorials/Exchange-Migration-Wizard.html
If You cant make it with this then exmerge is your best choice
Using the ExMerge utility
When you use the ExMerge upgrade method, you must:
* Export all your users' mailbox data to .pst files by using the ExMerge utility, and then export Public Folder data to .pst files on a Microsoft Outlook (MAPI) client.
* Remove Exchange Server from the existing server (if you are using the same server).
* Install Exchange 2000 or Exchange 2003.
* Import your mailbox and public folder data from .pst files.
Some advantages of the ExMerge method include:
* It offers a different recovery method, if an in-place upgrade is unsuccessful.
* It offers a way to help secure data from a failing server and run a clean installation of Exchange 2000 or Exchange 2003.
Some disadvantages to the ExMerge method include:
* You have to create new mailboxes for all users before the import.
* You have to re-create all permissions on Public Folders.
* You cannot reply to old e-mail messages from users on this server.
* You have to reconfigure all connectors.
* You have to re-create distribution lists.
* You have to re-create Custom Recipients.
* You have to create new Exchange Client Profiles at each user desktop. If the server name does not change, new Client Profiles may not be required.
* Any users with Offline Storage files (.OSTs) have to export them to .pst files before they connect to the new server.
