Re: Migration from Linux/QMail to SBS2003/Exchange2003

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

From: Pasha Phares (pphares_at_die.spammer.die.imagenetllc.com)
Date: 02/25/04


Date: Wed, 25 Feb 2004 09:16:39 -0800

Susan-

Thanks for the reply. I'm a wordy bastage and after I wrote that all out I
started thinking that most people weren't going to take the time to read
through the whole thing. :)

One problem with doing it directly like that is that until my clients are
into the new facility, getting them connected to Exchange is a hassle; it's
not possible to import PSTs while connected via IMAP, correct? Which means
enabling and configuring the RPC over HTTP thing. I'm leery of that for
security reasons, among other things.

-p

"Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]" <sbradcpa@pacbell.net>
wrote in message news:e6IPfL3%23DHA.3828@TK2MSFTNGP10.phx.gbl...
> You really only need a MX record [this does need to be better documented
> doesn't it ... check out Javier's
http://www.sbslinks.com/DNS_Smarthost.htm
>
> When you have Outlook files in pst... piece of cake... Load up the
> Outlook, click on File, import/export and export out the file... to
> pst... ensure [this is key I screwed up mine the first time] ensure that
> all subfolders is checked... park it on the local drive... now click on
> tools, email accounts, blow off those pop accounts, connect yourself to
> the Exchange server [put in the server name, then the person's mailbox
> name, click check name if things are good the name will "underline"...
> now click ok and close Outlook and reopen it. click File import and
> import that dumped out pst data into your Exchange folders.
>
> Welcome aboard... A busy newsgroup means a healthy community my friend!
>
> :-)
> Pasha Phares wrote:
>
> > Hi all-
> >
> > A newsgroup this busy sorta scares me. :)
> >
> > We've been running a local peer-to-peer network, no DC, no servers of
any
> > kind excepting SQL Servers running as development platforms. Our mail
> > server, DNS, corporate web, and client web sites are all at a colocation
> > facility. They're all various Linux flavors and will remain that way,
> > excepting the mail server. Our mail server is QMail with various
patches
> > and extensions. For the purposes of this post just consider it a
standard
> > IMAP/POP mail server.
> >
> > We're in the process of moving our corporate office to a new facility.
As
> > part of this move we've planned a domain network using SBS2003. At this
> > point the server on which SBS is installed is at our new office, while
all
> > of our users are still at the old office.
> >
> > Exchange 2003 and ISA Server 2003 are both configured and running
smoothly.
> > I can connect and use OWA, RWW, TS, etc., and have created user and
Exchange
> > accounts for all our email users.
> >
> > We've now come to the moment of truth. We need to migrate our users
over to
> > using Exchange instead of IMAP/POP. Some of these users have been using
POP
> > all along and so all their mail is stored in a PST on their local
machine.
> > Others have been using IMAP so it's all on the mail server. An
additional
> > complication is that these users are not on site with the SBS server
yet,
> > and thus will need to access Exchange either via RPC/HTTP or IMAP, using
> > their installed Outlook 2000/Outlook XP.
> >
> > My tentative plan is this:
> >
> > 1) Create a secondary MX record for the Exchange server.
> > 2) Use the POP3 Connector to suck user email to the Exchange server.
> > 3) Enable RPC/HTTP via Exchange and ISA.
> > 4) Configure clients to use IMAP to access their Exchange email.
> > 5) For those POP clients, copy the email stored in Outlook onto the
Exchange
> > server via drag-and-drop in Outlook.
> > 6) Change the MX records to point mail at Exchange and relegate QMail to
a
> > backup.
> > 7) Once all users are physically moved to the new office, switch them
over
> > to using Outlook 2003 and native Exchange connections via
ConnectComputer
> > and ClientInstall functionality.
> > 8) Take a month's vacation.
> >
> > My question to the assembled experts: what am I forgetting? Is there an
> > easier/quicker/more reliable way to do this? I've seen a few posts here
and
> > messages there regarding moves from Sendmail/Postfix to Exchange, but
> > nothing with the sort of meat-and-potatoes details that I need. Would I
be
> > better served to install Connection Manager/VPN client on each client
> > machine and make them use Exchange natively that way? Perhaps just make
> > them use OWA until they're moved to the new office and inside the
firewall?
> >
> > Enough questions? Any input is much appreciated in advance.
> >
> > -p
> >
> >
>
> --
> http://www.sbslinks.com/really.htm
>



Relevant Pages

  • Sending email to mydomain.com
    ... They do not offer an smtp server, ... different from the user account names for the exchange ... I added one user account in the POP3 Mailbox Accounts ...
    (microsoft.public.windows.server.sbs)
  • Re: Critical e-mail problem.
    ... I upgraded from Win2K Server to WinSBS2003 on my desktop ... of my POP3 e-mail accounts as an Exchange Server account. ... I found that I was only receiving mail from the Exchange ... your Outlook profile will have Exchange as its default (and this ...
    (microsoft.public.windows.server.sbs)
  • Re: Critical e-mail problem.
    ... I upgraded from Win2K Server to WinSBS2003 on my desktop ... of my POP3 e-mail accounts as an Exchange Server account. ... I found that I was only receiving mail from the Exchange ... your Outlook profile will have Exchange as its default (and this ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange Name
    ... When Exchange is responsible for an e-mail domain, ... If a local recipient with that e-mail address does not exist, ... Configure the SMTP virtual server in Exchange to send mail with unresolved ... recipients to the Internet service provider's mail server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Migration from SBS to 2003 Enterprise Server - Exchange Disast
    ... > a member server in Domain1.local running Windows 2003 Server Enterprise ... > working Domain2,local server) and restore the mail after the user accounts ... > Outlook to Exchange at the internal 192.168...IP -or- via web browser to ... > appears at the moment that if I could simply change the mailbox store ...
    (microsoft.public.windows.server.sbs)