We recently enabled drag and drop on our horizon desktops via DEM smart policies. On the initial connection the drag and drop functionality works as expected. However, after a disconnect/reconnect drag and drop ceases to function. I've tried using a triggered task to perform a user environment refresh, with Horizon Smart Policies enabled, that triggers on session reconnected but it didn't fix the issue. The DEM logs show the following on reconnect after enabling the triggered task:
2022-10-05 14:18:27.515 [INFO ] Performing user environment settings refresh [IFP#d8fcc774-15c36fc>>]
2022-10-05 14:18:27.588 [INFO ] Applied Horizon Smart Policies settings:
2022-10-05 14:18:27.588 [INFO ] Drag and drop is allowed from client to agent
2022-10-05 14:18:27.588 [INFO ] Client drive redirection is disabled
2022-10-05 14:18:27.588 [INFO ] Clipboard redirection is disabled
2022-10-05 14:18:27.588 [INFO ] Web and Chrome file transfer is disabled
2022-10-05 14:18:27.597 [INFO ] Done (81 ms) [<<IFP#d8fcc774-15c36fc]
Any thoughts on why drag and drop does not function after a reconnect?
- The DEM log shows that DnD only enabled the direction from Client to Agent, so please make sure your testing is just based on this direction. Also It shows the CDR is disabled, that means you can't do DnD for file and folder which replies on CDR feature. You can try to do DnD on string, picture.
- Are you using Horizon Windows Client? What's the client and agent version for the problem?
- From the description, "On the initial connection", DND can work fine. Have you tried to restart your remote desktop and what's the behavior then?
We are testing via the Client to Agent. We have the CDR feature installed on the parent image but are using Smart Policies to disable just the drive redirection. The DND functions correctly on the initial logon with drive redirection disabled via the Smart Policies, just not on reconnects. I'm not sure what you mean by string or picture, as that is controlled via the clipboard redirection Smart Policy in DEM.
We are using the Horizon Client, version 2111.1. The Agent is currently 2103.
Restarting the Horizon client does not fix the issue, nor does restarting the desktop its running on.