Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 242
  • Last Modified:

Changing Active Directory Domains

Hoping someone can help with a Domain change.  I'm overwhelmed and can't think clearly.

I need to merge (sort of) two separate domains.

Domain 1 is:
     - using SBS (which I want to do away with)
     - with the domain name of citylan
     - with the scope of 172.16.3.XXX
     
Domain 2 is
     - using server 2003
     - with the domain name of annexlan
     - with the scope of 192.168.1.XXX

I want to end up with (I think):
    - Forest of citylan
    - Sites for chlan (changing everyone currently on citylan to this one) and annexlan
    - Everyone using 192.168.1.XXX except for a few computers that need to remain on     172.16.3.XXX


Everyone can use the same gateway except for a few computers.  I currently have two routers/firewalls on each network and there is fiber running between each site.
Just need sites to be able to share resources yet be restricted from full access to other sites computers.

Losing connectivity has to be minimal as this is a 24/7 operation.

I'm not sure if I need to get a third server and build it this way and manually enter each user (ugh) or raise a domain level and merge the other....

Any help is super appreciated!
0
carolinasgirl28
Asked:
carolinasgirl28
  • 2
1 Solution
 
Craig BeckCommented:
Bit messy, but you'd have to perform a migration to a new domain from the SBS box - at the very least.  This would require a new/temporary server.

I would create a new domain, then migrate the users/data from the SBS domain and the annexlan domain to the new domain.  You can do this easily using domain trusts.

I'd treat the site connectivity restrictions as a separate issue.  This is what a firewall is for - not domain security (this is an additional layer).
0
 
carolinasgirl28Author Commented:
How would you handle the two computers that need to stay on the 172 domain?
0
 
Craig BeckCommented:
Exactly the same.

Unless you've got DCs in separate sites, on separate IP ranges, you don't need to worry about this from an AD perspective.  This isn't really an issue with clients.
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

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