Re: Exch 2007 & 2003

Tech-Archive recommends: Speed Up your PC by fixing your registry

Hey guys,

Thanks for the info Bharat.

If the budget is unavailable until 3rd quarter, which I am going to guess is
what will happen (and Exchange has to be implemented by end of January of
course), I should install 2003 on the back-end server and use 2007 as the
front-end / CAS for now and when the money does become available, upgrade the
back-end server at that point?

If that is possible, will I have to redo the CAS server at that point or
will the various 2007 functions automatically activate?

Alternatively, would I be better off, security aside, to just put a single
2007 server in the DMZ and hope nothing happens until I get money to move the
2003 server to 2007?

Thanks in advance,

Joel

"Bharat Suneja [MVP]" wrote:

An Exchange 2003 or Exchange 2000 front-end server cannot provide access to
an Exchange 2007 Mailbox server. In addition, an Exchange 2007 Mailbox
server cannot send or receive e-mail messages if a Hub Transport server does
not also exist in its Active Directory site. Therefore, when upgrading an
existing Exchange organization, we recommend that you install the Client
Access and Hub Transport server roles before installing the Mailbox server
role. If you install the Mailbox server first, you will not have client
access or mail flow to or from the Mailbox server until you install the
Client Access and Hub Transport server roles.
http://www.microsoft.com/technet/prodtechnol/exchange/e2k7help/406a2d1a-ddc6-4d43-a162-c7179d31a973.mspx

Just installing an Exchange Server 2007 Client Access Server (CAS -
equivalent to a Front-End in 2003) - without an Exchange Server 2007 server
with Mailbox & Hub Transport role doesn't really buy you anything. Users on
the Exchange Server 2003 Back-End will still see the Exchange 2003 OWA
interface.

I would recommend finding the budget to move both servers to Exchange Server
2007.
--
Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
www.exchangepedia.com/blog
----------------------------------------------



"Joel M." <JoelM@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E3E6EFF4-8566-4C3D-AC9F-D7ACF3077679@xxxxxxxxxxxxxxxx
Hi all,

Our domain is a plain Windows Server 2003 AD integrated domain. I am
about
to add Exchange to the mix, but due to some timeline and budget issues, I
have ended up with two servers and one license for Exchange 2003 and one
license for Exchange 2007. The hardware is geared towards one BE and one
FE
server with the BE having 8 GB RAM and multiple RAID SCSI cards and the FE
having one RAID card.

Which server should be running 2003 and which should run 2007, or would I
be
better off trying to allocate money from other budgets and get both
servers
to 2007? I plan on using rpc over https, owa, fax sharing and eventually
unified messaging and some custom mapi programming.

Thanks in advance.

Joel



.

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)
  • Exchange Service Pack 1 Install fails
    ... I have a Small Business Server 2003 set up. ... Exchange SP1 resolves. ... before installing this Microsoft Exchange Server Service Pack. ...
    (microsoft.public.exchange.setup)