How to Deploy a Read-Only Domain Controller (RODC) in Windows Server 2022

A Read-Only Domain Controller (RODC) is a special type of Active Directory Domain Controller designed primarily for branch offices and locations where physical security cannot be guaranteed. Unlike a traditional writable Domain Controller, an RODC maintains a read-only copy of the Active Directory database and receives directory updates through replication from writable Domain Controllers.

In this tutorial, we will deploy a Read-Only Domain Controller in an existing Windows Server 2022 Active Directory environment. We will configure a new server, install Active Directory Domain Services (AD DS), promote the server as an RODC, configure Password Replication Policy (PRP), and verify successful deployment.

Lab objective: Deploy RODC01 with IP address 192.168.248.140 in the existing vmorecloud.com Active Directory domain.

Lab Environment and Network Topology

Before starting the deployment, let’s review the existing infrastructure.

Our Active Directory domain is vmorecloud.com. We already have two writable Domain Controllers:

  • DC1: 192.168.248.135
  • DC2: 192.168.248.139

We will introduce a third server with the hostname RODC01 and IP address 192.168.248.140.

IP Address Configuration

Component Hostname IP Address Purpose
GatewayVMware Gateway192.168.248.2Network connectivity
Primary DCDC1192.168.248.135AD DS, DNS and FSMO roles
Additional DCDC2192.168.248.139Writable AD DS and DNS
Read-Only DCRODC01192.168.248.140Read-only Active Directory

RODC01 Network Configuration

Computer NameRODC01
Operating SystemWindows Server 2022
IP Address192.168.248.140
Subnet Mask255.255.255.0
Default Gateway192.168.248.2
Preferred DNS192.168.248.135
Alternate DNS192.168.248.139
Domainvmorecloud.com
Windows Server 2022 RODC topology showing DC1 at 192.168.248.135, DC2 at 192.168.248.139 and RODC01 at 192.168.248.140
Figure 1: Active Directory RODC lab topology.

2. What Is a Read-Only Domain Controller?

A Read-Only Domain Controller is a domain controller that hosts a read-only copy of the Active Directory database.

Traditional writable Domain Controllers allow administrators to create, modify and delete Active Directory objects. An RODC, however, does not accept ordinary directory changes locally.

Its main characteristics include:

  • Read-only Active Directory database.
  • Inbound replication of directory changes from writable DCs.
  • Password Replication Policy (PRP).
  • Credential caching for authorized users and computers.
  • Delegated administration.
  • Optional DNS Server and Global Catalog functionality.

Why Do We Need an RODC?

Imagine an organization with its headquarters in Islamabad and a branch office in Swabi.

The headquarters has writable Domain Controllers, but the branch office has limited physical security and fewer IT resources.

Deploying an RODC at the branch office provides local directory services while reducing the risk associated with storing a fully writable directory database at a less secure location.

3. Prerequisites for RODC Deployment

Before promoting the server, ensure the following requirements are satisfied:

  1. A functioning Active Directory domain already exists.
  2. At least one writable Domain Controller is available.
  3. DNS resolution is working correctly.
  4. The new server has a static IP address.
  5. The new server can communicate with existing Domain Controllers.
  6. The server is running a supported Windows Server edition.
  7. You have suitable credentials to promote a domain controller.
  8. The forest functional level meets the RODC requirements (Windows Server 2003 or higher).

4. Step 1: Configure the Network Settings

First, configure the static IP address on the new Windows Server.

Open:

Server Manager → Local Server → Ethernet → IPv4 Properties

Enter the network configuration shown in the table above.

You can also verify the configuration using PowerShell:

ipconfig /all
Windows Server 2022 IPv4 properties showing RODC01 static IP configuration 192.168.248.140
Figure 2: Configure the static IP address on RODC01.

5. Step 2: Rename the Server

Rename the new Windows Server to RODC01.

Open PowerShell as Administrator and execute:

Rename-Computer -NewName RODC01 -Restart

The server will restart automatically.

After restarting, verify the hostname:

hostname

Expected output:

RODC01

6. Step 3: Join the Existing Active Directory Domain

Before promoting the server, you can join it to the existing domain.

  1. Open Server Manager.
  2. Select Local Server.
  3. Click the current workgroup setting.
  4. Select Change.
  5. Choose Domain.
  6. Enter vmorecloud.com.
  7. Provide suitable domain credentials.
  8. Restart the server when prompted.

You can also use PowerShell:

Add-Computer -DomainName "vmorecloud.com" -Restart

After restarting, verify domain membership:

Get-CimInstance Win32_ComputerSystem |
Select-Object Name, Domain, PartOfDomain

Expected result:

Name         : RODC01
Domain       : vmorecloud.com
PartOfDomain : True
Windows Server successfully joined to vmorecloud.com domain
Figure 3: RODC01 successfully joined to the existing domain.

7. Step 4: Install Active Directory Domain Services

Now we will install the AD DS role on RODC01.

Using Server Manager

  1. Open Server Manager.
  2. Select Manage.
  3. Click Add Roles and Features.
  4. Select Role-based or feature-based installation.
  5. Select RODC01 as the destination server.
  6. Select Active Directory Domain Services.
  7. Add the required management tools.
  8. Click Next and install.

Using PowerShell

Alternatively, run:

Install-WindowsFeature AD-Domain-Services -IncludeManagementTools

Verify installation:

Get-WindowsFeature AD-Domain-Services

The installation state should show Installed.

Server Manager displaying successful installation of Active Directory Domain Services
Figure 4: Installing the Active Directory Domain Services role.

8. Step 5: Promote the Server as a Read-Only Domain Controller

This is the most important part of the deployment.

After installing AD DS, open Server Manager.

  1. Click the notification flag.
  2. Select Promote this server to a domain controller.
  3. The Active Directory Domain Services Configuration Wizard will open.

Deployment Configuration

Select:

Add a domain controller to an existing domain
Domain: vmorecloud.com

Provide the appropriate domain credentials.

AD DS Configuration Wizard showing Add a domain controller to an existing domain
Figure 5: Selecting the existing Active Directory domain.

Domain Controller Options

On the Domain Controller Options page, configure the following:

OptionConfiguration
DNS ServerOptional
Global CatalogRecommended for this lab
Read-only domain controller (RODC)Selected
DSRM PasswordSet a strong password
Important: Make sure you select the Read-only domain controller (RODC) checkbox. If you leave it unchecked, the server will be promoted as another writable domain controller.

DNS and Global Catalog services are optional choices depending on your infrastructure requirements. For a branch-office deployment, installing both can provide useful local directory and name-resolution services.

Windows Server Domain Controller Options with Read-only domain controller selected
Figure 6: Selecting the Read-only domain controller option.

9. Step 6: Configure Password Replication Policy

Password Replication Policy (PRP) is one of the most important features of an RODC.

Unlike writable Domain Controllers, an RODC does not automatically cache every user’s password.

The Password Replication Policy determines which users and computers are permitted to have their credentials cached on the RODC.

For example, we can allow branch-office users to cache their passwords while preventing privileged administrative accounts from being cached.

Suggested Password Replication Policy

Account or GroupPolicy
Branch Office UsersAllow
Branch Office ComputersAllow
Domain AdminsDeny
Enterprise AdminsDeny
Schema AdminsDeny

Configure PRP Through Active Directory Users and Computers

  1. Open Active Directory Users and Computers.
  2. Locate the Domain Controllers organizational unit.
  3. Open the properties of RODC01.
  4. Select the Password Replication Policy tab.
  5. Add the required users and groups to the appropriate lists.

Remember that an account being allowed by PRP does not mean its password has already been cached. The credential must be replicated or successfully cached through an authentication process.

RODC01 Password Replication Policy tab in Active Directory Users and Computers
Figure 7: Configuring Password Replication Policy.

10. Step 7: Configure Delegated Administration

One advantage of RODC is the ability to delegate local administrative responsibilities without granting the delegated administrator Domain Admin privileges.

During promotion, you can specify a user or group that will be allowed to administer RODC01.

For example:

vmorecloud\BranchITAdmin

This delegated account can manage the RODC locally without automatically receiving full domain administrative rights.

RODC Delegation Options page in Active Directory Domain Services Configuration Wizard
Figure 8: Configuring delegated RODC administration.

11. Step 8: Complete the RODC Promotion

After configuring the deployment options:

  1. Review Additional Options.
  2. Select the replication source Domain Controller.
  3. Review the database, log and SYSVOL paths.
  4. Run the prerequisites check.
  5. Review any warnings.
  6. Click Install.

The server will restart after successful promotion.

You now have an RODC in your existing Active Directory domain.

12. Step 9: Verify the RODC Deployment

After restarting, log in to RODC01 and open PowerShell.

Verify the Domain Controller

Get-ADDomainController -Identity RODC01 |
Format-List HostName,IPv4Address,IsReadOnly,IsGlobalCatalog

Expected output should include:

HostName        : RODC01.vmorecloud.com
IPv4Address     : 192.168.248.140
IsReadOnly      : True
IsGlobalCatalog : True

Verify Active Directory Replication

repadmin /showrepl RODC01

This displays the inbound replication status and replication partners.

Check Domain Controller Health

dcdiag /s:RODC01 /v

Verify DNS Resolution

If DNS is installed on RODC01, test:

nslookup vmorecloud.com 192.168.248.140

Verify RODC Properties

Get-ADDomainController -Filter * |
Select-Object HostName,IPv4Address,IsReadOnly
PowerShell verification of RODC01 showing IsReadOnly True and IP 192.168.248.140
Figure 9: Verifying successful RODC deployment.

13. Practical RODC Testing

To understand how an RODC behaves, perform the following experiments.

Experiment 1: Create a User on RODC01

Try creating a new user directly on RODC01 using Active Directory Users and Computers.

Expected result: You cannot write ordinary Active Directory changes directly to the RODC. Create the user on a writable DC instead.

Experiment 2: Create a User on DC1

On DC1 (192.168.248.135), create a test account:

Username: TestUser
Domain: vmorecloud.com

After replication, verify that the account appears in the directory when viewed through RODC01.

Experiment 3: Test Password Replication Policy

Configure a test user as allowed by the RODC’s Password Replication Policy.

Authenticate using that account against RODC01, then check whether the password has been cached.

repadmin /prp view RODC01 reveal

Examine the accounts whose passwords are permitted to be cached:

repadmin /prp view RODC01 allow

And accounts denied caching:

repadmin /prp view RODC01 deny

Experiment 4: Test Cached Credentials

Once an authorized user’s password has been cached, temporarily disconnect RODC01 from writable DCs and test authentication at the branch-office client.

An eligible user with cached credentials may still authenticate locally.

However, new password changes and other directory modifications require connectivity to a writable domain controller.

14. RODC vs. Writable Domain Controller

FeatureWritable DCRODC
Read Active Directory databaseYesYes
Write ordinary AD changes locallyYesNo
Accepts inbound replicationYesYes
Sends ordinary AD changes to replication partnersYesNo
Password Replication PolicyNo RODC PRPYes
Credential cachingNormal DC credential storageControlled by PRP
DNS ServerSupportedSupported
Global CatalogSupportedSupported
Delegated local administrationSupportedSpecial RODC delegation feature

15. Important AZ-802 Examination Concepts

For Microsoft AZ-802, pay special attention to these RODC-related topics:

  1. RODC deployment and prerequisites.
  2. Password Replication Policy.
  3. Credential caching and authentication.
  4. Delegated administration.
  5. RODC replication behaviour.
  6. DNS and Global Catalog configuration.
  7. RODC unavailability and recovery.
  8. Differences between writable DCs and RODCs.

Conclusion

In this practical lab, we deployed a Read-Only Domain Controller in an existing Windows Server 2022 Active Directory environment.

Our infrastructure now contains two writable Domain Controllers and one Read-Only Domain Controller:

The RODC provides read-only directory services, controlled credential caching and delegated administration capabilities. This makes it particularly useful for branch-office environments where physical security and administrative control are important considerations.

Further Reading

Microsoft Learn – Read-Only Domain Controllers (RODCs)

Leave a Reply

Your email address will not be published. Required fields are marked *