Safeguard - Error message after leaving a remoteapp

Dear Community,

I am facing the following problem:

 When successful remote session is finished/closed  and "Check-in" is clicked button by user in SPP, RDC error window pops up intermittently:

Perhaps someone has encountered a similar problem? What could be the reason?

Virtuall Appliance Safeguard 7.5

Jump-Host: Windows Server 2019 Datacenter

Thank you in advance!

Best Regards

Arif Mamedzade

Top Replies

Parents
  • If the RDP window is minimized and the user did not sign out from target server and then clicks the check-in then the error would be expected
    if SPP Access Request Policy has the option for Close Expired Sessions enabled, then that means it would disconnect the RDP session when the access request is checked-in or expired

    SPP does not actually perform a sign out on behalf of the user from the target machine and therefore the user should log out from target server then perform a check-in of access request when finished.

    Thanks!

  • Hello  ,

    thank you for your reply and Instructions.

    Unfortunately, enabling and disabling the "Close Expired Sessions" parameter in Entitlements settings did not solve this problem.
    This error occurs only when creating an RPD-Application session, namely after the user completes it (check-in).

    This problem does not affect the performance of the session itself, but will occasionally make end-users nervous.

    Perhaps there are settings that should be adjusted or disabled on Jump-Host Asset?

  • Do you already have this policy disabled?

    Disable the Use advanced RemoteFX graphics for RemoteApp group policy on the RDP server.

    The policy is available at Computer Configuration > Policies > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Remote Session Environment > Use advanced RemoteFX graphics for RemoteApp.

    Thanks!

Reply
  • Do you already have this policy disabled?

    Disable the Use advanced RemoteFX graphics for RemoteApp group policy on the RDP server.

    The policy is available at Computer Configuration > Policies > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Remote Session Environment > Use advanced RemoteFX graphics for RemoteApp.

    Thanks!

Children
  • Hello  ,

    thank you for this instruction, but unfortunately, deactivating this policy in Jump-Host settings didn't bring any results.
    Is there anything else that can cause this error?

    Still recieving that error message after clicking on Check-in button.

    Best Regards

    Arif Mamedzade

  • Do you have multiple RDP session per user enabled? For example if multiple users are requesting the same RemoteApp with the same user on the RDP host, you can try allowing multiple sessions per user to avoid conflicting sessions.

    for example:

    1. Start Registry Editor

    2. Go to the following registry key:
    HKEY LOCAL MACHINE\System\CurrentControlSet\Control\TerminalServer

    3. If the fSingleSessionPerUser value doesn't exist, create a new DWORD value named fSingleSessionPerUser

    4. Open the fSingleSessionPerUser value. The possible values for this setting are as follows:

    0x0
    Allow multiple sessions per user

    0xl
    Force each user to a single session

    5. Enter the new setting, and then click OK.

  • Hello  ,

    thank you for your support.

    This setting has been changed to value "0" - did not help to achieve complete elimination of the error. But I have good news: after looking around in the gpedit.msc settings and changing some parameters and getting the following situation:

    Computer Configuration > Policies > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host:

    1. Licensing - Remote Desktop License Mode - "Active" - "per device"
    2. Session-Limits - Time Limit for disconnected Sessions - "Active" - Close disconnected Sessions - "1 Minute"
    3. Use advanced RemoteFX graphics for RemoteApp - "Deactived"
    4. RDPTransport Protocol - "Active" - "Use only TCP"

    Thanks to these modified settings I was able to achieve the elimination of the error. Slight smile