feature parity with https://ideas.patchmypc.com/ideas/PATCHMYPC-I-6099

Cross-Platform Remote Helpdesk Right-Click Actions

Summary

I would like to suggest a cross-platform right-click tools / remote helpdesk action framework for Patch My PC Advanced Insights, ConfigMgr, and Intune.

The idea is to make PMPC a central daily helpdesk workspace where admins can:

• View device, user, update, and software context

• Launch remote support tools

• Trigger Intune or ConfigMgr actions

• Run approved scripts or remediations

• Open native consoles or admin portals

• Use custom customer-defined actions

• Enforce RBAC, approvals, and auditing

Ideally this would be delivered through a single Microsoft Edge extension for Windows and macOS, optionally backed by a native helper / native messaging host. The extension would expose different actions depending on:

• Admin workstation OS

• Target device OS

• Installed local tools

• Available backends

• User permissions

• Customer configuration

• Risk level of the action

This would extend the existing PMPC pattern of contextual “View in Advanced Insights” integration and turn it into a broader helpdesk action framework.

Core Concept

PMPC could provide a context-aware right-click menu on:

• Devices

• Users

• Groups

• ConfigMgr collections

• Updates

• Software objects

The menu should be:

• Object-aware — device, user, group, collection, update, software

• OS-aware — Windows actions on Windows admin devices, macOS actions on Mac admin devices

• Capability-aware — only show actions if required tools/backends are available

• Role-aware — hide or approval-gate sensitive actions

• Audited — record who ran what, against which object, when, and with what result

• Extensible — allow customers to define approved custom actions

Suggested Menu Structure

PMPC Remote Helpdesk Actions├── Device├── User├── Group / Collection├── Update / Software├── Privileges / Elevation├── Wrapper UX└── Custom Actions

1. Device Actions

Open / Context

Device└── Open / Context ├── Open in Advanced Insights ├── Open in Intune Admin Center ├── Open in ConfigMgr Console ├── Open in Windows Admin Center ├── Open Company Portal │ ├── Windows Company Portal │ └── macOS Company Portal └── Open App Store / Store ├── Microsoft Store / Company apps ├── Mac App Store └── Safari Extensions``

This would allow admins to jump directly from PMPC context to the correct management or user-facing app experience.

Remote Support

Device└── Remote Support ├── Windows │ ├── Remote Desktop / RDP │ ├── Remote Help │ ├── Quick Assist │ ├── ConfigMgr Remote Control │ └── Event Viewer remote connect └── macOS ├── Screen Sharing ├── Remote Management / Apple Remote Desktop ├── Remote Login / SSH └── Remote Help for macOS, if deployed

This should support both native Microsoft tools and platform-native macOS support paths.

Remote Actions

Device└── Remote Actions ├── Intune │ ├── Sync device │ ├── Restart device │ ├── Collect diagnostics │ ├── Rename device │ ├── Defender quick scan │ ├── Defender full scan │ ├── Retire / Delete / Wipe │ ├── Autopilot Reset │ └── Fresh Start ├── ConfigMgr │ ├── Trigger client action │ ├── Machine policy retrieval │ ├── User policy retrieval │ ├── Hardware inventory │ ├── Software inventory │ ├── Software updates scan │ ├── Application deployment evaluation │ ├── Compliance evaluation │ ├── Repair ConfigMgr client │ ├── Install ConfigMgr client │ └── Uninstall ConfigMgr client ├── Remote Command / Terminal │ ├── Open remote PowerShell session │ ├── Run remote PowerShell command │ ├── Run remote PowerShell script │ ├── Open remote CMD / WinRS shell │ ├── Run JEA delegated admin task │ ├── Open SSH session to Mac │ ├── Run SSH command on Mac │ └── Run Intune shell script on Mac └── Scheduled Task Runner ├── Query remote tasks ├── Run remote task ├── Create temporary remote task ├── End remote task └── Delete temporary remote task

This would make PMPC useful not only for visibility, but also for controlled operational remediation.

Remote-Capable Admin Consoles

PMPC should distinguish between:

1. Tools that require a remote-control session

2. Tools that can natively target another computer

Device└── Remote-Capable Admin Consoles ├── Event Viewer → selected remote computer ├── Services → selected remote computer ├── Computer Management → selected remote computer ├── Task Scheduler → selected remote computer ├── Remote Registry ├── Saved custom .msc console └── Windows Admin Center handoff

Example launch templates:

eventvwr.mscservices.msc /computer={{DeviceName}}compmgmt.msc /computer={{DeviceName}}

For saved consoles, PMPC could allow customer-defined MMC templates, while treating /computer= behavior as snap-in-specific rather than universal.

View / Diagnose

Device└── View / Diagnose ├── Device state │ ├── Entra join / hybrid join status │ ├── Intune enrollment state │ ├── ConfigMgr client state │ ├── Primary user │ └── Primary devices ├── Security / readiness │ ├── BitLocker status │ ├── FileVault status │ ├── TPM state │ ├── Secure Boot state │ ├── BIOS / UEFI mode │ ├── Windows 11 readiness │ └── MBR2GPT readiness ├── Operational health │ ├── Last 24h errors │ ├── Service crash events │ ├── Windows Update events │ ├── MDM / Intune events │ ├── Installed software │ ├── Missing / failed updates │ ├── Services │ ├── Processes │ ├── Drivers │ ├── Scheduled tasks │ └── Collected diagnostics └── Network / user-impact ├── IP / DNS / proxy ├── Wi-Fi / 802.1X details ├── Mapped drives / mounted volumes ├── Shares ├── Printers ├── Print queue └── Backup / Time Machine status

Many of these should be PMPC wrapper grids rather than legacy console launches.

Security / Recovery

Device└── Security / Recovery ├── BitLocker │ ├── View recovery key │ ├── Rotate recovery key │ ├── Suspend protection │ └── Resume protection ├── FileVault │ ├── View recovery key │ └── Rotate recovery key ├── LAPS │ ├── View Windows LAPS password │ ├── Rotate Windows LAPS password │ ├── View macOS LAPS password │ └── Rotate macOS LAPS password ├── TPM / Secure Boot / UEFI │ ├── View TPM state │ ├── Clear TPM │ └── View firmware readiness └── MBR2GPT ├── Validate MBR2GPT ├── Convert MBR to GPT └── Show prerequisites / warnings

These should be tightly controlled with RBAC, approvals, justification prompts, and full audit trails.

Network / Printer Fixes

Device└── Network / Printer Fixes ├── Browse device by hostname ├── Open admin share ├── Connect to SMB share ├── Disconnect / eject share ├── Add / remove printer ├── Set default printer ├── View print queue └── Reset print spooler

Printer, SMB share, and spooler actions are common helpdesk workflows and would be very useful from the same device context.

2. User Actions

User├── Account / Identity│ ├── View account details│ ├── Reset password│ ├── Unlock account│ ├── Enable account│ ├── Disable account│ ├── Open ADUC for user│ └── Open user in Entra / M365 admin center├── Access / Groups│ ├── View current groups│ ├── Add user to AD / Entra group│ ├── Remove user from AD / Entra group│ ├── Add user to ConfigMgr collection│ └── Open access request / approval workflow├── Licensing│ ├── View assigned licenses│ ├── View assignment source│ ├── View service plan state│ ├── Open in Microsoft 365 admin center│ ├── Assign license│ └── Remove license└── Devices ├── View assigned devices ├── View primary devices ├── Open selected device └── Open selected device in Advanced Insights

For identity and access actions, PMPC should use safe search/select pickers, confirmations, approvals, and audit logging instead of free-text input wherever possible.

3. Group / Collection Actions

Group / Collection├── Membership│ ├── View members│ ├── Add member│ └── Remove member├── Targeting│ ├── Add device to ConfigMgr collection│ ├── Add user to ConfigMgr collection│ ├── Open collection in ConfigMgr│ └── Open collection in Advanced Insights└── Licensing ├── View group-based license assignment ├── Open group licensing in M365 admin center ├── Assign group license └── Remove group license

Collection and group changes should be approval-friendly and fully audited.

4. Update / Software Actions

Update / Software├── View│ ├── Compliance│ ├── Missing updates│ ├── Failed updates│ ├── Affected devices│ ├── Vulnerable software│ └── Unsupported software└── Actions ├── Install / retry deployment ├── Validate deployment ├── Open Windows Update ├── Open macOS Software Update ├── Install all macOS updates ├── Download full macOS installer └── Install Rosetta 2

This fits naturally with PMPC’s existing focus on software, update, vulnerability, and compliance reporting.

5. Privileges / Elevation

Privileges / Elevation├── Windows│ ├── Run with Elevated Access│ ├── Request Elevated Access│ ├── Approve / deny elevation│ └── Run JEA delegated admin task└── macOS ├── View / rotate local admin password ├── Promote user to administrator └── Temporary admin session

Windows workflows could integrate with Endpoint Privilege Management where available.

For macOS, these should probably remain customer-configurable unless backed by Intune macOS LAPS or a third-party elevation tool.

6. Required Wrapper UX

Wrapper UX├── Search / select picker├── Interactive grid / list├── Approval / confirmation dialog├── Dry run / preview├── Capability check├── Role check└── Audit trail

This is one of the most important parts of the request.

PMPC should not just launch arbitrary commands. Risky or complex actions should be wrapped with:

• Preview

• Confirmation

• Justification

• Approval workflow

• RBAC enforcement

• Dry-run where possible

• Full audit history

This is especially important for actions such as:

• Restart

• Wipe

• Retire/delete

• BitLocker/FileVault recovery key access

• LAPS password viewing

• LAPS rotation

• MBR2GPT conversion

• Account disablement

• License assignment/removal

• Elevation approval

7. Custom Actions

Custom Actions├── Run custom Graph action├── Run custom PowerShell action├── Run custom shell / SSH action├── Run custom Intune remediation├── Run custom runbook├── Open CMDB / ITSM / approval workflow├── Run saved MMC launch template├── Run PsExec / PsTools template├── Run Remote Registry template└── Run customer-specific tool/workflow

Custom actions are important because every organization has different tooling, policies, and risk tolerance.

A template model could allow customers to define:

• Display name

• Object type

• Required role

• Required OS

• Required local tool

• Backend type

• Command or URL template

• Confirmation requirements

• Approval requirement

• Audit classification

• Risk level

Suggested Architecture

PMPC Remote Helpdesk Framework├── Microsoft Edge extension├── Optional native helper / native messaging host├── Action catalog├── Launch-template engine├── PMPC wrapper grids├── Intune / Graph connector├── ConfigMgr connector├── Remote PowerShell / WinRM support├── SSH support for macOS/Linux├── Remote-capable MMC launchers├── Remote support tool launchers├── RBAC engine├── Approval workflow├── Audit trail└── Customer-extensible custom actions

Final Summary

In short, I would love to see PMPC evolve this into a context-aware remote helpdesk action framework, not just a list of shortcuts.

The ideal outcome would be:

One Edge extension+ optional native helper+ action / launch-template engine+ PMPC wrapper grids+ Intune / ConfigMgr / Graph actions+ remote PowerShell / SSH support+ remote-capable MMC support+ remote-support tool launchers+ RBAC / approval / audit+ customer-extensible actions

This would make PMPC much more useful as a daily helpdesk workspace and would reduce the need for admins to constantly jump between:

• Advanced Insights

• Intune Admin Center

• ConfigMgr Console

• Microsoft 365 Admin Center

• Entra Admin Center

• Windows Admin Center

• Native MMC consoles

• Remote support tools

• PowerShell scripts

• SSH tools

• ITSM/CMDB systems

• Third-party utilities

Overall, this could turn PMPC into a central operational console for endpoint support, remediation, and compliance-driven helpdesk work.