Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 6 replies
  • Subscribers 28 subscribers
  • Views 501 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Heartbeat Authentication not working with Vmware Horizon connection to workstations

Markus Ottmann1

Hello community,

we are using VMware Horizon VDI to realize HomeOffice for our collegues mainly to virtual machines. We have configured Sophos Heartbeat to realize user based firewall rules. This works great for us from VDI machines and workstations locally, but not in some the special cases, when the user is logged on the workstation over VMware Horizon client.

I think it has something to do with the way the session was established:

logged on ...

... locally on workstation -> sessionname: console -> heartbeat works

... via rdp on workstation -> sessionname: rdp-tcp#5 -> heartbeat works

... via Horizon client on VDI machine -> sessionname: console -> heartbeat works

... via Horizon client von workstation -> sessionname: vmware-rds#3 -> no heartbeat! no user based firewall grips!

Does anyone have an idea?

Markus



This thread was automatically locked due to age.
Parents
  • 0

    If it is a terminal Server type of connection, this will not work. Heartbeat is a client based single auth. 

    If the workstation has multiple Accounts logged in, Heartbeat does not fetch it. 

    __________________________________________________________________________________________________________________

  • 0 in reply to LuCar Toni

    The workstations have Windows 10 installed and there is only one user logged in at the same time. I think Sophos Heartbeat cannot fetch the user, because the session is established by the Horizon Agent installed on the workstation.

Reply Children
Share Feedback
×

Submitted a Tech Support Case lately from the Support Portal?