SSO parallels VDI

we have parallels RAS that allow us to login to VDIs. I have setup SSO on parallels it allows me to log in with my user name and password then once i select the vdi it tells me i have to be part of RDP group. I got in touch with Parallels and they suggested that iuninstall sophos endpoint and it worked. they sent me what to exclude, i did apply the exclusion and made sure that the newly  created vdis get the policy yet it is still not working. The other weird behavior is that when i uninstall endpoint reinstall it again single sign on remains working. I tried to turn off all the settings on the endpoint to determine what is blocking the sso it still doesn't allow me to log in. I have always to uninstall sophos to make it work. How can i determine what is blocking the sso? any tools or cmd to check what is happening in the background? why when uninstalling the endpoint and reinstalling it, it works? 

Parents
  • Hard to say from that but your comment:

    The other weird behavior is that when i uninstall endpoint reinstall it again single sign on remains working

    ...is perhaps the most significant. 

    I assume when you re-install and it continues working, is this until the first reboot after re-installing?

    I just wonder if this is due to the injection of a Sophos module into one or more processes.  This only happens on process creation so if the "processes of interest" are already running, then until the reboot they wouldn't get the module.

    As a test, if you disable Tamper on the computer and rename:

    C:\Program Files\Sophos\AutoUpdate\SophosLaunchUpdate.exe to C:\Program Files\Sophos\AutoUpdate\SophosLaunchUpdate.off 
    This will just prevent updates and the software repairing itself temporarily so rename back one done.

    Then rename:
    C:\windows\system32\hmpalert.dll to C:\windows\system32\hmpalert.dll.off
    C:\windows\syswow64\hmpalert.dll to C:\windows\syswow64\hmpalert.dll.off

    That will prevent hmpalert.sys injecting those modules into processes as they start.  

    Does that help narrow it down to the hmpalert.dll module being loaded?

  • Well never thought of rebooting, sometimes you miss importatn steps.

    I did try to turn off the tamper protection to one of the VDIs and it worked but for other VDIs it did not this is driving me crazy.

    Ill try you solution.

Reply Children
No Data