RE: Exchange 5.5 to 2003 co-exist question



I have made a Exchange 5.5 to 2003 Migration with 18000 users. I advice you
the folowing things :

1. Every User should have only one account, only this account is associate
to the Ex 5.5 Mailbox
2. Use ADMT with SID history for the migration.
3. Install ADC, after the ADMT you should get no additional accounts in AD
4. Move the Exchange 5.5 Mailboxes fast to 2003. If you decide to make a
long time migration you get a difference between the Ex.5.5 directory an the
AD by extended administration or replication problems


"KarlC" wrote:

> Hello.
>
>
> We've been performing testing and doing research on a migration
> procedure from Exchange 5.5 to 2003 and have some odd results.
>
>
> The current system is a straightforward single org, single site 5.5
> system with about servers and 2000 users.
>
>
> We will be performing an intra-org migration. The NT domain will not be
>
> upgraded, instead trusts will be set between the NT and 2003 domains.
>
>
> It's not going to be a big bang approach but instead a rolling
> migration over a couple of months.
>
>
> Documentation and postings point out not to enable ADC created place
> holders, no problem with that.
>
>
> We tested using freshly created from scratch (not migrated and not
> enabled placeholder) accounts both on 5.5 and AD. Ran ADC first.
>
>
> Delegate rights work apart from when a 5.5 user tries to send on behalf
>
> of the AD user.
>
>
> Shared mailboxes, users can access shared mailboxes as long as the
> users accessing AND the shared mailbox is on either 2003 or 5.5. We
> can't seem to get a 5.5 user to access a 2003 shared mailbox or
> vice-versa.
>
>
> There seems to be 2 migration options according to the documentation
> and postings.
>
>
> A). Initially run ADMT (with sidhistory) to populate AD, then ADC (no
> need for ADclean this way). Users will continue to log into their NT
> accounts and access their 5.5 mailboxes as per normal.
> Then when a batch of users are to be migrated, we move the mailboxes
> and then test the AD login. The trick here is keeping track of any new
> accounts that have been created since ADMT was run.
>
>
> B). First run ADC and let it populate the AD with the disabled
> placeholders (NOT to be enabled!). Users will continue to log into
> their NT accounts and access their 5.5 mailboxes as per normal.
> When it comes for the users to be migrated we would then run ADMT (with
>
> SIDhistory) for the batch of users, run ADclean to marry up the
> accounts. Then move mailbox from 5.5 to the ADMT enabled account and
> test the login. This is a nice way of doing things as if there are any
> remaining disabled placehoders, these will mark out un-used accounts
> that have not been migrated.
>
>
> My question is which is the correct way of doing things for 100%
> co-existence between the 5.5 and 2003 users. We prefer B but got the
> above issues.
>
>
> I've viewed http://support.microsoft.com/?­id=316047 but as we're not
> enableing the disabled accounts and have even tried with freshly
> created accouts I can't see what we're doing wrong or is this a
> limitation of the co-existance?
>
>
> Help!!!
>
>
.



Relevant Pages

  • Re: AD merge with exchange 2007 srv, can ADMT do it?
    ... > ADMT will do user and computer account migration. ... > "Exchange cross forest migration" and you will find some documentations. ... I usually do put together step by step docs such as this, to help folks in the newsgroups, but I haven't yet with this procedure because besides being scattered and the procedure having many facets, my notes are customer specific with domain names, user accounts, passwords, etc, that it will take me some time to go through to compile it into one doc, and I do apologize I am short on time to do anything with this at this point. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Win2k3 and E2k3 migration to SBS 2003
    ... Most users here have given up on ADMT ... and switched to Swing Migration. ... > Migration Wizard (MigWiz). ... >>>accounts and then using Exchange Migration Wizard ...
    (microsoft.public.windows.server.sbs)
  • Re: Win2k3 and E2k3 migration to SBS 2003
    ... Migration Wizard (MigWiz). ... property is populated on those ADMT migrated accounts. ... and tested process as a basis for this migration. ...
    (microsoft.public.windows.server.sbs)
  • Re: Inter-forest migration confusion
    ... Dom1/Org1 users and mailboxes are to be migrated to Dom2/Org2, ... My current plan is to use ADMT to migrate users & resources, ... Microsoft's ADMT v3 Migration Guide says to first migrate mailboxes ... running ExMerge? ...
    (microsoft.public.exchange.admin)
  • RE: Migration from 4.5 to 2003
    ... Depends on how far you are in the migration. ... accounts, they will belongs to the new domain. ... unjoin/rejoin the machines back to the domain, or use ADMT to move it back. ... backup, backup, backup. ...
    (microsoft.public.windows.server.sbs)