Re: Exchange 5.5



What we did is we migrated the users from nt4 domain to he new domain. We
joined the new domain with the 2k and 5.5 server corrected some security
stuff cause the builtin accounts aren't migrated and all seemed ok. Today I
noticed that when a user logs into their mail box I get a 1016 error in the
even log that states that someone has logged onto a mail box that isn't the
primary user. It sounds like this may be a problem when I try to move the
mailboxes from 5.5 to 2003 exchange.what do you think

"Al Mulnick" wrote:

> Well, if it's a new domain, then it doesn't sound like you plan to move the
> 2K server over to the new domain? Is that correct? If so, then leave it as
> is. You can install the Exchange 2003 server in the new domain/forest and
> migrate the users over.
>
> What you're talking about is covered as a migration vs. an upgrade which may
> be why it's harder to find in the docs. That's because the ORG boundaries in
> 5.5 equate to the forest boundaries in 2003. If you install new vs
> upgrading, then you have no upgrade path. It's strictly a migration.
>
> If you want to have the organizations connected in terms of address book etc
> and want to upgrade Exchange but migrate the Windows accounts, then you can
> do that as well as long as you have a trust between the domains. In that
> case, you would want to migrate the Windows accounts before doing anything
> with Exchange for simplicity. Then use the ADC and join the new forest with
> the old 5.5 ORG and move the mailboxes over. This is a little trickier but
> works just fine.
>
> I think this is what you're asking, but correct me if I'm wrong. I'll try to
> be helpful.
>
> Al
>
>
>
> "VERY CONCERNED" <VERYCONCERNED@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:2864BE09-F73B-4B1D-AC42-1499E32E602A@xxxxxxxxxxxxxxxx
> >I appreciate the link I have been there before I came here and all my
> >serches
> > produce articles that think I am upgrading 5.5 to 2003 and I will but not
> > untill I have played with sp2 for exchange to get familiure with the
> > mobile
> > piece. I have done some more reading and I'm just not sure what is
> > required
> > to put my 5.5 exhcange runing on wk2 onto 2003 AD. after I have done my
> > research I plan on reinstalling exhchange 203 enterprise into the exchange
> > sommunity and moving the mailboxes but that is in the future.
> >
> > "Al Mulnick" wrote:
> >
> >> http://www.microsoft.com/exchange/library has some very good upgrade
> >> documents. Not sure what your boundaries are for upgrade, but you should
> >> be
> >> able to find some helpful information at that link.
> >> Does that help?
> >>
> >>
> >> "VERY CONCERNED" <VERYCONCERNED@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
> >> message
> >> news:F1B396DB-4B45-4538-B7A1-01703026BD2C@xxxxxxxxxxxxxxxx
> >> >I have 1 5.5 exchange mail server with sp4 running on a win2k server. It
> >> >is
> >> >a
> >> > member server in a nt 4.0 domain. We are moving to a 2003 active
> >> > directory
> >> > with a new domain and I need to have this exchange server in the domain
> >> > as
> >> > our only mail server. I havn't been able to find anything on how to do
> >> > this
> >> > and I need to know by friday the 29th. Any recomendations would be
> >> > appreciated.
> >>
> >>
> >>
>
>
>
.



Relevant Pages

  • Re: Install new hardware for SBS 2003
    ... I agree Cliff and having done a Swing migration myself I can attest to the ... his plan would not work. ... then the new accounts would obviously cause a mismatch...and ... have to get the current Exchange mail over too. ...
    (microsoft.public.windows.server.sbs)
  • NT 4 Exchange 5.5 to AD and Exchange 2003
    ... have completed migration of user accounts, sid histories, ... Installation of Exchange 2003 in AD domain on new server ... accounts to this location in a sub org called recipients. ... In the root org is also a sub org called users to which it ...
    (microsoft.public.exchange2000.setup.installation)
  • Re: Integrating a newly acquired subsidiary of a big corporation.
    ... I wouldn't use CSVDE because of delimiter problems, but LDIFDE is ... accounts, so groups should be migrated after the accounts. ... because of GUID ties to the source exchange ... I found when I used the exchange migration wizard on the source ...
    (microsoft.public.windows.server.active_directory)
  • Re: Install new hardware for SBS 2003
    ... The plan will work. ... create new user accounts and computer accounts with the *exact* same names ... Personally I'd recommend a "swing" migration. ... have to get the current Exchange mail over too. ...
    (microsoft.public.windows.server.sbs)
  • Re: Managing another domain via AD
    ... Luckily Exchange is not involved. ... in your existent domain is through migration. ... run ADMT to create active user accounts in Active Directory. ... use Migration Wizard to migrate mailboxes. ...
    (microsoft.public.windows.server.active_directory)

Loading