Exchange 2010 and internal/external DNS
I'm sure this is an easy one, but I can't seem to wrap my head around it.
#1 I have an SBS 2003 server with a FQDN of srvr1.easyco.local. I have just added a new windows 2008 R2 server to the
network wi th a new forest and it's FQDN is srvr1.easyco98.local. (Eventually we are phasing out the sbs 2003 that's why
I've started a new forest - but that's another topic.) On the new 2008 R2 server I'm only going to run Exchange 2010.
My workstations all look to the SBS 2003 server for their default DNS. I'm stumped on what I need to add on the sbs 2003
DNS so that all my workstations can resolve the new server name. I've tried a few things and with some success, but I need
the experts to advise me on this.
#2 Since I'm using a .local as my domain name what happens when I'm outside the network with my laptop and open Outlook? Is it going
to be looking for the .local name?
This is my first experience with exchange, I've been a GroupWise admin for many years and struggling.
Thanks in advance for any help you can give this old dog. Please teach me new tricks.
#1 I have an SBS 2003 server with a FQDN of srvr1.easyco.local. I have just added a new windows 2008 R2 server to the
network wi th a new forest and it's FQDN is srvr1.easyco98.local. (Eventually we are phasing out the sbs 2003 that's why
I've started a new forest - but that's another topic.) On the new 2008 R2 server I'm only going to run Exchange 2010.
My workstations all look to the SBS 2003 server for their default DNS. I'm stumped on what I need to add on the sbs 2003
DNS so that all my workstations can resolve the new server name. I've tried a few things and with some success, but I need
the experts to advise me on this.
#2 Since I'm using a .local as my domain name what happens when I'm outside the network with my laptop and open Outlook? Is it going
to be looking for the .local name?
This is my first experience with exchange, I've been a GroupWise admin for many years and struggling.
Thanks in advance for any help you can give this old dog. Please teach me new tricks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Yes, I would still recommend doing the whole procedure.
ASKER
I'm justing going through the doc and notice that the last step #13 DCpromo SBS 2003 server so it is no longer a domain controller and remove from network. In my scenario we are still using the SBS 2003 server. We're just adding a 2008 R2 and installing exchange. Can I just stop after the 12th step?
Thanks again for all your help. It is greatly appreciated.
Thanks again for all your help. It is greatly appreciated.
Yes, if you are not removing SBS then don't transfer the FSMO roles or DCPROMO the SBS server.
ASKER
Thanks