I just read this article: https://borncity.com/win/2022/11/15/windows-server-2012-r2-sophos-user-authentication-using-heartbeat-disabled-on-rds-servers/
saying a customer found out tha his Windows 2012 R2 Servers no longer send their heartbeat status to the XG/S Firewall after Sophos disabled that feature.
Can Sophos confirm that is true?
I cannot report this from our side - our 2012 R2 machines have heartbeat - but the reason may be that the relevant updates have not yet been pushed by central in our region.
Looking forward to your answers on that thing.
I want to add: the blog post is a bit mixed up - writing of SATC, User authentication and heartbeat things. SATC has been replaced by Intercept-X - I know.
I can confirm, that SATC (included in endpoint) is not supported in 2012R2 any longer. We had a long case with Sophos / GES for this problem. Sophos stopped support for this with the lates Core agent and it will not be supported again. If you want to use user authentication on 2012R2 RDS server “Per-connection authentication” (using old direct proxy technology) is the only solution.
Thanks for confirming that situation. I hope it may help others using 2012 R2 RDS Servers with user authentication against the firewall. Kevin Kingston can you please tell the Intercept-X Version (probably Core Agent) that stopped supporting that feature for Server 2012 R2?
As per my first message, while it was available for a period of time for Server customers who had enrolled in our 'New Server Protection Features' Early Access Beta program, the SATC functionality was never made generally available to customers on Windows Server 2012 R2. It was officially released and supported for Windows Server 2016 and above when our 2022.2 Core Agent was released.