Re: Adding Enterprise Exchange to SBS environment

Mike,

You can't do this. You can do something similiar, though.

Only Exchange 2000/2003 Enterprise Edition can function as a front end
server. If you try to use a standard edition box, the user's browser will
get redirected to the fqdn of their mailbox server which is obviously
inaccessible outside of the corporate network.

So, solution is to point your firewall at the mailbox server for OWA. You'll
need ot open at a minimum port 443 and port 80 to redirect to the secure
connection.

Outlook clients will automatically get updated after you've moved the
mailbox, assuming you're using the move mailbox wizard.

You could use ipsec between the servers fi you feel it's necessary. You'll
want to do some extra testing ot make sure it's all setup right.

Coming from someone who works with medium to very large environments, I see
no issue with this. You've got the DC on one box and Exchange on another.
PSS is probably screaming because you're goofing around with SBS. A SBS
friend of mine tells me that you can uninstall MS Exchange from the SBS box,
however some of hte SBS toys (e.g. the POP3 connector, and probably those
pretty wizards) will get broken.

I'm cc'ing hte SBS2003 group on this as the folks over there know SBS alot
better than I do.
--
--
Brian Desmond
Windows Server MVP


Http://www.briandesmond.com


"Mike Fefferman" <> wrote in message
news:...
> We are adding an Exchange enterprise server to our SBS2003 network. The
> reason being the need for increase storage in the message store. We are
> going to make the SBS box a front end server and make the enterprise
server
> the back end server. I have a couple of questions, first will we have to
> reconnect everyone's mailboxes to the new enterprise server after they are
> moved over or will they automatically find their mailbox after it is
moved?
> Should we configure IPsec between the two servers? And lastly, has anyone
> else done this in production? After talking with Microsft support, they
> said this is not a supported environment.
>
> Thanks,
>
> Mike Fefferman
>
>

Brian,

Thanks for the input. In my reading I thought that with Exchange 2003, you
could make the standard version a front end machine, but not with Exchange
2000.

Mike

"Brian Desmond [MVP]" <> wrote in message
news:...
> Mike,
>
> You can't do this. You can do something similiar, though.
>
> Only Exchange 2000/2003 Enterprise Edition can function as a front end
> server. If you try to use a standard edition box, the user's browser will
> get redirected to the fqdn of their mailbox server which is obviously
> inaccessible outside of the corporate network.
>
> So, solution is to point your firewall at the mailbox server for OWA.
You'll
> need ot open at a minimum port 443 and port 80 to redirect to the secure
> connection.
>
> Outlook clients will automatically get updated after you've moved the
> mailbox, assuming you're using the move mailbox wizard.
>
> You could use ipsec between the servers fi you feel it's necessary. You'll
> want to do some extra testing ot make sure it's all setup right.
>
> Coming from someone who works with medium to very large environments, I
see
> no issue with this. You've got the DC on one box and Exchange on another.
> PSS is probably screaming because you're goofing around with SBS. A SBS
> friend of mine tells me that you can uninstall MS Exchange from the SBS
box,
> however some of hte SBS toys (e.g. the POP3 connector, and probably those
> pretty wizards) will get broken.
>
> I'm cc'ing hte SBS2003 group on this as the folks over there know SBS alot
> better than I do.
> --
> --
> Brian Desmond
> Windows Server MVP
>
>
> Http://www.briandesmond.com
>
>
> "Mike Fefferman" <> wrote in message
> news:...
> > We are adding an Exchange enterprise server to our SBS2003 network. The
> > reason being the need for increase storage in the message store. We are
> > going to make the SBS box a front end server and make the enterprise
> server
> > the back end server. I have a couple of questions, first will we have
to
> > reconnect everyone's mailboxes to the new enterprise server after they
are
> > moved over or will they automatically find their mailbox after it is
> moved?
> > Should we configure IPsec between the two servers? And lastly, has
anyone
> > else done this in production? After talking with Microsft support, they
> > said this is not a supported environment.
> >
> > Thanks,
> >
> > Mike Fefferman
> >
> >
>
>

Hi,

You are right. In Exchange 2003 a standard edition server can be configured
as a front-end server.

Leif

"Mike F" <> skrev i en meddelelse
news:...
> Brian,
>
> Thanks for the input. In my reading I thought that with Exchange 2003,
you
> could make the standard version a front end machine, but not with Exchange
> 2000.
>
> Mike
>
> "Brian Desmond [MVP]" <> wrote in message
> news:...
> > Mike,
> >
> > You can't do this. You can do something similiar, though.
> >
> > Only Exchange 2000/2003 Enterprise Edition can function as a front end
> > server. If you try to use a standard edition box, the user's browser
will
> > get redirected to the fqdn of their mailbox server which is obviously
> > inaccessible outside of the corporate network.
> >
> > So, solution is to point your firewall at the mailbox server for OWA.
> You'll
> > need ot open at a minimum port 443 and port 80 to redirect to the secure
> > connection.
> >
> > Outlook clients will automatically get updated after you've moved the
> > mailbox, assuming you're using the move mailbox wizard.
> >
> > You could use ipsec between the servers fi you feel it's necessary.
You'll
> > want to do some extra testing ot make sure it's all setup right.
> >
> > Coming from someone who works with medium to very large environments, I
> see
> > no issue with this. You've got the DC on one box and Exchange on
another.
> > PSS is probably screaming because you're goofing around with SBS. A SBS
> > friend of mine tells me that you can uninstall MS Exchange from the SBS
> box,
> > however some of hte SBS toys (e.g. the POP3 connector, and probably
those
> > pretty wizards) will get broken.
> >
> > I'm cc'ing hte SBS2003 group on this as the folks over there know SBS
alot
> > better than I do.
> > --
> > --
> > Brian Desmond
> > Windows Server MVP
> >
> >
> > Http://www.briandesmond.com
> >
> >
> > "Mike Fefferman" <> wrote in message
> > news:...
> > > We are adding an Exchange enterprise server to our SBS2003 network.
The
> > > reason being the need for increase storage in the message store. We
are
> > > going to make the SBS box a front end server and make the enterprise
> > server
> > > the back end server. I have a couple of questions, first will we have
> to
> > > reconnect everyone's mailboxes to the new enterprise server after they
> are
> > > moved over or will they automatically find their mailbox after it is
> > moved?
> > > Should we configure IPsec between the two servers? And lastly, has
> anyone
> > > else done this in production? After talking with Microsft support,
they
> > > said this is not a supported environment.
> > >
> > > Thanks,
> > >
> > > Mike Fefferman
> > >
> > >
> >
> >
>
>

Does anyone see any problems with this setup? We have tried it in a virtual
machine environment and had no issues.

Thanks,

Mike Fefferman
"Leif Pedersen [MVP]" <> wrote in message
news:%...
> Hi,
>
> You are right. In Exchange 2003 a standard edition server can be
> configured
> as a front-end server.
>
> Leif
>
> "Mike F" <> skrev i en meddelelse
> news:...
>> Brian,
>>
>> Thanks for the input. In my reading I thought that with Exchange 2003,
> you
>> could make the standard version a front end machine, but not with
>> Exchange
>> 2000.
>>
>> Mike
>>
>> "Brian Desmond [MVP]" <> wrote in message
>> news:...
>> > Mike,
>> >
>> > You can't do this. You can do something similiar, though.
>> >
>> > Only Exchange 2000/2003 Enterprise Edition can function as a front end
>> > server. If you try to use a standard edition box, the user's browser
> will
>> > get redirected to the fqdn of their mailbox server which is obviously
>> > inaccessible outside of the corporate network.
>> >
>> > So, solution is to point your firewall at the mailbox server for OWA.
>> You'll
>> > need ot open at a minimum port 443 and port 80 to redirect to the
>> > secure
>> > connection.
>> >
>> > Outlook clients will automatically get updated after you've moved the
>> > mailbox, assuming you're using the move mailbox wizard.
>> >
>> > You could use ipsec between the servers fi you feel it's necessary.
> You'll
>> > want to do some extra testing ot make sure it's all setup right.
>> >
>> > Coming from someone who works with medium to very large environments, I
>> see
>> > no issue with this. You've got the DC on one box and Exchange on
> another.
>> > PSS is probably screaming because you're goofing around with SBS. A SBS
>> > friend of mine tells me that you can uninstall MS Exchange from the SBS
>> box,
>> > however some of hte SBS toys (e.g. the POP3 connector, and probably
> those
>> > pretty wizards) will get broken.
>> >
>> > I'm cc'ing hte SBS2003 group on this as the folks over there know SBS
> alot
>> > better than I do.
>> > --
>> > --
>> > Brian Desmond
>> > Windows Server MVP
>> >
>> >
>> > Http://www.briandesmond.com
>> >
>> >
>> > "Mike Fefferman" <> wrote in message
>> > news:...
>> > > We are adding an Exchange enterprise server to our SBS2003 network.
> The
>> > > reason being the need for increase storage in the message store. We
> are
>> > > going to make the SBS box a front end server and make the enterprise
>> > server
>> > > the back end server. I have a couple of questions, first will we
>> > > have
>> to
>> > > reconnect everyone's mailboxes to the new enterprise server after
>> > > they
>> are
>> > > moved over or will they automatically find their mailbox after it is
>> > moved?
>> > > Should we configure IPsec between the two servers? And lastly, has
>> anyone
>> > > else done this in production? After talking with Microsft support,
> they
>> > > said this is not a supported environment.
>> > >
>> > > Thanks,
>> > >
>> > > Mike Fefferman
>> > >
>> > >
>> >
>> >
>>
>>
>
>

It will work fine.

--
--
Brian Desmond
Windows Server MVP


Http://www.briandesmond.com


"Mike Fefferman" <> wrote in message
news:uiD$...
> Does anyone see any problems with this setup? We have tried it in a
virtual
> machine environment and had no issues.
>
> Thanks,
>
> Mike Fefferman
> "Leif Pedersen [MVP]" <> wrote in message
> news:%...
> > Hi,
> >
> > You are right. In Exchange 2003 a standard edition server can be
> > configured
> > as a front-end server.
> >
> > Leif
> >
> > "Mike F" <> skrev i en meddelelse
> > news:...
> >> Brian,
> >>
> >> Thanks for the input. In my reading I thought that with Exchange 2003,
> > you
> >> could make the standard version a front end machine, but not with
> >> Exchange
> >> 2000.
> >>
> >> Mike
> >>
> >> "Brian Desmond [MVP]" <> wrote in message
> >> news:...
> >> > Mike,
> >> >
> >> > You can't do this. You can do something similiar, though.
> >> >
> >> > Only Exchange 2000/2003 Enterprise Edition can function as a front
end
> >> > server. If you try to use a standard edition box, the user's browser
> > will
> >> > get redirected to the fqdn of their mailbox server which is obviously
> >> > inaccessible outside of the corporate network.
> >> >
> >> > So, solution is to point your firewall at the mailbox server for OWA.
> >> You'll
> >> > need ot open at a minimum port 443 and port 80 to redirect to the
> >> > secure
> >> > connection.
> >> >
> >> > Outlook clients will automatically get updated after you've moved the
> >> > mailbox, assuming you're using the move mailbox wizard.
> >> >
> >> > You could use ipsec between the servers fi you feel it's necessary.
> > You'll
> >> > want to do some extra testing ot make sure it's all setup right.
> >> >
> >> > Coming from someone who works with medium to very large environments,
I
> >> see
> >> > no issue with this. You've got the DC on one box and Exchange on
> > another.
> >> > PSS is probably screaming because you're goofing around with SBS. A
SBS
> >> > friend of mine tells me that you can uninstall MS Exchange from the
SBS
> >> box,
> >> > however some of hte SBS toys (e.g. the POP3 connector, and probably
> > those
> >> > pretty wizards) will get broken.
> >> >
> >> > I'm cc'ing hte SBS2003 group on this as the folks over there know SBS
> > alot
> >> > better than I do.
> >> > --
> >> > --
> >> > Brian Desmond
> >> > Windows Server MVP
> >> >
> >> >
> >> > Http://www.briandesmond.com
> >> >
> >> >
> >> > "Mike Fefferman" <> wrote in message
> >> > news:...
> >> > > We are adding an Exchange enterprise server to our SBS2003 network.
> > The
> >> > > reason being the need for increase storage in the message store.
We
> > are
> >> > > going to make the SBS box a front end server and make the
enterprise
> >> > server
> >> > > the back end server. I have a couple of questions, first will we
> >> > > have
> >> to
> >> > > reconnect everyone's mailboxes to the new enterprise server after
> >> > > they
> >> are
> >> > > moved over or will they automatically find their mailbox after it
is
> >> > moved?
> >> > > Should we configure IPsec between the two servers? And lastly, has
> >> anyone
> >> > > else done this in production? After talking with Microsft support,
> > they
> >> > > said this is not a supported environment.
> >> > >
> >> > > Thanks,
> >> > >
> >> > > Mike Fefferman
> >> > >
> >> > >
> >> >
> >> >
> >>
> >>
> >
> >
>
>

I have implemented the setup we discussed using the sbs box as the front end
server and the enterprise exchange box as the back end server. Everything
work surprisingly perfect and my users never noticed a difference.

My only question now is how do I configure RPC over HTTP. I have followed
the directions in "Exchange Server 2003 RPC over HTTP Deployment Scenarios"
from Microsoft, but when I established the front end server as the RPC proxy
server it told me to setup ssl. I thought I already had this set up when I
was using the SBS box as the exchange server. I have a certificate setup
that points to my front end exchange server. Do I need to establish one for
the back end server?

Thanks,

Mike



"Brian Desmond [MVP]" <> wrote in message
news:%...
> It will work fine.
>
> --
> --
> Brian Desmond
> Windows Server MVP
>
>
> Http://www.briandesmond.com
>
>
> "Mike Fefferman" <> wrote in message
> news:uiD$...
>> Does anyone see any problems with this setup? We have tried it in a
> virtual
>> machine environment and had no issues.
>>
>> Thanks,
>>
>> Mike Fefferman
>> "Leif Pedersen [MVP]" <> wrote in message
>> news:%...
>> > Hi,
>> >
>> > You are right. In Exchange 2003 a standard edition server can be
>> > configured
>> > as a front-end server.
>> >
>> > Leif
>> >
>> > "Mike F" <> skrev i en meddelelse
>> > news:...
>> >> Brian,
>> >>
>> >> Thanks for the input. In my reading I thought that with Exchange
>> >> 2003,
>> > you
>> >> could make the standard version a front end machine, but not with
>> >> Exchange
>> >> 2000.
>> >>
>> >> Mike
>> >>
>> >> "Brian Desmond [MVP]" <> wrote in message
>> >> news:...
>> >> > Mike,
>> >> >
>> >> > You can't do this. You can do something similiar, though.
>> >> >
>> >> > Only Exchange 2000/2003 Enterprise Edition can function as a front
> end
>> >> > server. If you try to use a standard edition box, the user's browser
>> > will
>> >> > get redirected to the fqdn of their mailbox server which is
>> >> > obviously
>> >> > inaccessible outside of the corporate network.
>> >> >
>> >> > So, solution is to point your firewall at the mailbox server for
>> >> > OWA.
>> >> You'll
>> >> > need ot open at a minimum port 443 and port 80 to redirect to the
>> >> > secure
>> >> > connection.
>> >> >
>> >> > Outlook clients will automatically get updated after you've moved
>> >> > the
>> >> > mailbox, assuming you're using the move mailbox wizard.
>> >> >
>> >> > You could use ipsec between the servers fi you feel it's necessary.
>> > You'll
>> >> > want to do some extra testing ot make sure it's all setup right.
>> >> >
>> >> > Coming from someone who works with medium to very large
>> >> > environments,
> I
>> >> see
>> >> > no issue with this. You've got the DC on one box and Exchange on
>> > another.
>> >> > PSS is probably screaming because you're goofing around with SBS. A
> SBS
>> >> > friend of mine tells me that you can uninstall MS Exchange from the
> SBS
>> >> box,
>> >> > however some of hte SBS toys (e.g. the POP3 connector, and probably
>> > those
>> >> > pretty wizards) will get broken.
>> >> >
>> >> > I'm cc'ing hte SBS2003 group on this as the folks over there know
>> >> > SBS
>> > alot
>> >> > better than I do.
>> >> > --
>> >> > --
>> >> > Brian Desmond
>> >> > Windows Server MVP
>> >> >
>> >> >
>> >> > Http://www.briandesmond.com
>> >> >
>> >> >
>> >> > "Mike Fefferman" <> wrote in message
>> >> > news:...
>> >> > > We are adding an Exchange enterprise server to our SBS2003
>> >> > > network.
>> > The
>> >> > > reason being the need for increase storage in the message store.
> We
>> > are
>> >> > > going to make the SBS box a front end server and make the
> enterprise
>> >> > server
>> >> > > the back end server. I have a couple of questions, first will we
>> >> > > have
>> >> to
>> >> > > reconnect everyone's mailboxes to the new enterprise server after
>> >> > > they
>> >> are
>> >> > > moved over or will they automatically find their mailbox after it
> is
>> >> > moved?
>> >> > > Should we configure IPsec between the two servers? And lastly,
>> >> > > has
>> >> anyone
>> >> > > else done this in production? After talking with Microsft
>> >> > > support,
>> > they
>> >> > > said this is not a supported environment.
>> >> > >
>> >> > > Thanks,
>> >> > >
>> >> > > Mike Fefferman
>> >> > >
>> >> > >
>> >> >
>> >> >
>> >>
>> >>
>> >
>> >
>>
>>
>
>

Mike,

Do you ahve the SSL cert imported into IIS on the frontend? That's crucial
here.

There are quite a few docs if you just google for setting up rpc/http. It
takes some tinkering to get it working right.

--
--
Brian Desmond
Windows Server MVP


Http://www.briandesmond.com


"Mike Fefferman" <> wrote in message
news:...
> I have implemented the setup we discussed using the sbs box as the front
end
> server and the enterprise exchange box as the back end server. Everything
> work surprisingly perfect and my users never noticed a difference.
>
> My only question now is how do I configure RPC over HTTP. I have followed
> the directions in "Exchange Server 2003 RPC over HTTP Deployment
Scenarios"
> from Microsoft, but when I established the front end server as the RPC
proxy
> server it told me to setup ssl. I thought I already had this set up when
I
> was using the SBS box as the exchange server. I have a certificate setup
> that points to my front end exchange server. Do I need to establish one
for
> the back end server?
>
> Thanks,
>
> Mike
>
>
>
> "Brian Desmond [MVP]" <> wrote in message
> news:%...
> > It will work fine.
> >
> > --
> > --
> > Brian Desmond
> > Windows Server MVP
> >
> >
> > Http://www.briandesmond.com
> >
> >
> > "Mike Fefferman" <> wrote in message
> > news:uiD$...
> >> Does anyone see any problems with this setup? We have tried it in a
> > virtual
> >> machine environment and had no issues.
> >>
> >> Thanks,
> >>
> >> Mike Fefferman
> >> "Leif Pedersen [MVP]" <> wrote in message
> >> news:%...
> >> > Hi,
> >> >
> >> > You are right. In Exchange 2003 a standard edition server can be
> >> > configured
> >> > as a front-end server.
> >> >
> >> > Leif
> >> >
> >> > "Mike F" <> skrev i en meddelelse
> >> > news:...
> >> >> Brian,
> >> >>
> >> >> Thanks for the input. In my reading I thought that with Exchange
> >> >> 2003,
> >> > you
> >> >> could make the standard version a front end machine, but not with
> >> >> Exchange
> >> >> 2000.
> >> >>
> >> >> Mike
> >> >>
> >> >> "Brian Desmond [MVP]" <> wrote in
message
> >> >> news:...
> >> >> > Mike,
> >> >> >
> >> >> > You can't do this. You can do something similiar, though.
> >> >> >
> >> >> > Only Exchange 2000/2003 Enterprise Edition can function as a front
> > end
> >> >> > server. If you try to use a standard edition box, the user's
browser
> >> > will
> >> >> > get redirected to the fqdn of their mailbox server which is
> >> >> > obviously
> >> >> > inaccessible outside of the corporate network.
> >> >> >
> >> >> > So, solution is to point your firewall at the mailbox server for
> >> >> > OWA.
> >> >> You'll
> >> >> > need ot open at a minimum port 443 and port 80 to redirect to the
> >> >> > secure
> >> >> > connection.
> >> >> >
> >> >> > Outlook clients will automatically get updated after you've moved
> >> >> > the
> >> >> > mailbox, assuming you're using the move mailbox wizard.
> >> >> >
> >> >> > You could use ipsec between the servers fi you feel it's
necessary.
> >> > You'll
> >> >> > want to do some extra testing ot make sure it's all setup right.
> >> >> >
> >> >> > Coming from someone who works with medium to very large
> >> >> > environments,
> > I
> >> >> see
> >> >> > no issue with this. You've got the DC on one box and Exchange on
> >> > another.
> >> >> > PSS is probably screaming because you're goofing around with SBS.
A
> > SBS
> >> >> > friend of mine tells me that you can uninstall MS Exchange from
the
> > SBS
> >> >> box,
> >> >> > however some of hte SBS toys (e.g. the POP3 connector, and
probably
> >> > those
> >> >> > pretty wizards) will get broken.
> >> >> >
> >> >> > I'm cc'ing hte SBS2003 group on this as the folks over there know
> >> >> > SBS
> >> > alot
> >> >> > better than I do.
> >> >> > --
> >> >> > --
> >> >> > Brian Desmond
> >> >> > Windows Server MVP
> >> >> >
> >> >> >
> >> >> > Http://www.briandesmond.com
> >> >> >
> >> >> >
> >> >> > "Mike Fefferman" <> wrote in message
> >> >> > news:...
> >> >> > > We are adding an Exchange enterprise server to our SBS2003
> >> >> > > network.
> >> > The
> >> >> > > reason being the need for increase storage in the message store.
> > We
> >> > are
> >> >> > > going to make the SBS box a front end server and make the
> > enterprise
> >> >> > server
> >> >> > > the back end server. I have a couple of questions, first will
we
> >> >> > > have
> >> >> to
> >> >> > > reconnect everyone's mailboxes to the new enterprise server
after
> >> >> > > they
> >> >> are
> >> >> > > moved over or will they automatically find their mailbox after
it
> > is
> >> >> > moved?
> >> >> > > Should we configure IPsec between the two servers? And lastly,
> >> >> > > has
> >> >> anyone
> >> >> > > else done this in production? After talking with Microsft
> >> >> > > support,
> >> > they
> >> >> > > said this is not a supported environment.
> >> >> > >
> >> >> > > Thanks,
> >> >> > >
> >> >> > > Mike Fefferman
> >> >> > >
> >> >> > >
> >> >> >
> >> >> >
> >> >>
> >> >>
> >> >
> >> >
> >>
> >>
> >
> >
>
>