Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 195
  • Last Modified:

Exchange RPC over HTTPS system setup, GC placement, Frontend on another machine

Exchange system setup:

I am trying to get my system setup right and would very much appreciate your insights:

I have two location one in LA (15 people) and one in San Diego (40 People) connected by a T1 via Cisco pix routers

Each location has one 2003 DC, one 2000 DC ( I want to demote these to member servers, they are old) and a one exchange server 2003 as well as some other member servers.

San Diego is the HQ

Everything is up and running fine, however I would like to add RPC over HTTPS, so that I don’t need VPN connections for connection to the exchange servers for remote users.

From what I have read it looks like I should:

Make a the 2003 DC at San Diego the Global Catalog Server(should I make the LA 2003 DC a GC too?) and the front end RPC proxy (Is this in windows components in add and remove programs?).

Then join the two exchange servers as back end servers. Is this right?

Thank you for your help.
0
tehr123
Asked:
tehr123
1 Solution
 
SembeeCommented:
You should have a global catalog domain controller with each Exchange server. You will see performance hits otherwise.

As you don't have a frontend server, keep the deployment simple.
Get each site its own SSL certificate and expose both servers to the internet on port 443. Then make the registry changes for a single Exchange server with a separate domain controller and point it at the closest Windows 2003 GC/DC.

Simon.
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now