Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have had success setting up Windows Server 2012 Standard as a domain controller, and have installed Exchange 2013 to test the software.

However, I am clearly not setting it up with best practice, as my Outlook clients are asking that the certificate isn't secure... etc.

I've searched so many sites and help topics - but I am wondering if anyone knows of a "Dummies Guide" style site that can explain exactlt the whole process of setting up a new domain controller, exchange server, forwarding ports, setting up certificates, the whole deal.


share|improve this question

closed as not constructive by HostBits, MDMarra, EEAA, kce, Dave M Mar 8 '13 at 13:57

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.If this question can be reworded to fit the rules in the help center, please edit the question.

This is for external clients use - say 1-5 user sites. Please help with some suggestions. – The Woo Mar 8 '13 at 2:45
Trying to replace SBS2011 with the new 2012. – The Woo Mar 8 '13 at 2:46
Get a non-dummy. This is not a task for rank amateurs. – vonbrand Mar 8 '13 at 12:37

First of all, don't put Exchange on a DC. Ever.

Second of all, there's no "guide" that will effectively cover this whole process. In fact, there are entire books on the proper configuration of AD, and even more books on Exchange.

share|improve this answer
So with the new Server 2012 that doesn't come with Exchange built in - as SBS2011 did - what would you suggest? – The Woo Mar 8 '13 at 2:08
You should have a server dedicate to Exchange in all but the smallest environments. SBS comes with a lot of stuff built in to keep the cost low and keep it simple for low-tech people to use, but that doesn't make it a good idea. – MDMarra Mar 8 '13 at 2:09

Not the answer you're looking for? Browse other questions tagged or ask your own question.