HowToFixMe
Windows Pro Enterprise

Intune (device side) Active Directory replication error 1722 RPC: Fix

By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-30

⚡ At a glance
BrandIntune (device side)
FamilyWindows Pro Enterprise
CategoryMicrosoft
Guide typeProblem Fix
Skill levelIntermediate

What's happening on your Intune (device side)

You hit Active Directory replication error 1722 RPC on a Intune (device side) device in the Windows Pro Enterprise family. This sits in the most-reported issue list for Intune (device side) in 2026 across community forums and vendor support, meaning the recovery path is mostly known.

Fast triage (5 minutes)

  1. service restart: stop the resource cleanly for 60 seconds, then power on. About 30% of Intune (device side) "Active Directory replication error 1722 RPC" reports clear here.
  2. Check status: any indicator service health indicators, dashboard alerts, or display codes on the Intune (device side) unit right now? Note them: they decide which branch to take below.
  3. Check release notes: is this device on the latest service version / OS update from Intune (device side)? An advisory for "Active Directory replication error 1722 RPC" may already be published.
  4. Try a clean test: a known-good cable / network / account isolates the device from external causes.
  5. Capture the exact symptom string, vendor TAC will ask for it verbatim.

Step-by-step fix for Intune (device side) Active Directory replication error 1722 RPC

  1. Confirm scope. Is this only on the one device, or fleet-wide? If fleet-wide, treat as a release / config / network issue, not a hardware fault.
  2. Apply the safe fix first.

- On Intune (device side) for "Active Directory replication error 1722 RPC", that usually means: soft reset → service version update from the Intune (device side) official portal → re-pair the device with its management tool / app.

  1. Targeted diagnostics. Use the Intune (device side)-specific diagnostic mode (most Intune (device side) Windows Pro Enterprise devices have one). It surfaces the exact subsystem reporting the fault, which speeds up parts ordering or escalation.
  2. Controlled hard reset (only if soft fix fails). Back up settings + data first. Then tenant reset following the Intune (device side) user manual for your model. Re-enrol from scratch.
  3. Validate. Reproduce the original trigger to confirm the fix held.
  4. Document. Log what worked. If it returns, you've got a faster path next time.

Escalation path for Intune (device side)

Avoid recurrence

Frequently asked questions

How long should the recovery / setup take?

For most Intune (device side) Windows Pro Enterprise cases, allow 15-45 minutes the first time. Repeats are usually under 10 minutes once you know the menu path.

Will this exact procedure work on every Intune (device side) model?

The procedure reflects current Intune (device side) behaviour. Menu paths shift between service version generations; verify against the manual for your specific model + revision.

Is the procedure safe in production / live use?

Apply during a maintenance window where possible. Capture pre-change state. Intune (device side) doesn't usually publish rollback procedures, so make sure you can restore manually.

Does this affect my Intune (device side) support coverage?

Standard operation per the user manual + applying official service version updates does NOT void support coverage. Opening managed services, third-party repair, or unauthorised modifications can void support coverage, check before going further.

Related guides worth a look while you sort this one out:

References

Reference material, not professional advice. Validate with your vendor manual and follow local regulations.

What changed recently?

Fault diagnosis on a Intune device goes faster when you map the symptom to a recent change:

The answer narrows the root cause to a manageable subset.

Before you start

A few things to confirm so the Intune device fix goes cleanly:

Quick verification

Before you walk away from a Intune device fix, run through:

1. Reproduce the original trigger. does the issue reappear? 2. Check the device's status / health screen for any new alerts. 3. Confirm paired devices (app, hub, controller) reconnected. 4. Save / commit any configuration changes per the device's normal workflow. 5. Note the change in your maintenance log with date + service version version.

Escalation guide

For a Intune device, the right escalation depends on impact:

More frequently asked questions

What if the fix returns after a reboot?

Persistent fault returns mean either: a hardware fault (escalate), a configuration that's being overwritten by a sync source (check cloud profiles), or a regression in a recent service version update (rollback).

How long does this fix usually take?

Most users complete the steps in 20-45 minutes the first time, and 5-10 minutes on subsequent runs once the menu paths are familiar.

Will this void my support coverage?

Applying official service version updates and following the user manual will not affect support coverage. Opening managed services, jumping safety circuits, or using third-party parts can void support coverage in most jurisdictions.

Should I update service version first or last?

Update service version first if a release note specifically mentions your symptom. Otherwise, finish the troubleshooting flow first, then update; that way you can isolate whether the update or the underlying fix solved it.

Are there safer alternatives for non-technical users?

Yes, the manufacturer's self-service troubleshooter (HP Smart, LG ThinQ, Samsung Members, similar) usually walks through the same steps in a guided UI. Use that first if you're not comfortable with menu paths.

Field notes from real Windows Pro Enterprise incidents

When I work on Intune (device side) Active Directory replication error 1722 RPC: Fix the rhythm I lean on is the one I have built over years of these tickets. DISM and sfc in that order; doing it the other way wastes a reboot when the component store is the actual problem. Reliability Monitor is the most underused tool in Windows: open it once and you have the last 30 days of crash history without writing a single query. Whenever a Pro/Enterprise box behaves weirdly after a feature update, I check gpresult before I touch anything else, group policy is usually the culprit, not the OS.

Tools I actually reach for

For Intune (device side) Active Directory replication error 1722 RPC: Fix on Intune (device side) the cheapest signal I can land usually comes from DISM, then sfc /scannow, Windows Performance Recorder (WPR) when DISM cannot see the layer the fault sits in, and Event Viewer (eventvwr.msc) for the cases where neither of those answers cleanly. That ordering is not academic. It matches the layers the failure tends to surface through, so the cheap signal lands first and the heavier tooling only comes out when the simpler answer does not hold up under scrutiny.

Verification I run before I close the ticket

Before I mark Intune (device side) Active Directory replication error 1722 RPC: Fix resolved on a Intune (device side) unit, the verification loop below is what I actually run. Each step proves a different layer is green, and the order matters - the cheap checks gate the more expensive ones.

Get-WinEvent -FilterHashtable @{LogName='System'; Level=2; StartTime=(Get-Date).AddHours(-24)}

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

DISM /Online /Cleanup-Image /CheckHealth

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

sfc /scannow

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

Get-HotFix | Sort-Object -Property InstalledOn -Descending | Select-Object -First 10

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

gpresult /scope:computer /v

Only when every line above runs clean do I close the ticket and update the runbook with the timestamps.

Where I check first when the docs disagree

When two sources contradict each other on a Windows Pro Enterprise detail, the disambiguation order I lean on is stable. I usually start at support.microsoft.com for the ground-truth view on Windows Pro Enterprise. I usually start at docs.microsoft.com/windows-server for the ground-truth view on Windows Pro Enterprise. I usually start at techcommunity.microsoft.com/category/windows for the ground-truth view on Windows Pro Enterprise. Random blog posts and reseller wikis are signal, not ground truth, and I treat them as such until the references above either confirm or contradict the claim.

Pitfalls I have walked into on this exact path

The shortcuts that look smart on Intune (device side) Active Directory replication error 1722 RPC: Fix have a habit of biting back. The pitfalls below are the ones I have personally walked into on a Intune (device side) unit, not things I read about. DISM and sfc in that order; doing it the other way wastes a reboot when the component store is the actual problem. Whenever a Pro/Enterprise box behaves weirdly after a feature update, I check gpresult before I touch anything else. group policy is usually the culprit, not the OS. Reliability Monitor is the most underused tool in Windows, open it once and you have the last 30 days of crash history without writing a single query. When in doubt I revert to the slower path that the manual prescribes - the time I save by skipping it is always smaller than the time I spend cleaning up afterwards.

What I tell the next on-call

When I hand Intune (device side) Active Directory replication error 1722 RPC: Fix off to the next person on rotation, the three lines I leave in the runbook are these. First, the symptom signature for Intune (device side) on the Windows Pro Enterprise family - not a paraphrase, the exact string that surfaces. Second, the diagnostic that gave the highest signal in the least time. Third, the exact verification command whose green output justified closing the ticket. That trio is what turns a one-off fix into a runbook entry the next engineer can use without paging me at three in the morning.

I also add a one-line note on the cost of getting this wrong. For Intune (device side) Active Directory replication error 1722 RPC: Fix on a Intune (device side) unit, the cost is rarely the replacement part. It is the downtime, the second site visit, and the trust deficit you spend with whoever owns the asset when the fix does not hold. That framing keeps the next on-call from choosing the cheap-looking shortcut that ends up costing the most in elapsed hours and goodwill.