Exchange 2013 & DNS & Active Directory New Install on MS Server 2012
I am trying to finalize a install Exchange 2013 in a small to medium size company.
My points I need to insure I full understanding on is Exchange 2013, DNS and Scheme of Domain Active Directory.
This is not a migration or upgrade. So not to many mistakes can be made. Its a new Exchange 2013 installation in a domain that has never had exchange installed in it before.
I understand not installing on a domain controller and on a member server only but the DNS is the issue.
1) DNS: Do I need to add DNS Manually to the Exchange Server 2013 which is a member server to the Domain do I add the DNS as:
Primary Zone all its own for the "A". MX" "SPF" etc
or a Secondary Zone which is the same as both Domain Controllers so they are same DNS???
2) Do I need to run a prep for exchange on the Domain Controllers. Like in previous versions of Exchange 2003, 2007 you ran prep to the Scheme of the active directory.
3) DNS: I am insuring I have it setup so it will use Spilt DNS when comes to OWA, RPC over HTTP and Exchange Anywhere so that same URL Exchange.domainname.com is being used for when you inside and outside the network.
Any other help advice would be greatlyt appreciated.
Thanks, Clint
My points I need to insure I full understanding on is Exchange 2013, DNS and Scheme of Domain Active Directory.
This is not a migration or upgrade. So not to many mistakes can be made. Its a new Exchange 2013 installation in a domain that has never had exchange installed in it before.
I understand not installing on a domain controller and on a member server only but the DNS is the issue.
1) DNS: Do I need to add DNS Manually to the Exchange Server 2013 which is a member server to the Domain do I add the DNS as:
Primary Zone all its own for the "A". MX" "SPF" etc
or a Secondary Zone which is the same as both Domain Controllers so they are same DNS???
2) Do I need to run a prep for exchange on the Domain Controllers. Like in previous versions of Exchange 2003, 2007 you ran prep to the Scheme of the active directory.
3) DNS: I am insuring I have it setup so it will use Spilt DNS when comes to OWA, RPC over HTTP and Exchange Anywhere so that same URL Exchange.domainname.com is being used for when you inside and outside the network.
Any other help advice would be greatlyt appreciated.
Thanks, Clint
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Yes and I do as well I don't phrase things always in completion because some don't care about the extra details. I still use .PDC and .BDC but also use Microsoft recommendations on real live domain names with proper DNS setup.
I lucky in the respect I do small to medium size that I use Split DNS and IP is changed on MAC address for internal for security reasons etc...
On what you said "That isn't a "back in the day" situation, and it definitely isn't for no reason. Without actually casting an opinion on it myself, since it isn't relevant to your question, all I will say is that plenty of people still choose a private TLD for active directory, like .local, and there are legitimate reasons with pros and cons in doing so. That won't impact your setup either way.
I lucky in the respect I do small to medium size that I use Split DNS and IP is changed on MAC address for internal for security reasons etc...
On what you said "That isn't a "back in the day" situation, and it definitely isn't for no reason. Without actually casting an opinion on it myself, since it isn't relevant to your question, all I will say is that plenty of people still choose a private TLD for active directory, like .local, and there are legitimate reasons with pros and cons in doing so. That won't impact your setup either way.
ASKER
At the original Questions I knew most of what I asked but I at times for get a step so it is nice to hear it again or in a new way.
In past Exchange installation the scheme is changed and updates to the active directory and wanting to insure I do this part correctly... Active directory issues can be a nightmare even on minor accidentals...
Looking at the link on AD.
In past Exchange installation the scheme is changed and updates to the active directory and wanting to insure I do this part correctly... Active directory issues can be a nightmare even on minor accidentals...
Looking at the link on AD.
ASKER
There was no help from "Cliff Galiher", other the offense he got from back in the day lol. There no response back on further help. I had googled found the that answer already from the respondent in the question and google is where I found my solution ultimately.
EE Please delete this questions. Thanks
EE Please delete this questions. Thanks
ASKER
I've requested that this question be closed as follows:
Accepted answer: 0 points for ClintStephenJones's comment #a39897701
for the following reason:
There was no help from "Cliff Galiher", other the offense he got from back in the day lol. There no response back on further help. I had googled found the that answer already from the respondent in the question and google is where I found my solution ultimately.
EE Please delete this questions. Thanks
Accepted answer: 0 points for ClintStephenJones's comment #a39897701
for the following reason:
There was no help from "Cliff Galiher", other the offense he got from back in the day lol. There no response back on further help. I had googled found the that answer already from the respondent in the question and google is where I found my solution ultimately.
EE Please delete this questions. Thanks
Three questions were asked, and my first comment answered all three. Everything else was follow-up, but was neither offensive nor off-topic. Legitimate answers were provided.
ASKER
So just use the DNS setting for my DC on the NIC card of Exchange server and put all the records in the DNS of the main domain controller???
When installing exchange it will update the active directory scheme for 2013 that is???