How to set up Windows LAPS modern on RDP / RDS
By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-30
| Brand | RDP / RDS |
|---|---|
| Family | Windows Pro Enterprise |
| Category | Microsoft |
| Guide type | How To |
| Skill level | Intermediate |
Why this matters
Set up windows laps modern on a RDP / RDS device is one of the highest-volume how-to searches for the Windows Pro Enterprise category. Most users find the menu path inconsistent across RDP / RDS model revisions, so this guide gives a generalised path plus model-specific notes.
Pre-requisites
- A RDP / RDS device that's powered on and on the latest stable service version / OS.
- The RDP / RDS companion app or management tool installed and signed in.
- 5-15 minutes uninterrupted.
Step-by-step
- Locate the setting. Open settings on your RDP / RDS device. For "set up Windows LAPS modern", the option lives under one of: General, Advanced, Connectivity, Accessibility, or a RDP / RDS-specific menu. Check the RDP / RDS user manual for your exact model if you can't find it.
- Toggle the feature on. Confirm the on-screen prompt.
- Configure sub-options. Most features have 2-3 sub-options (mode, schedule, paired device). Pick values that match your real-world usage pattern.
- Save / apply. Some RDP / RDS models auto-save, others require an explicit Done / Save tap.
- Test live. Trigger the feature in a real scenario to confirm the configuration is correct.
Tips that save time
- Pair this feature with a RDP / RDS automation / routine if the device supports it.
- If the feature relies on cloud sync, give it 1-2 minutes after enabling to propagate.
- For multi-user households / multi-admin teams, set per-user profiles so each user sees their preferred state.
Common gotchas
- Feature greyed out. usually service version too old. Update + retry.
- Feature works once then stops, battery saver / power saver mode is killing the RDP / RDS app process. Whitelist it.
- Feature works but with delay: usually cloud-sync latency; check internet speed and RDP / RDS service status.
Region / variant notes
Some RDP / RDS features are region-locked or only available on higher-tier SKUs. If your variant doesn't show "set up Windows LAPS modern" at all, check the RDP / RDS model spec sheet to confirm support.
Frequently asked questions
How long should the recovery / setup take?
For most RDP / RDS 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 RDP / RDS model?
The procedure reflects current RDP / RDS 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. RDP / RDS doesn't usually publish rollback procedures, so make sure you can restore manually.
Does this affect my RDP / RDS 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
- All Windows Pro Enterprise guides → /microsoft/section/windows_pro_enterprise.html
- All Microsoft guides → /microsoft/
Related fixes
Related guides worth a look while you sort this one out:
- How to set up RDS deployment Server 2025 on Microsoft LAPS
- How to set up Windows LAPS modern on Active Directory
- How to set up Windows LAPS modern on BitLocker (managed)
- How to set up Windows LAPS modern on Defender for Endpoint
- How to set up Windows LAPS modern on DFS
- How to set up Windows LAPS modern on DHCP
References
- RDP / RDS official support portal for your model.
- RDP / RDS community forum + Reddit threads.
- Vendor PSIRT / advisory page (where applicable).
Reference material, not professional advice. Validate with your vendor manual and follow local regulations.
Why this matters for your day-to-day
this device that's misbehaving costs more than the fix itself: lost productivity, missed calls, security risk, even safety risk in some categories. Treating the symptom quickly with a documented procedure is cheaper than letting it persist. The steps above are written to get you back to working in under an hour where possible, and to flag clearly when escalation is the right call.
Before you start
A few things to confirm so the unit fix goes cleanly:
- Latest service version downloaded if you're going to update.
- support coverage + support contract status checked. opening managed parts may void it.
- Backup of current configuration (where applicable) taken.
- Spare parts on hand if you anticipate replacement.
- Adequate workspace, lighting, and time, rushing causes regressions.
Quick verification
Before you walk away from this 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 this unit, the right escalation depends on impact:
- Cosmetic / minor: log a ticket via the How app or web portal. Response 1-3 business days.
- Mid-impact: phone support. Have your serial number ready.
- Critical (production down, safety issue): in-person dealer / TAC visit. Bring proof of purchase.
- Out of support coverage: third-party repair shop with manufacturer-certified technicians.
More frequently asked questions
Does this affect other devices on my network?
Generally no. The procedure is local to this device. Network-side changes (service version updates that affect TLS, SMB, or routing) are flagged explicitly in the steps.
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 often should I run preventive checks?
Quarterly for most consumer devices; monthly for production / commercial devices. Set a calendar reminder so the device stays healthy between issues.
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.
Field notes from real Windows Pro Enterprise incidents
When I work on set up Windows LAPS modern on RDP / RDS the rhythm I lean on is the one I have built over years of these tickets. 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. DISM and sfc in that order; doing it the other way wastes a reboot when the component store is the actual problem.
Tools I actually reach for
For set up Windows LAPS modern on RDP / RDS on RDP / RDS the cheapest signal I can land usually comes from Reliability Monitor (perfmon /rel), then gpresult /h gpresult.html, DISM when Reliability Monitor (perfmon /rel) cannot see the layer the fault sits in, and Process Monitor (procmon) 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 set up Windows LAPS modern on RDP / RDS resolved on a RDP / RDS 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.
gpresult /scope:computer /vIf 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 /CheckHealthIf 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-WinEvent -FilterHashtable @{LogName='System'; Level=2; StartTime=(Get-Date).AddHours(-24)}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 learn.microsoft.com/windows 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 set up Windows LAPS modern on RDP / RDS have a habit of biting back. The pitfalls below are the ones I have personally walked into on a RDP / RDS unit, not things I read about. 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. 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. 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 set up Windows LAPS modern on RDP / RDS off to the next person on rotation, the three lines I leave in the runbook are these. First, the symptom signature for RDP / RDS 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 set up Windows LAPS modern on RDP / RDS on a RDP / RDS 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.