This is probably what they are talking about:
http://support.microsoft.com/default.aspx?scid=kb;en-us;314649

If it is, please point out to them that this is not a show-stopper at all.
Actually, it's easily rectified. Chances are that it may not even apply to
you at all. If this is not what they are talking about, ask them for
specifics and let us know what they are referring to. Simply saying "there's
a problem" IS a problem.

side note: I wasn't aware that Dell now does Exchange/AD consulting :)
--
Sincerely,

Dèjì Akómöláfé, MCSE MCSA MCP+I
www.akomolafe.com
www.iyaburo.com
Do you now realize that Today is the Tomorrow you were worried about
Yesterday? -anon
"Brian Desmond [MVP]" <desmondb@payton.cps.k12.il.us> wrote in message
news:Ow1NtkxCEHA.2424@TK2MSFTNGP09.phx.gbl...
> Hi Matthew,
>
> No problem on the crosspost - it's not at all unreasonable.
>
> The Dell guy is right about mangling some attributes, but there is a fix:
> http://support.microsoft.com/default.aspx?kbid=314649&product=winsvr2003.
>
> I'm not an Exchange expert, but, if I'm not mistaken, Exchange Servers all
> have to be in the same organization to move mailboxes amongst them, which
> means, that if you move your users to the child domain of the parent
> company, the mailboxes are not coming with. I may very well be wrong on
> this. The Exchange MVPs on the exchange2000 group will probably pick this
up
> and correct me.
>
> --
> --
> Brian Desmond
> Windows Server MVP
> desmondb@payton.cps.k12.il.us
>
> Http://www.briandesmond.com
>
>
> "Matthew Kitchin" <matthewkitchin_public@hotmail.com> wrote in message
> news:%23pXNsdwCEHA.3256@TK2MSFTNGP09.phx.gbl...
> > Sorry for the cross post. I wouldn't normally do that, but I really
don't
> > know where the issue lies.
> >
> > My company has been acquired by another. They are 2003 active directory,
> and
> > in the process of migrating to Exchange 2003 from 5.5. I am exchange
2000,
> > AD 2000. The other company has hired 2 Microsoft professionals from Dell
> to
> > handle most of this.
> >
> > Their domain won't be native for a while, because they have 18 BDCs
around
> > the country. Mine is Native (AD and Exchange). This presents us with
> several
> > issues. They want to fold my domain into theirs. I recommended creating
a
> > child domain on their site, putting it in Native mode, and migrating my
> > users to that. The Dell consultant told me their is a attribute
corruption
> > issue when moving exchange users from a 2000 AD to a 2003 AD. I said,
ok,
> I
> > will upgrade my AD to 2003. I only have 4 DCs with a root and child
> domain,
> > so it would take a weekend at most. He then said that would produce the
> same
> > attribute corruption issue. He said it occurs when running the various
> preps
> > (domain, forest) to prepare the 2000 AD to be upgraded to 2003.
> >
> > Surely there is a supported way to upgrade a 2000 AD with Exchange 2000
> (in
> > a cluster) to 2003 AD. He said this issue pertained to 4 attribute
fields.
> > They could get corrupted and require you to completely delete the
affected
> > accounts. Does anyone have any documentation on this?
> >
> > Thanks,
> > Matthew
> >
> >
>
>