How to 'insert' front end Exchange 2003 server

I currently am running 1 Exchange 2003 server (BE) and would like to to add a
new Exchange front end server.
I would prefer to not have to re-configure each users Outlook settings in
order to have them access the FE server instead of the current BE server. I
believe I will need to rename the old BE server, and then rename the new FE
server to the old BE name. Is this correct?
Actually I tried this, and it didn't work. The FE & BE configuration worked,
until I changed the server names. Should I do the renaming before installing
Exchange on the new FE server? Or is there an other (easier) way of
accomplishing this.

All servers are running Server 2003 SP1. Exhange is SP2.
Thank you for any help.

teo
Sat Aug 12 19:57:02 CDT 2006

We'll have to get some technology straight. Outlook can be configured to
access a front end server through RPC/HTTP. This is useful for mobile users
who need to use outlook and access Exchange through the Internet. For most
users, and a simpler solution, OWA Outlook Web Access works fine.


--
Teo Heras



"CraigVS" wrote:

> I currently am running 1 Exchange 2003 server (BE) and would like to to add a
> new Exchange front end server.
> I would prefer to not have to re-configure each users Outlook settings in
> order to have them access the FE server instead of the current BE server. I
> believe I will need to rename the old BE server, and then rename the new FE
> server to the old BE name. Is this correct?
> Actually I tried this, and it didn't work. The FE & BE configuration worked,
> until I changed the server names. Should I do the renaming before installing
> Exchange on the new FE server? Or is there an other (easier) way of
> accomplishing this.
>
> All servers are running Server 2003 SP1. Exhange is SP2.
> Thank you for any help.
>

CraigVS
Sun Aug 13 21:58:01 CDT 2006

Yes I agree that these are other posible ways to connect to the Exchange
server. However I have 100+ users that are using Outlook 2000 & 2003 which
are configured to access Exchange directly. These are the users that I do not
wish to modify their Outlook email account settings.

I wish to have these users start accessing the new FE server instead of the
BE that they are now accessing.

Craig


"Teo Heras" wrote:

> We'll have to get some technology straight. Outlook can be configured to
> access a front end server through RPC/HTTP. This is useful for mobile users
> who need to use outlook and access Exchange through the Internet. For most
> users, and a simpler solution, OWA Outlook Web Access works fine.
>
>
> --
> Teo Heras
>
>
>
> "CraigVS" wrote:
>
> > I currently am running 1 Exchange 2003 server (BE) and would like to to add a
> > new Exchange front end server.
> > I would prefer to not have to re-configure each users Outlook settings in
> > order to have them access the FE server instead of the current BE server. I
> > believe I will need to rename the old BE server, and then rename the new FE
> > server to the old BE name. Is this correct?
> > Actually I tried this, and it didn't work. The FE & BE configuration worked,
> > until I changed the server names. Should I do the renaming before installing
> > Exchange on the new FE server? Or is there an other (easier) way of
> > accomplishing this.
> >
> > All servers are running Server 2003 SP1. Exhange is SP2.
> > Thank you for any help.
> >

Leif
Mon Aug 14 14:50:18 CDT 2006

Hi,

Outlook using standard RPC connects directly to the server where whe user
mailbox is located and never uses a front-end server.

Remark that it is not possible to rename an exchange server (it might be
possible but exchange won't work after the fact).

Exchange front-end servers are for connecting with Outlook using RPC over
HTTP, OWA, OMA, Active-Sync and POP3.

Leif


"CraigVS" <CraigVS@discussions.microsoft.com> wrote in message
news:6CD9BFE3-7473-4861-8C8D-3FA7DF061EF0@microsoft.com...
> Yes I agree that these are other posible ways to connect to the Exchange
> server. However I have 100+ users that are using Outlook 2000 & 2003 which
> are configured to access Exchange directly. These are the users that I do
> not
> wish to modify their Outlook email account settings.
>
> I wish to have these users start accessing the new FE server instead of
> the
> BE that they are now accessing.
>
> Craig
>
>
> "Teo Heras" wrote:
>
>> We'll have to get some technology straight. Outlook can be configured to
>> access a front end server through RPC/HTTP. This is useful for mobile
>> users
>> who need to use outlook and access Exchange through the Internet. For
>> most
>> users, and a simpler solution, OWA Outlook Web Access works fine.
>>
>>
>> --
>> Teo Heras
>>
>>
>>
>> "CraigVS" wrote:
>>
>> > I currently am running 1 Exchange 2003 server (BE) and would like to to
>> > add a
>> > new Exchange front end server.
>> > I would prefer to not have to re-configure each users Outlook settings
>> > in
>> > order to have them access the FE server instead of the current BE
>> > server. I
>> > believe I will need to rename the old BE server, and then rename the
>> > new FE
>> > server to the old BE name. Is this correct?
>> > Actually I tried this, and it didn't work. The FE & BE configuration
>> > worked,
>> > until I changed the server names. Should I do the renaming before
>> > installing
>> > Exchange on the new FE server? Or is there an other (easier) way of
>> > accomplishing this.
>> >
>> > All servers are running Server 2003 SP1. Exhange is SP2.
>> > Thank you for any help.
>> >

Andrew
Tue Aug 15 05:43:10 CDT 2006

So you have 100+ users that have Outlook configured to use
mailserver.mydomain. You have 2 Exchange servers - The old one called
mailserver.mydomain, which is now the BE mail server, and a new one called
fe.mydomain.

When you changed the name of the FE server to mailserver.mydomain, and the
BE server to be.mydomain, did you also change the IP address? If you rename
the servers then ping mailserver.mydomain, do you get the new mail server or
the old one?

It may be that DNS is taking a while to reflect the change, or the client
machines have it cached. Try NBTSTAT -R on one of the clients after you have
renamed the servers and confirmed that the A and PTR records are correct.