Re: Moving from ISP Mail to Exchange

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Brian,

One more if you have time.

Once this is done, and all is working, are their any other docs I need to
look for to do things like shared calendaring and OWA and spam and spyware
blocking on the server than the ones mentioned in my previous note (admin
guide, and deployment guide)?


Thanks for your help!

Mike


"Brian Desmond [MVP]" wrote:

> Mike,
>
> This certainly helps. What you want to do is actually fairly easy. Some prep
> work involved, but not much:
>
> Get Exchange loaded and configured on your mailbox server. The wizards and
> what have you included with 2003 are pretty handy for a first timer like
> you. Get SP1 for Exchange and Windows on there as well. I think htere's an
> Internet Mail wizard in Exchange 2003 for getting setup to receive internet
> mail. Otherwise, it's not that hard to go in ESM and change the default smtp
> address to *@mydomain.com
>
> You can then mailbox enable your users
>
> As far as firewall, just need to forward 25 to your mailbox server for SMTP
>
> As far as DNS, will need to create an A record pointing to the publci IP
> that has 25 open on the firewall for the exchange server, and edit the mx
> record to point to this new A record.
>
> For clients, ahve to go in and create a new exchange server account and
> change their default delivery location. Do this step before you do the above
> DNS config.
>
> --
> --Brian Desmond
> Windows Server MVP
> desmondb@xxxxxxxxxxxxxxxxxxxx
>
> www.briandesmond.com
>
>
> "Mike" <Mike@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:66780A08-2780-4F88-8A64-FAA48F2156DE@xxxxxxxxxxxxxxxx
> > Brian,
> >
> > Thanks for the note. Yes, I knew it was somewhat vague but didn't know
> > how
> > much detail to include.
> >
> > I have never ran Exchange before so I am nervous about making the switch,
> > but basically I have Exchange 2003 installed on one Server, and as best I
> > can
> > tell the normal setup and install went fine. Our company is somewhat small
> > (35 employees), and our e-mail is currently hosted by our ISP, and so the
> > users Outlook are set for POP3, and point to the ISP's e-mail servers.
> > What
> > I am looking for is a step by step process of how to properly change from
> > our
> > e-mail being hosted by the ISP to my Exchange Server. Some of the steps
> > involved would have to be a) having the ISP point the MX records to my
> > server, b) having certain ports opened on my firewall for mail delivery,
> > and
> > c) configuring the client machines to look to our server instead of our
> > ISP's
> > for e-mail. I'm sure there are several steps more to make all of that
> > happen.
> > Then, after that is working good, set up shared calendaring, and Outlook
> > Web
> > Access, learn how to block spam, etc, but that is after the mail is
> > working
> > properly.
> > I have downloaded and printed the deployment guide, and admin guide, and
> > they have steps to move from older Exchange to Exchange 2003, but I don't
> > see
> > anything about my scenario. It might be no more difficult than the steps
> > above, but I wanted to bounce it off of somebody before I throw a switch
> > and
> > have a disaster on my hands. Does that help?
> >
> > Thanks,
> >
> > Mike
> >
> >
> > "Brian Desmond [MVP]" wrote:
> >
> >> Mike,
> >>
> >> Can you go into more detail on exactly what you want ot accomplish? I can
> >> probably help, as can others here, just that your question is rather
> >> vague.
> >> Do you just want to have your users receive mail via your Exchange
> >> server,
> >> or is there more involved here?
> >>
> >> --
> >> --Brian Desmond
> >> Windows Server MVP
> >> desmondb@xxxxxxxxxxxxxxxxxxxx
> >>
> >> www.briandesmond.com
> >>
> >>
> >> "Mike" <Mike@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> >> news:B6D428B9-6FF6-4612-9E2F-E5FC82720BFD@xxxxxxxxxxxxxxxx
> >> > Hi,
> >> >
> >> > I have recently installed Exchange 2003 in our company, and want to
> >> > begin
> >> > the task of moving our e-mail from being hosted at our ISP to our
> >> > Exchange
> >> > Server, and I am looking for "How to's" or documents describing all of
> >> > the
> >> > steps involved. I have poked around on the Exchange Site on MS web
> >> > site,
> >> > but
> >> > don't quite see anything like what I am looking for. Any advice?
> >> >
> >> > Thanks,
> >> > Mike
> >> >
> >>
> >>
> >>
>
>
>
.

Relevant Pages

  • Re: Sharepoint Administrator and SubWebs
    ... Mike, I suspec5t you are right about STS, being that the website is ... > Subweb is the term used in STS for what in WSS is called sub-sites. ... > Can you also please state the Operating System being used for your Exchange ... > in which case WSS will not run at all on theat server only WSS. ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Echange Backup
    ... Exchange Deployment Guide. ... mal den Deployment Guide und die Online Hilfe durch. ... MVP ISA / Exchange Server ...
    (microsoft.public.de.german.exchange2000.general)
  • Re: w95.hybris.worm on SBS 2003
    ... Mike - I lean towards your explanation, but I'm not familiar enough with ... Exchange to say what is happening. ... There are good SBS groups here, ... I'm sorry this isn't a server group I ...
    (microsoft.public.security.virus)
  • Re: RPC over HTTP, NAT firewall, authentication problems
    ... This solution cost me $312.00 Mike, ... exchange man….” is selected. ... Restart the server. ... "To configure the RPC proxy server to use specified ports for RPC over HTTP" ...
    (microsoft.public.exchange.setup)
  • RE: 5.5 to 2003 migration & recipient connection agreement question
    ... match the procedures listed in the Deployment Guide. ... site and server protocol port to 3890, ... > After you install Exchange 2003, do you recommend keeping the recommended ... > to change the connection agreements to connect to the Exchange 2003 sever ...
    (microsoft.public.exchange.setup)