New Server Exchange 2013 in Exisiting Domain
Posted on 2013-11-15
I need help with advice, forgotten info and how to's on Setting up an Exchange Server 2013.
- Exchange Setup and Integration.
- Split DNS
- RPC over HTTPS (also known as Outlook Anywhere)
-- client protocol management for Exchange ActiveSync, POP3, and IMAP4 is also handled on the Client Access server.
- Real world FQDN as the servers and exchange / outlook FQDN.
I have an existing domain with 2 domain controllers.
There are 3 new servers.
They will all become part of the existing domain.
ALL SERVERS ARE RUNNING - Windows Server 2012.
CTCSVR003 - New Exchange Server 2013
CTCSVR004 - New Share Team Server 2013
CTCSVR005 - New Web Server IIS 8.0
I am googling everything to get up to speed but professional real world help is preferred.
I understand the domain / forest scheme updated as usual.
I do want to insure proper:
- Domain Controller Integration - Should I make Exchange 2013 a Domain Controller???
- Split DNS - So when you leave the office with your Phone, Tablet, Laptop the settings with not need to be changed or forced to use OWA.
- Do make just a member server with the DNS setup as just a primary DNS server of its own with just the IP addresses of the DNS / Domain Controllers in its DNS and IP setup???
Any thing I might need to research more that i left out please - Push me any direction you see I need to look at further.
Thanks, For all your help.