This feature has been implemented in version 2025.3.17.0
Implemented

Publish RDM through Intune

1 vote

avatar

How can we disable it by-default and grey‑out the following option and deploy the configuration to end users via Intune?
Path: Settings > Entry Types > Credential Management > CyberArk > “Keep authenticated sessions alive”

All Comments (4)

avatar

Hello,

I believe you can push a default configuration through the intune installation package (.intunewin) with the RemoteDesktopManager.cfg file which contains your configuration. You can export your configuration through File -> Settings -> Export settings.

However, the users will still be able to go in their setting and enable "Keep authenticated sessions alive".

What we could do is create a group policy that you could activate for your users. When that policy is active we would disable the "Keep authenticated sessions alive" setting completely so it can never be used.

Would you prefer we do that?

Best Regards,

Michaël Beaudin

avatar

Thanks @Michael Beaudin,

Yes, we tried the feature "File -> Settings -> Export settings" at first but still user is able to modify the setting as you said. So, wanted to explore the other to disable it completely through GPO. How can we achieve it, do we have any corresponding registry key to disable that setting. Appreciate your help if you could share any instructions to disable it via GPO.

Regards,
Harish

avatar

Hello,

We will create a ticket on our end to add a GPO specifically for your case and get back to you once it is done.

Here is our documentation about our already existing policies : https://docs.devolutions.net/rdm/kb/how-to-articles/group-policies/

Best Regards,

Michaël Beaudin

avatar

Hello,

We've added the GPO CyberArkKeepAuthenticatedSessionsAlive. It will have the following settings:
0 = GPO inactive
1 = Enforce the "Keep authenticated sessions alive" to always be active
2 = Enforce the "Keep authenticated sessions alive" to always be disabled

You can expect this GPO to reach live with the upcoming 2025.3.17 version.

Regards,

Jafran Majeau

This feature has been implemented in version 2025.3.17.0