Exchange 2003 Service Pack1 Single Server RPC - HTTP (S) Setup Question

[rickiez]

I was looking to set up a RPC over HTTP(s) and all the documentation
isn't very detailed. I have found where you need to enable the exchange
server as a back-end server, but what about the front-end? When you set
it as a back-end server and you don't have a front-end the message box
tells you that you have to have one. Do I really need one? Is all I
really need to do is port forward TCP 443 to the exchange server, set it
up as a back-end and set up Outlook to use RPC-HTTP? Thanks in advance!!

 

[neo [mvp outlook]]

You don't need a front-end server for a smallish setup.

Yes on forwarding HTTPS, however you need to install a web certificate that
IIS can use to secure the site since the default configuration won't allow
for anonymous connection. If you decide to use an internal CA to create the
web certificate, make sure that your workstations have a copy of the public
half of the internal CA. If Outlook 2003 can't verify the chain back to the
signing CA, you won't be able to connect.

/neo

ps - I noticed you didn't mention creating/checking the registry keys that
are going to be necessary on the Exchange server and Global Catalog servers.
Make sure they get created.

pss - because you posted this to a win2k forum, exchange 2003 must be
installed on windows 2003 server and the dc/gcs must be windows 2003 as
well.

 

[rickiez]

Thanks for the tips man. However, my understanding was that w/ SP1 for
Exchange 2003 you didn't have to make those reg changes....or does that
not hold true. Also, I usually use OpenSSL an convert it to an X509.
If I take my CA cert and add it as a trusted CA in IE, is that the only
place I would need to add it? (Does Outlook use the IE settings?)

 

[neo [mvp outlook]]

I've never done a clean install of Exchange 2003 SP1 to be sure. Besides it
doesn't take much time (20 minutes of waiting) to verify the software did
its job.

Yes, that is sufficient in regards to installing the CA cert. (Needs to go
into the Trusted Root Authority)

 

[rickiez]

What do you mean it takes 20 mins of waiting to see if it did it's job?
You mean installing SP1 or waiting 20 mins for Outlook to time out
trying to connect?

I've never done a clean install of Exchange 2003 SP1 to be sure. Besides it
doesn't take much time (20 minutes of waiting) to verify the software did
its job.

Yes, that is sufficient in regards to installing the CA cert. (Needs to go
into the Trusted Root Authority)

Thanks for the tips man. However, my understanding was that w/ SP1 for
Exchange 2003 you didn't have to make those reg changes....or does that
not hold true. Also, I usually use OpenSSL an convert it to an X509. If I
take my CA cert and add it as a trusted CA in IE, is that the only place I
would need to add it? (Does Outlook use the IE settings?)

neo [mvp outlook] wrote:

You don't need a front-end server for a smallish setup.

Yes on forwarding HTTPS, however you need to install a web certificate
that IIS can use to secure the site since the default configuration won't
allow for anonymous connection. If you decide to use an internal CA to
create the web certificate, make sure that your workstations have a copy
of the public half of the internal CA. If Outlook 2003 can't verify the
chain back to the signing CA, you won't be able to connect.

/neo

ps - I noticed you didn't mention creating/checking the registry keys
that are going to be necessary on the Exchange server and Global Catalog
servers. Make sure they get created.

pss - because you posted this to a win2k forum, exchange 2003 must be
installed on windows 2003 server and the dc/gcs must be windows 2003 as
well.



I was looking to set up a RPC over HTTP(s) and all the documentation
isn't very detailed. I have found where you need to enable the exchange
server as a back-end server, but what about the front-end? When you set
it as a back-end server and you don't have a front-end the message box
tells you that you have to have one. Do I really need one? Is all I
really need to do is port forward TCP 443 to the exchange server, set it
up as a back-end and set up Outlook to use RPC-HTTP? Thanks in advance!!

 

[neo [mvp outlook]]

According to the deployment whitepaper, it takes Exchange 15-20 minutes for
the registry updates to happen/take effect.

What do you mean it takes 20 mins of waiting to see if it did it's job?
You mean installing SP1 or waiting 20 mins for Outlook to time out trying
to connect?

I've never done a clean install of Exchange 2003 SP1 to be sure. Besides
it doesn't take much time (20 minutes of waiting) to verify the software
did its job.

Yes, that is sufficient in regards to installing the CA cert. (Needs to
go into the Trusted Root Authority)

Thanks for the tips man. However, my understanding was that w/ SP1 for
Exchange 2003 you didn't have to make those reg changes....or does that
not hold true. Also, I usually use OpenSSL an convert it to an X509. If
I take my CA cert and add it as a trusted CA in IE, is that the only
place I would need to add it? (Does Outlook use the IE settings?)

neo [mvp outlook] wrote:


You don't need a front-end server for a smallish setup.

Yes on forwarding HTTPS, however you need to install a web certificate
that IIS can use to secure the site since the default configuration
won't allow for anonymous connection. If you decide to use an internal
CA to create the web certificate, make sure that your workstations have
a copy of the public half of the internal CA. If Outlook 2003 can't
verify the chain back to the signing CA, you won't be able to connect.

/neo

ps - I noticed you didn't mention creating/checking the registry keys
that are going to be necessary on the Exchange server and Global Catalog
servers. Make sure they get created.

pss - because you posted this to a win2k forum, exchange 2003 must be
installed on windows 2003 server and the dc/gcs must be windows 2003 as
well.



I was looking to set up a RPC over HTTP(s) and all the documentation
isn't very detailed. I have found where you need to enable the
exchange server as a back-end server, but what about the front-end?
When you set it as a back-end server and you don't have a front-end the
message box tells you that you have to have one. Do I really need one?
Is all I really need to do is port forward TCP 443 to the exchange
server, set it up as a back-end and set up Outlook to use RPC-HTTP?
Thanks in advance!!