| Author |
Message |
P
Guest
|
 Posted:
Thu Aug 25, 2005 5:00 pm Post subject:
Front End/Information Store |
|
|
Another dumb Backend/frontend question.. Can I safely designate a Exchange
2003 server with an information store on it as a front end for other Exchange
2003 servers and still have the server function properly? Currently it is
acting as a psuedo front end and redirecting users to their home server when
they login via OWA and they are having to reauthenticate.
Wanting to move this to SSL with only one cert on the public facing server,
but a little afraid that clicking the front end box will cause other problems
on a server with an information store hosted on it, and don't want to
dedicate a server to only being a front end server if I can avoid it.
|
|
| Back to top |
|
 |
Al Mulnick
Guest
|
| Posted:
Thu Aug 25, 2005 5:00 pm Post subject:
Re: Front End/Information Store |
|
|
If you leave the information store on that server, just don't put any user
mailboxes on it.
Having a FE server with an information store is a valid configuration and is
required for SMTP traffic.
Al
"P" <P@discussions.microsoft.com> wrote in message
news:BC935E85-5030-4B61-A35C-11C29110060E@microsoft.com...
| Quote: | Another dumb Backend/frontend question.. Can I safely designate a
Exchange
2003 server with an information store on it as a front end for other
Exchange
2003 servers and still have the server function properly? Currently it is
acting as a psuedo front end and redirecting users to their home server
when
they login via OWA and they are having to reauthenticate.
Wanting to move this to SSL with only one cert on the public facing
server,
but a little afraid that clicking the front end box will cause other
problems
on a server with an information store hosted on it, and don't want to
dedicate a server to only being a front end server if I can avoid it.
|
|
|
| Back to top |
|
|
P
Guest
|
| Posted:
Thu Aug 25, 2005 11:03 pm Post subject:
Re: Front End/Information Store |
|
|
Thanks.. so its not possible to have any mailboxes exist on the front end
server at all? Trying to figure out the best way to do this without
dedicating another server.
"Al Mulnick" wrote:
| Quote: | If you leave the information store on that server, just don't put any user
mailboxes on it.
Having a FE server with an information store is a valid configuration and is
required for SMTP traffic.
Al
"P" <P@discussions.microsoft.com> wrote in message
news:BC935E85-5030-4B61-A35C-11C29110060E@microsoft.com...
Another dumb Backend/frontend question.. Can I safely designate a
Exchange
2003 server with an information store on it as a front end for other
Exchange
2003 servers and still have the server function properly? Currently it is
acting as a psuedo front end and redirecting users to their home server
when
they login via OWA and they are having to reauthenticate.
Wanting to move this to SSL with only one cert on the public facing
server,
but a little afraid that clicking the front end box will cause other
problems
on a server with an information store hosted on it, and don't want to
dedicate a server to only being a front end server if I can avoid it.
|
|
|
| Back to top |
|
|
Al Mulnick
Guest
|
| Posted:
Thu Aug 25, 2005 11:04 pm Post subject:
Re: Front End/Information Store |
|
|
Nope. It won't work.
"P" <P@discussions.microsoft.com> wrote in message
news:B5CF15BA-6B5E-4102-8151-BF37EBD10B8F@microsoft.com...
| Quote: | Thanks.. so its not possible to have any mailboxes exist on the front end
server at all? Trying to figure out the best way to do this without
dedicating another server.
"Al Mulnick" wrote:
If you leave the information store on that server, just don't put any
user
mailboxes on it.
Having a FE server with an information store is a valid configuration and
is
required for SMTP traffic.
Al
"P" <P@discussions.microsoft.com> wrote in message
news:BC935E85-5030-4B61-A35C-11C29110060E@microsoft.com...
Another dumb Backend/frontend question.. Can I safely designate a
Exchange
2003 server with an information store on it as a front end for other
Exchange
2003 servers and still have the server function properly? Currently it
is
acting as a psuedo front end and redirecting users to their home server
when
they login via OWA and they are having to reauthenticate.
Wanting to move this to SSL with only one cert on the public facing
server,
but a little afraid that clicking the front end box will cause other
problems
on a server with an information store hosted on it, and don't want to
dedicate a server to only being a front end server if I can avoid it.
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in