- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
08-20-2025 05:41 AM
We upgraded our PAM - Self Hosted environment to version 14.2 from v12.6. At v12.6 it was possible to map local drives via SecureConnect (Ad hoc) connections. After upgrading, it seems it no longer works. I tried adjusting the connection component parameter "AllowMappingLocalDrives" on the RPD Connection component being used, on the SecureConnect Platform. I confirmed that that is the correct Platform, as well as the correct connection component, as certain changes took effekt for the SecureConnect connections. It seems that the relevant mapping local drives parameters are being overridden, as the RDP file shows "redirectdrives:i:0" and "drivestoredirect:s:", even though I set the AllowMappingLocalDrives parameter exactly as on a different platform for managed accounts, where it works as intended.
Same PSM Server for both Platforms as well.
Therefore my question (see title)
09-04-2025 12:58 AM
Regarding the Issue,
I opened a Case an CyberArk support answered with the following:
"Regarding this issue,
there is a known bug in 14.2 where local drive mapping does not work when connecting to a target via ad-hoc connection from the regular account view.
It should work as normal with Secure Connect from the account view (classic UI), so please try that."
https://community.cyberark.com/s/article/KI00024460
So it seems there is a bug, but I can confirm that the workaround worked for us.
08-20-2025 06:19 PM
Hi @Steffen Jerke
Can you please check whether 'Do not allow drive redirection' policy is set to Enabled on PSM server through GPO? Please disable it
Also refer to this KB https://community.cyberark.com/s/article/PSM-Unable-to-map-drives-in-PSM-RDP-session
Hope it helps!
08-20-2025 09:47 PM
Hello @Steffen Jerke
I have experienced the similar issue with 14.2 version. As per my understanding ad-hoc connections do not use vaulted credentials and sessions are also not managed, so few of PSM features are not supported and drive mapping is also one of those features. Drive mapping is available when sessions are initiated via PVWA vaulted creds so that session policies and features can be fully featured.
08-20-2025 09:47 PM
Hello @Steffen Jerke
I have experienced the similar issue with 14.2 version. As per my understanding ad-hoc connections do not use vaulted credentials and sessions are also not managed, so few of PSM features are not supported and drive mapping is also one of those features. Drive mapping is available when sessions are initiated via PVWA vaulted creds so that session policies and features can be fully featured.
08-20-2025 11:53 PM
Hi @Malhar Vora
"Do not allow drive redirection" policy is disabled. I made sure that the same PSM is being used when connecting via SecureConnect (drive mapping not working) and when using a "normal" connection with managed credentials (drive mapping working). That should exclude all errors related to GPO's or settings on that specific PSM.
08-21-2025 03:06 AM
Hi @Steffen Jerke
So you have already tried adding AllowMappingLocalDrives at the SecureConnect platform policy level and set to Yes
Please compare the RDP file from a working connection to the one from a non working SecureConnect connection and check for any other parameters that are present in one but not the other, or any values that are different. This can point you to the exact setting that is causing the override.
Also try creating a new SecureConnect platform policy and add AllowMappingLocalDrives parameter.
Hope it helps !
09-04-2025 12:58 AM
Regarding the Issue,
I opened a Case an CyberArk support answered with the following:
"Regarding this issue,
there is a known bug in 14.2 where local drive mapping does not work when connecting to a target via ad-hoc connection from the regular account view.
It should work as normal with Secure Connect from the account view (classic UI), so please try that."
https://community.cyberark.com/s/article/KI00024460
So it seems there is a bug, but I can confirm that the workaround worked for us.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

