Re: Exchange 2003 (2 Sites into 1)

Actually, is there any real documentation to make sure the order is done
correctly and no other little items are missed. Conceptually, I agree, clean
is better, however; just asked about the utility in case we're forced that
route.

Thanks for your help.

"Al Mulnick" wrote:

> For my money, you picked the best route already. The advantage is that you
> won't bring over old stale information. The downside is that replies will
> break unless you modify their new address list (X.500 type address for that
> type email to work). You could use a migration utility instead of exmerge
> and put data right into the mailbox, but my preference is to leave the old
> with the old and move forward. Forces the users to clean up a bit and takes
> care of the adherence to policy.
>
> Al
>
>
>
>
>
>
> "Jenn" <Jenn@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:047286FA-2EB4-42C2-8090-13F65CC41BA6@xxxxxxxxxxxxxxxx
> > We are currently running a clustered Exchange 2003 environment. We
> > purchased
> > a company awhile back who has a stand-alone Exchange 2003 environment.
> > Currently, we have a connector and replication between us for the Global
> > Address book and Distribution lists, but the Exchange domains are not
> > related. We in a multiple-forest AD domain as well. So, they are members
> > of
> > our domain by having another user, but their domain is seperate. (This is
> > another issue for another time)
> >
> > Another problem is their end-users have very large mailboxes (typically
> > 500MB to over 1GB) and we have lower (Around 250mb) limits set on ours and
> > they need to adhere to these limits.
> >
> > I need to move their users into our Clustered Exchange environment. I'm
> > trying to find the best method to do this.
> >
> > I have been thinking about running exmerge on their Exchange server to
> > archive the mail. Then, create mailboxes for their users on Cluster
> > Exchange
> > and start new with them accessing the .pst's like an archive. Then simply
> > point their MX records to us, and decommissioning their Exchange server.
> >
> > What other possiblities exist? What is the least painful?
> >
> > Help, I'm having a hard time finding documentation as it's not an upgrade,
> > but rather Exchange 2003 to Exchange 2003 merge.
> >
> > Thanks in advance for your wisdom.
>
>
>
.

Relevant Pages

  • Re: Exchange services wont start on clean SBS 2003 install
    ... I have found several people in exchange and sbs groups ... using nothing but the wizards on a clean format. ...
    (microsoft.public.windows.server.sbs)
  • Re: Mail bounces back from Exchange ONLY
    ... IP from Verizon and our domain IP and name and they all come up clean. ... Exchange) can send mail to the mercercolor.com domain. ... our ISP directly and not through our Exchange server and their email goes ... as most dynamic ranges are entirely on blacklists. ...
    (microsoft.public.windows.server.sbs)
  • Re: AD all screwed up
    ... or can I work with MS to clean this up during business hours? ... "Jorge Silva" wrote: ... only after that I would add the new server transfer the FSMO roles, DNs, ... be aware that with Exchange you need a GC ...
    (microsoft.public.windows.server.active_directory)
  • Re: Exchange services wont start on clean SBS 2003 install
    ... You've done the install using the wizards from a clean format of the drive? ... > Exchange is timing out. ...
    (microsoft.public.windows.server.sbs)
  • Re: Restoring Exchange 2000 cluster to "standard" Exchange 2000 En
    ... install of Exchange with the computer named EX04. ... Exchange with a different name, do the restore of the databases, then rename ... the Exchange server to the correct name. ... Our previous environment was an environment that wasn't built up using ...
    (microsoft.public.exchange.admin)