Creating new site

  • Thread starter Thread starter James
  • Start date Start date
J

James

Here is what I got. I have just the default site now. I want to add
another site for one of our locations. I have a member server at that
location that I am going to run dcpromo and make a domain controller and dns
server. Here is my question. What order should I do all of this? This is
what I think but need to make sure.

1. Create new site.
2. Add subnet to the new site.
3. Upgrade server to DC.

If I already have the site and subnet created will it automatically put
the new DC in the new site?


Thanks,
James
 
James said:
Here is what I got. I have just the default site now. I want to add
another site for one of our locations. I have a member server at that
location that I am going to run dcpromo and make a domain controller and
dns server. Here is my question. What order should I do all of this? This
is what I think but need to make sure.

1. Create new site.
2. Add subnet to the new site.
Click to expand...

2A. Add new SiteLink
2B. Remove new Site from Default-IP-SiteLink*
3. Upgrade server to DC.
Click to expand...

*2A-B is not technically necessary for 2nd (1st manual) site, but should
become
a habit as subsequent sites typically need to distinguish their site link
from the
original Default.
If I already have the site and subnet created will it automatically put
the new DC in the new site?
Click to expand...

Yes, it SHOULD do that.

You should always check to ensure that happened correctly and move it
if it didn't.

Step 4. Run complete "DCDiag /c >dcname.txt" on EACH DC to ensure
replication, DNS, etc is correct.

Repeate step 4 regularly (>weekly) and before/after any significant DC
maintenance or changes, or anytime you suspect replication, authentication,
or access to resources problems.
 
Thanks. After adding the site and subnet I upgraded the dc. I noticed that
when i restarted our exchange server which is located in the default site
the topology discovery would fail. After some digging I read that the
exchagne subnet had to be defined to be able to access and discover other
sites. My question is this. We have about 7 physical locations that are all
part of our default site. Do I really need to add the subnet for each
location if we do not have any servers or anything at those locations? The
only thing at those locations are printers and workstations and they access
all of the servers and things at our main location.

Thanks,
James
 
James said:
Thanks. After adding the site and subnet I upgraded the dc. I noticed that
when i restarted our exchange server which is located in the default site
the topology discovery would fail. After some digging I read that the
exchagne subnet had to be defined to be able to access and discover other
sites. My question is this. We have about 7 physical locations that are
all part of our default site. Do I really need to add the subnet for each
location if we do not have any servers or anything at those locations?
Click to expand...

Technically "no" but I find it a good practice to define even the default
site.
The only thing at those locations are printers and workstations and they
access all of the servers and things at our main location.
Click to expand...

Those aren't true sites and can either be set as sites (with specific
subnsets
AND site links) or left as part of the adjacent (default?) site.
 
Back
Top