Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows Server 2003Windows 2000Windows NTSmall Business ServerVirtual ServerExchange ServerIISHost Integration ServerISA ServerSMSWSUSMOMWindows Media ServerSecurityCertification
Related Topics
SQL ServerMS WindowsMS OfficePC HardwareMore Topics ...

Windows Server Forum / Exchange Server / Design / August 2005

Tip: Looking for answers? Try searching our database.

RPC over HTTP single server setup

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
jacksors - 23 Aug 2005 20:18 GMT
We have only a single Exchange 2003 server running SP1 in a 2003 AD
environment. We need to configure it to support RPC over HTTP. The articles I
have found say that for single server designs, the exchange server requires
that it be a Global Catalog as well. Does this mean I need to make my
exchange server a domain controller as well?

This does not seem like the best design. Are there any security concerns
with having my mail server also be a domain controller?
Don Wilwol - 24 Aug 2005 00:34 GMT
No, you should not make the Exchange server a DC if you can help it. Follow
this article, it doesn't say anything about making the Exchange server a DC.
http://support.microsoft.com/default.aspx?kbid=833401

The reference to a global catalog is just referencing ports used by
Exchange.

Signature

Hope it helps

dw

_______________________________
Don Wilwol
donwilwol(DELETE)@yahoo.com
http://spaces.msn.com/members/wilwol/

> We have only a single Exchange 2003 server running SP1 in a 2003 AD
> environment. We need to configure it to support RPC over HTTP. The
[quoted text clipped - 6 lines]
> This does not seem like the best design. Are there any security concerns
> with having my mail server also be a domain controller?
jacksors - 24 Aug 2005 19:29 GMT
This was the article I was referencing. What particularly caught my attention
was the statement at the beginning of the article: "Single server
In this configuration, you have a single server that is configured to
function as a global catalog server, an Exchange computer, and an RPC proxy
server."

so what I take that to mean, is exactly what it says. The server needs to
have exchange on it, host a GC, and have the RPC over HTTP proxy component
loaded.

Later in the article it discusses that the registery needs to be modified on
all GC servers. The registry key it refeneces does not exist on my Exchange
box currently because it is not a GC. If I dont have to install AD that would
be great. However, this article leads me to believe that I have no other
choice.

If I were to not install AD on the exchange server, and modify the registery
on the domain controllers hosting GC's, would I then also need to load the
RPC over HTTP protocol on the domain controllers as well?

With this design it seems like we are moving to a multiple server
configuration instead of the single server configuration as referenced in the
title of the article. I don't see any way around making the exchange server a
DC. I would like to avoid this at all costs.

> No, you should not make the Exchange server a DC if you can help it. Follow
> this article, it doesn't say anything about making the Exchange server a DC.
[quoted text clipped - 13 lines]
> > This does not seem like the best design. Are there any security concerns
> > with having my mail server also be a domain controller?
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.