• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 177
  • Last Modified:

How to create AD Site(s) in existing forest

Abstract: I need to create site(s) in my existing Active Directory to assist with the implementation of DFS.

Environment: Windows 2003 Forest, single domain, two physical sites connected with a 6Mbps link; only one logical site in active directory.  At least one DC exists at each physical site.  No subnets are defined in the Default-First-Site.  All DCs are GCs and the other FSMO roles are held by a DC (DCa) at the main site (Site A).

Problem: I created a new Site in AD to represent my second physical site (Site B).  I then created the proper subnet and site link.  I then moved the DC already present at the physical site (DCb) into Site B.  After a few minutes several of my member servers at Site A became "unavailable".  That is they simply lost network connectivity -- I could not ping to them but I could initiate pings from them.  After moving DCb back to Site A and deleting Site B (and its subnet and removing it from the site link) things started to return to normal.

Question: I have two questions, the first is less important.  1. What could have caused this; and 2. What do I need to do differently when I try this again?

I realize this is somewhat complex and will be around to clarify anything.  Thanks in advance!
  • 2
1 Solution
1) SRV records inside your DNS will contain site information.  By moving the server manually, you broke the process because the DNS records weren't updated to reflect the site change.

2) Don't move the servers into their respective sites. KCC (Knowledge Consistency Checker) will do this for you - it's an automated process.  It will also update the SRV records accordingly.
ryanmcnaughton11Author Commented:

It did seem like a DNS problem.  Thank you so much for your comment.  I'm not sure of the etiquette here but I'm marking this as the solution (I won't have a chance to try this solution until after hours next week).

Thanks for your help.

Adam for Ryan
ryanmcnaughton11Author Commented:

Thanks again for pointing me in the right direction; the actual problem was the DC was missing the _msdcs zone (it was never created after an upgrade from Win2000).

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now