Sophos Connect - OpenVPN service not available - Windows 10 LTSB (IoT)

Hi Sansor

Thank you for reaching out to the community. Please post the error message you are getting on Sophos Connect with snapshot?

Thanks 

Hi Bharat J

I hope it is ok, that they are in German.

Hi Sansor

May I know the total number of systems affected?

Thanks 

Hi Sansor

May I know the total number of systems affected?

Thanks 

Hi Bharat J

I testet it only on this one thin client. There are more thin clients, but they are identical, installed from the same image. So I think there will be the same issue.

The message appears 1 -2 second after clicking on the connection button. No other message or anything other information. I know, not a lot of information.

There is only one additional program installed beside Sophos Connect, Windows standard programs und HP standard tools for thin clients:

3CX-Client

The thin client serves as remote client.

Bharat J said:

May I know the total number of systems affected?

I my case - around 150 point-of-sale endpoints ^^

Yeayyy.

Could you please ensure, that this is documented somewhere? If you could specify the error message in Sophos Connect, this would be even better.

See: https://docs.sophos.com/nsg/sophos-firewall/18.5/Help/en-us/webhelp/onlinehelp/AdministratorHelp/VPN/RemoteAccessVPN/VPNSophosConnectClient/index.html#sophos-connect-client-compatibility-with-platforms 

Yes. This site doesn't mention missing support for LTSB/LTSC Versions. At least, I wasn't able to find them.

It's just saying "we support x86 versions of Windows 10 and 11" - this includes LTSC versions.
In fact Server Versions are not supported. 

The older 17.5 docs also mentions support for "everything after Windows 7 SP2": Sophos Connect client

The Connect Client troubleshooting page could also include a hint:

Troubleshoot event errors - Sophos Connect

General troubleshooting - Sophos Connect

Don't get me wrong - I am really happy to get an answer here instead of digging this through the support and investing several hours. Just please update the docs. 

For the note: IPSec does work fine - if we wouldn't have problems in the generation of scx files on the appliance :D