RE: [ActiveDir] Exchange 2003 Migration Question

[Nicolas Blank]

Title: Message

Suggest you do one org at a time and never more people than you can a) roll back at a time b) support by yourself/with helpdesk the next day ;) I’ve had a LOT of success with Quest’s migration tool, since you can do the domain migration and the exchange migration from the same tool, which is cool when you’re trying to track down which tool did what. It also rewrites the outlook profile remotely, which is a big plus when it comes to not driving to Hicksville to repoint profiles, even if you’re willing to remote admin them, it’s hard without a tool to catch every profile that’s logged onto a machine once, including people on maternity leave. Aelita also does a really exchange migration tool, but they’ve split their directory and email migration tool, as have so many others.   PST files are a real bane to absorb during migration, and although I’ve kept these attached during a migration, it’s a bit hard to re-address to profile once migrated to reflect a new mailbox as the delivery location, since this would transparently pump the pst help mail back into the new active mailbox.   Tools that address mail held in PST files, tend to be archive related – KVS, EAS, COMVAULT, etc, which major on getting the PST content into another online store. If you’re feeling brave, then have a dig around here [HKEY_USERS\S-1-5-21-YOUR-USER-SID-HERE\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles\Outlook\XXXXXGUID You’ll find some info on the delivery location, although you’ll have to lookup the XXXX GUID values at the end on MSDN or a friendly outlook developer. If you understand these keys, you CAN influence your mail delivery location, and of course you can break every outlook profile on every desktop J if you get it wrong.   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kent Maxwell Sent: 20 February 2004 06:25 PM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] Exchange 2003 Migration Question    Nicolas,   Thank you very much!  I found your email very informative!  We are going to be doing three migrations.  The first is 400+ mailboxes, one exchange server.  The second will be 100 mailboxes, to a different exchange server in a different site.  The third will be 300+ mailboxes to another exchange server in a different site.  I am particularly interested in the 3rd party tool you would recommend to connect the exchange organizations and if you know of any good tool to change the client outlook profiles.  I also have a problem that in one site they have many PST files and did not retain the email in their exchange mailbox and I need to not only get their new MAPI profile connected with the PST(s) but also migrate all the email in the PST back to Exchange.   Thank you!   Kent -----Original Message----- From: Nicolas Blank [mailto:[EMAIL PROTECTED] Sent: Friday, February 20, 2004 3:19 AM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] Exchange 2003 Migration Question Kent There's a number of factor you need to consider here, and three of the biggest one's that come to mind are co-existence, user profile re-pointing, and freezing the admin environment for the duration on one or both sides. You didn't mention how many mailboxes, servers or mail you had, so it's hard to advise on the purchase on a 3'rd party tool, native tool or manual options, although I would recommend you look at a number of the 3'rd party tools that are available, especially when you look at an extended co-existence period where you need solid dir-sync to maintain both set's of directories.   If you go the tool route, you should look at a solution which will build and maintain the target GAL, plus build objects, or in your case match on the objects which you already have which is matching the associated NT account on the 5.5 mailbox to the AD user's sidHistory attribute.   This can be done natively, but not as cleanly as I've done with third party.   In essence your migration path would be the following: Setup routing between the two org's - preferably X.400 connector, since this allows you to maintain your SMTP namespace in both orgs and still have a namespace to route against   Build a target GAL that would route mail back to the source org using x400 proxy's, but mace sure the GAL is built using mail enabled users that are stamped with the source org's DN as x500 addresses. This will absorb reply-ability between source and target org, including outstanding meeting request, etc   Batch MAILBOX ENABLE as many users as you wish to migrate at a time and transfer their mail. Since the target object's will be overwritten the x400 proxy route will be overwritten.   Set alternate recipients on the source mailboxes to route new mail to the target GAL.   The advantage of this method is that you have a co-existence model which will allow you to co-exist for a while, plus once your target GAL is built you can switch your MX record over at any time.   This is one method of migrating/coexisting, and while it's not detailed exhaustively, it gives you a route to start thinking on.   I strongly suggest you stay away from the ADC and use a third party tool to do this with, unless you have enough time to break your lab several times and rebuild it  ;)   Please respond with your migration parameters, such as mailbox count, server count and mail volume, as these will all influence your migration time considerably       Nic       From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kent Maxwell Sent: 19 February 2004 05:19 PM To: '[EMAIL PROTECTED]' Subject: [ActiveDir] Exchange 2003 Migration Question   I know this isn't quite an Active Directory question... I am working on finding a way to migrate private mailboxes and public folders stored in an Exchange 5.5 server to a Exchange 2003 server.  The Exchange Organization is different for both servers.  The user accounts that were associated with the mailboxes in the Exchange 5.5 have been migrated to the new ADS running on Windows 2003 with the SIDHistory intact.  Can any one give me suggestions on what has worked for you to migrate accounts in a situation similar to this?  I am looking for anything...even if it will cost me money. Thanks, Kent --- This e-mail is intended for the use of the addressee (s) only and may contain privileged, confidential, or proprietary information that is exempt from disclosure under law. If you have received this message in error, please inform us promptly by reply e-mail, then delete the e-mail and destroy any printed copy. Thank you. --- This e-mail is intended for the use of the addressee (s) only and may contain privileged, confidential, or proprietary information that is exempt from disclosure under law. If you have received this message in error, please inform us promptly by reply e-mail, then delete the e-mail and destroy any printed copy. Thank you.