• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 173
  • Last Modified:

How to configure 3 servers in my network?

I have three servers in my network all behind a firewall.  I am looking for an answer to the best practice on how to configure my network.  This is the functionality I need to support:

1. Mail Server (Exchange)
2. Web Server (IIS)
3. File Server

Currently, this is split into two domains: 1 machine is the mail server and webserver.  It is in it's own domain on the private network (xxx.net).  It is running AD and DNS, and is a DC.  One other server is the file server, and it is in another domain (.org).  It is running AD, is a DC, and is running DNS.  The final server is also in the .org domain, and is currenlty just a back for the main server's AD, so it is also running AD, is a DC, and is running DNS.

My question is this.  Should I keep it this way?  It seems like they should all be in the .net domain, using the same AD.  That way, I don't have to run the Exchange server as a DC, and can demote it to a member server using the AD from the "main" server.  The last server I can use as a backup server in case one of the other servers goes down.

Any comments or suggestions are welcome as to how to configure these servers.

Thanks!
0
mdiehly64
Asked:
mdiehly64
  • 2
  • 2
1 Solution
 
MesthaCommented:
Running DCPROMO on an Exchange server is not supported. That will usually break Exchange.
If you only have three servers then ideally they need to be in the same AD domain, two as domain controllers and one as a member server for Exchange. However if you have a public web site running on a server that really shouldn't be part of the domain at all.

Simon.
0
 
mdiehly64Author Commented:
Ok, so  you would recommend this:

Server1: DC / File Server (xxx.net)
Server2: DC / File Server (xxx.net)
Server3: Member Server/Exchange (member of xxx.net)
Server4: Standalone (no AD)/ Web Server (no AD)

All behind a firewall with forwarding rules.  It sounds like I'd have to reinstall a server (or demote my current backup DC), make it a member server, install Exchange, then move my mailbox store to the new server.  Then remove Exchange from the first server and it becomes a DC for xxx.net.  Then just run DCPROMO on the third server to demote it, then run DCPROMO again to join the xxx.net domain.  It also sounds like you are recommending that a new machine be set up as the webserver (it gets almost no traffic).
0
 
MesthaCommented:
If the web server gets no traffic, then unless the web site is doing something that means it needs to have network access, throw it out to a host. Web hosting is cheap these days, with more bandwidth than you will ever get - much cheaper and more secure than running your own server.

Simon.
0
 
mdiehly64Author Commented:
Since we aren't using OWA, and I already have a machine provisioned for the web, I think I'll keep it in-house.  Zero cost that way, and if I keep it seperate from the domain, I should be ok.  I may even put it in a DMZ by itself.

Thanks!
0

Featured Post

[Webinar] Cloud and Mobile-First Strategy

Maybe you’ve fully adopted the cloud since the beginning. Or maybe you started with on-prem resources but are pursuing a “cloud and mobile first” strategy. Getting to that end state has its challenges. Discover how to build out a 100% cloud and mobile IT strategy in this webinar.

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