Advanced Insights Remote Control

PLEASE

+999 bump

We are packaging the Configuration Manager Remote Control Viewer with the Advanced Insights helper and would appreciate guidance on the supported registration method.

Our goal is one per-machine application deployed through Configuration Manager and potentially managed as a Patch My PC Custom App.

Files:

CmRcViewer.exe
RdpCoreSccm.dll
AdvInsRemoteControl.exe
00000409\CmRcViewerRes.dll

Installation directory:

C:\Program Files\Remote Control Viewer

The package would create Start Menu and Public Desktop shortcuts, an ARP entry, and configure:

HKLM\SOFTWARE\Wow6432Node\Microsoft\ConfigMgr10\AdminUI\Connection
Server = SCCM01.contoso.com

Because the Configuration Manager console may also use this value, uninstall would preserve it when the console is installed. Otherwise, it could remove only the Server value if it still matches our configured value.

The main issue is the cmrc handler. Your documentation says running AdvInsRemoteControl.exe creates:

HKCU\Software\Classes\cmrc

This mixes machine and user contexts:

• Files and ConfigMgr settings are per-machine

• cmrc registration is per-user

• ConfigMgr installs as SYSTEM

• No user may be logged on

• Shared workstations may have multiple users

We would prefer to avoid requiring a user session, reboot, sign-in cycle, GPO, scheduled task or Active Setup.

Could the exact cmrc registration instead be installed machine-wide under:

HKLM\SOFTWARE\Classes\cmrc

With this open command:

"C:\Program Files\Remote Control Viewer\AdvInsRemoteControl.exe" "%1"

This should expose the handler to all users through HKEY_CLASSES_ROOT and allow an MSI to install, repair and remove it.

Could you please confirm:

1. Is machine-wide cmrc registration under HKLM supported?

2. What is the complete expected registry structure?

3. Is the open command above correct?

4. Does AdvInsRemoteControl.exe perform initialization beyond creating the protocol registration?

5. Does it require other HKCU values, files or per-user configuration?

6. Would HKLM registration work for multiple standard users?

7. Would an existing HKCU registration override or conflict with HKLM?

8. Can a matching HKCU registration safely remain?

9. Is the registration format stable across Advanced Insights versions?

10. Are there supported options for silent registration, unregistration, repair or machine-wide registration?

11. Is running AdvInsRemoteControl.exe once per user the only supported method?

If HKLM is unsupported, Master Packager has an "Apply HKCU registries to all users" action that can apply an exported cmrc registration to existing and default profiles during SYSTEM installation. Would that be supported?

Other options considered:

• Active Setup, but this adds sign-in execution, version tracking and uninstall cleanup

• PSAppDeployToolkit user-session execution, but this only configures the user logged on during installation

Proposed workflow:

Master Packager MSI
→ Optional PSAppDeployToolkit wrapper
→ Master Packager Toolbox
→ Patch My PC Custom Apps
→ Publisher
→ Configuration Manager

The MSI would provide the ARP entry, Program Files installation, shortcuts, protocol registration, repair, upgrades and uninstall. PSADT would only be used for process closure, migration cleanup or logging.

Is this the recommended workflow for maintaining the package as a Custom App?

Our preferred solution should install silently as SYSTEM, require no user session, support all workstation users, and allow clean repair, upgrade and uninstall.

atleast maybe a article regarding how to properly deploy/custom package this? or a installer ;)

btw why is this exe so large? 160mb just for a helper without installer seems a little weird to me

https://github.com/conocidotech/sccm-rc-viewer

+999