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

Adding extended perimeter network to existing domain

I had this question after viewing Advice on fixing AD replication.

So after everyone helped me resolve my replication tweak, I would appreciate some advice on my next task- creating a RODC on an extended perimeter network.

I need to create a new RODC on a new subnet that will be part of our existing domain. It will be a new "DMZ" site in ADSS. It will be located in the same colocation facility as my "VPN" site. My plan is to create a site link b/t the "DMZ" and "VPN" sites so the RODC only communicates with the local writable DC in the subnet closest to it.

I'm reading through all the TechNet guides now on all the various tasks to do (firewall rules, password policies, filtered attribute set).

I've created a server-core install of W2K12.

If anyone has any advice on their favorite doc that walks me through the details for this scenario, that would be greatly appreciated. TechNet is lacking on the details sometimes
  • 2
1 Solution
Krzysztof PytkoSenior Active Directory EngineerCommented:
OK, these 2 documents would be your friends for couple of days ;)

First one is about good practices to deploy RODC in DMZ

the second one is about securing replication between RODC from DMZ to your network by limiting dynamic ports range

You should avoid situation which allows to have all dynamic ports opened in perimeter network, for security reasons.

and of course also very important topic, setting up Site for RODC, defining Subnet(s) and connecting it to other Site(s). Please also take a look at this article explaining the topic about Sites, Subnets and Site links at https://technet.microsoft.com/en-us/library/cc754697(v=ws.11).aspx

If you would have more questions, do not hesitate to ask.

RhoSysAdminAuthor Commented:
So you were right. You have to take your time reading through these. I'm only through the first "design" doc now.

I have a bit of a chicken and egg situation. Our domain and forest functional levels are still at 2003 b/t we needed to hold on to a W2K3 DC for an old Exchange 2003 instance. That restriction is no longer in place. Should I replace that W2K3 DC first before adding the RODC, and up the domain and forest functional levels to 2008?

Our other DC's are 2008 already. The RODC will not rely on the W2K3 DC, but on one, and only one, of the W2K8 DC's. I already have this particular writable DC in its own site, so I can setup the proper site link with just the one DC and the RODC.

I also have questions about DNS, but will withhold my questions to a single file formation.

RhoSysAdminAuthor Commented:
Follow-up question: it looks like the cloud based servers just need to be able to do secure LDAP queries to our global catalog - i.e. the RODC we setup in the perimeter network. Does this change anyone's opinion on what to setup?
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

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

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