0% found this document useful (0 votes)
76 views5 pages

Deploy A Read Only Domain Controller

Read only domain controllers (RODCs) were introduced to address security risks of placing domain controllers in branch offices. RODCs host read-only copies of Active Directory and SYSVOL, limiting damage if compromised. While RODCs provide security advantages, not all applications are compatible so testing is required before deployment. The article then describes installing an RODC using either Server Manager, which involves selecting the RODC option during promotion, or PowerShell, using the Install-ADDSDomainController cmdlet and specifying the ReadOnlyReplica parameter as true.

Uploaded by

TháiFletcher
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
76 views5 pages

Deploy A Read Only Domain Controller

Read only domain controllers (RODCs) were introduced to address security risks of placing domain controllers in branch offices. RODCs host read-only copies of Active Directory and SYSVOL, limiting damage if compromised. While RODCs provide security advantages, not all applications are compatible so testing is required before deployment. The article then describes installing an RODC using either Server Manager, which involves selecting the RODC option during promotion, or PowerShell, using the Install-ADDSDomainController cmdlet and specifying the ReadOnlyReplica parameter as true.

Uploaded by

TháiFletcher
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

Deploy a Read Only Domain Controller

Read Only Domain Controllers were introduced in Windows


Server 2008 as a response to the security risks of placing DCs
in branch office locations that lack the physical security of
centralized datacenters. Hosting read-only copies of the Active
Directory (AD) database partitions, SYSVOL folder, and
optionally the DNS database, RODCs can limit the damage
caused if the server is compromised. The AD database is
replicated from a writeable DC to each RODC, but not vice
versa, so even if an RODC is hacked, global changes cannot be
made to Active Directory.

RODCs communicate with a writeable DC for user


authentication because they don’t store account credentials
locally, although you can elect accounts to have their
passwords cached on a RODC for fast logons, which is useful
for regular users of a branch office network. To protect
privileged AD accounts, there’s also a deny list to prevent local
password caching. Administrator role separation also gives
local administrator access to an RODC but without any access
to AD.

While RODCs provide several security advantages over


writeable DCs, it’s worth bearing in mind that not all
applications are compatible with RODCs. So it’s important to
check that server applications are compatible and that you
test thoroughly before deploying RODCs in a production
environment.

Install an RODC

An RODC can’t be the first domain controller in a domain, so


you must have at least one writeable DC online. The good
news is that the installation process doesn’t differ much from
installing a writeable DC, for which you can find the
instructions in Add Windows Server 2012 as a Domain
Controller on the Petri IT Knowledgebase.

I’m not going to outline the entire process here again, but just
the differences when choosing to install an RODC.

Using Server Manager

After having installed the AD Directory Services bits, when


promoting the server to a DC, make sure you check Read only
domain controller (RODC) on the Domain Controller
Options screen before proceeding.
Once you’ve opted to install an RODC, you get an additional page with
RODC-specific settings. On the RODC Options screen, you have the
chance to nominate an account for local administrator access to this
RODC only, something you can’t achieve with a writeable DC, and
decide which accounts can have their credentials cached locally for
fast logins. There’s a default list of accounts already added to the deny
list, but you can add your own. Denies override allows.

hen you continue to install the DC as normal.

Using PowerShell

We need to set a few parameters before starting, including the


NetBIOS name and fully qualified domain name (FQDN) for the
existing AD domain, and the NTDS and SYSVOL paths.
PowerShell
1 $domain = 'AD'
2 $domainName = 'ad.contoso.com'
3 $NTDSpath = 'C:\Windows\NTDS'
4 $SYSVOLpath = 'C:\Windows\SYSVOL'

We’ll use the Install-WindowsFeature cmdlet to install the ADDS bits along


with the AD management tools. Finally, the Install-
ADDSDomainController cmdlet is used to install the RODC. Note
the ReadOnlyReplica parameter is set to true, which designates this DC as a
RODC. You’ll be prompted to enter the credentials for an account that has
permission to add a DC to the domain, and to provide and confirm a Directory
Services Restore Mode (DSRM) password.

PowerShell
Install-WindowsFeature –Name AD-Domain-Services -includemanagementtools
 
1
Install-ADDSDomainController -Credential (Get-Credential) -CriticalReplicationOnly:$false
2
-DomainName $domainName -InstallDNS:$true -LogPath $NTDSpath -DatabasePath $NTDSpath
3
-ReadOnlyReplica:$true -SiteName "Default-First-Site-Name" -SYSVOLPath $SYSVOLpath -Force:
$true

Optionally you can add the -AllowPasswordReplicationAccountName and -


DenyPasswordReplicationAccountName parameters to specify accounts to be
added to the allow and deny password caching policy lists. Also the -
DelegatedAdministratorAccountName parameter allows you to specify an
account that will be delegated local administrator rights to this RODC only.

Running the Install-ADDSDomainController cmdlet

PowerShell
-DenyPasswordReplicationAccountName @("BUILTIN\Administrators", "BUILTIN\Server Operators",
1 "BUILTIN\Backup Operators", "BUILTIN\Account Operators", "AD\Denied RODC Password Replication
Group")
If you exclude the -AllowPasswordReplicationAccountName and -
DenyPasswordReplicationAccountName parameters from the cmdlet, the
default settings will be used.

In this article, I explained the differences between RODCs and


DCs, and how to install an RODC using Server Manager and
Windows PowerShell.

You might also like