Re: Best way to implement Front-End/Back-End Exchange 2003

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

From: Rui J.M. Silva (rjms(nospam4me)_at_oninet.pt)
Date: 02/09/05 

Date: Wed, 9 Feb 2005 12:01:15 -0000

It depends on the firewall used.
Basically you only need ports 80/443.
There are lots of documentation on the internet about the subject:
www.msexchange.org
www.msd2d.com
www.searchexchange.com 

-- 
Blog "subject: exchange"
http://spaces.msn.com/members/ehlo/
"justin_dabs" <justin_dabs@hotmail.com> wrote in message 
news:1107901732.252049.209380@g14g2000cwa.googlegroups.com...
Is there any step by step guides on setting up FE/BE exchange servers
with any firewalls? e.g. which ports needs to be opened on the firewall
for successful installation of the FE exchange server.
any help, links etc would be most greatly appreciated.
thanks
justin_dabs
(student of life)
Rui J.M. Silva (nospam4me) wrote:
> Both take the same time.
> Configuring a front-end / back-end architecture takes very little
time, so
> deal first with the migration.
>
> --
> Blog "subject: exchange"
> http://spaces.msn.com/members/ehlo
>
>
> "Iván Sainz" <IvnSainz@discussions.microsoft.com> wrote in message
> news:1834F56C-FFCA-4D62-AD1B-969EFE0874ED@microsoft.com...
> > That is what I thought because of the risk.
> > Option 2 I think is less risky since you do one thing at a time.
> > But, what about time?
> > Does is take more time option 1 than option 2 or just about the
same?
> >
> >
> > "Rui J.M. Silva" wrote:
> >
> >> To setup a front-end server you just need to install the OS and
then
> >> Exchange. There's no configuration issues, besides checking a
check-box,
> >> so
> >> you should deal first with the migration to the future back-end
server.
> >> Option 2), definitelly.
> >>
> >> --
> >> Blog "subject: exchange"
> >> http://spaces.msn.com/members/ehlo/
> >>
> >>
> >>
> >> "Iván Sainz" <IvnSainz@discussions.microsoft.com> wrote in
message
> >> news:5B9AC961-13BB-4210-A15E-42F05CD2A164@microsoft.com...
> >> > Hello,
> >> > I have been assigned a migration from Exchange 5.5 to Exchange
2003.
> >> > The question is whic is the best way to implement a
Front-End/Back-End
> >> > Exchange 2003 architecture?
> >> > 1) FE-BE from the beginning
> >> > 2) Migrate to a single-server architecture and then migrate that
to the
> >> > Front-End/Back-End architecture
> >> >
> >> > I should say why it is better according to time of
implementation and
> >> > risk.
> >> >
> >> > Thank you
> >>
> >>
> >>

Relevant Pages

  • OWA Setup - HELP PLS
    ... How to Configure OWA to Connect to Exchange Through ... through a firewall. ... two ports need to be statically mapped. ...
    (microsoft.public.exchange2000.setup.installation)
  • Add or Edit rules gives message that user must be logged in.
    ... I am running Exchange on Server2003 and Outlook 2003 on a Win XP box. ... The exchange server is outside of my firewall, ... I have configured Outlook to use RPC over HTTP, ... Exchange was using random ports over 1024, ...
    (microsoft.public.exchange.setup)
  • Re: ActiveSync, Exchange 2003 SP2, firewall ports
    ... >I heard that Exchange 2003 SP2 will not require to open the ports on ... > the firewall in order to have ActiveSync working with handheld over the ... > handheld device over the air. ...
    (microsoft.public.pocketpc)
  • Re: Ports numbers used for mapi trough firewall
    ... Between the two domains there is a firewall. ... > I want my outlook XP on the W2k clients to connect to the Exchange ... I have set all the ports as mentioned in KB ... The portnumbers used except the static ports are: ...
    (microsoft.public.exchange2000.connectivity)
  • Re: IPSec question
    ... Anti-Virus software is a fool - DMZ or not. ... > it and all of the Exchange Servers and all of the Domain Controllers. ... > That's either a fair amount of IPSec or a lot of holes in the firewall. ... the Exchange Servers and Domain Controllers! ...
    (microsoft.public.exchange.connectivity)