Re: Please help me!!! Migrating from Outsourced Exchange to In-House

Tech-Archive recommends: Fix windows errors by optimizing your registry



In news:1140622855.051059.38180@xxxxxxxxxxxxxxxxxxxxxxxxxxxx,
baito7@xxxxxxxxx <baito7@xxxxxxxxx> typed:
Hello

I am faced with a rather difficult task and dilemma. Here is my
scenario:

My company currently hosts Microsoft Exchange 2003 with a third-party
solution that hosts several thousand accounts from different companies
on the same exchange server.

We have built an in-house exchange server that is ready for
deployment. I need to know the best and most seamless way to
transition from the outsourced company to our in-house exchange so
that mail delivery is not disrupted. The email address and domain
name will remain the same.

I have contacted several companies that offer tools for exchange
migration, though my challenge lies in the fact that most of these
companies need the source to set certain privilidges on their exchange
servers so we can migrate the mail. They do not want to do this.
My idea was to pull .psts from them and copy them to users mailboxes.

One option--if the existing clients are using OL2003 in cached mode--you
could export each mailbox to a PST file in that user's profile (then close
Outlook, make sure the PST file name matches their new mailbox's alias name
(e.g., username.pst) and copy it to a folder on your server so you can use
exmerge to import them all at once).
Export public folders to PSTs in Outlook as well, and then when you're done
with the migration, open those PSTs and *copy* the items into the new PFs
you've created.


What is the best way to migrate from the outsourced solution to the
in-house? I was thinking setting up a rule to send all mail to our
server. I was also thinking about setting POP mailboxes in addition
to our exchange.

What for? I'd avoid POP. All you need to do to get mail going to your own
server is to change your domain's public MX record(s). Presuming your server
is ready to receive that mail,

I'd do all of this over a weekend....and beforehand, have whomever hosts
your domain's public DNS set the TTL to something low so changes you make
will take effect more quickly.





Does anyone have any ideas, suggestions, web-links or even experience
in this arena.

Thanks alot.


.

Relevant Pages

  • Re: Exchange Disaster Recovery Server
    ... The backup server is setup also in the lab so I ... >>> The Microsoft Exchange Server computer is not available. ... >>> Microsoft Exchange Server Information Store ...
    (microsoft.public.exchange2000.admin)
  • Exchange 2003 SP1 periodicaly losses connection to active directory for about 30 minutes
    ... We have active directory in two servers but the mail server fails to ... the promotion of the server to active directory the exchange was up. ... After a Domain Controller is promoted to a Global Catalog, ...
    (microsoft.public.exchange.connectivity)
  • Exchange 2003 SP1 periodicaly losses connection to active directory for about 30 minutes
    ... We have active directory in two servers but the mail server fails to ... the promotion of the server to active directory the exchange was up. ... After a Domain Controller is promoted to a Global Catalog, ...
    (microsoft.public.exchange.misc)
  • Re: LDAP Bind Unsuccessful
    ... We have a similar problem with Exchange 2003 and two DC servers 2003. ... After a Domain Controller is promoted to a Global Catalog, ... server that is designated to be a Global Catalog Server but did ...
    (microsoft.public.exchange2000.active.directory.integration)
  • Re: DMZ and AD
    ... and Exchange hosts assuming that the problem of IPSec tunnels to ... Exchange clusters is now recommended) with the intent of requiring fewer ... allow the FE server the communications with the Exchange and Active ...
    (microsoft.public.windows.server.active_directory)