We have found recently that deactivating the Client TLS 1.0 for a Server 2016 OS, prevents Automox from being able to download the payload associated with the required software policy, the policy itself still runs, but it fails to connect and download the payload.

we still have TLS 1.1 and 1.2 enabled, but the payload will not download.

the scans and patching still seems to function like normal.

as soon as we re enable the TLS Client 1.0,  we can then download the payloads again and have automox install software.

in the exact same ENV, instead using Server 2019, and just TLS 1.2 enabled, with the same version of automox agent, 1.42.13, and the same required software deployment, it works without issue.

so it seems like Server 2016 is missing something, that Server 2019 has natively.

has anyone seen anything like this, and is there a fix besides upgrading to 2019 ?