Sophos updating policy not set
For more information about user data and profiles, see How to Create User Data and Profiles Configuration Items in Configuration Manager.The update logs within the Sophos client give the following: "There was a problem while establishing a connection to the server. A windows API call returned error 1311" After lots of googling, we can find nothing relating to "error 1311". The primary update server (mgmt1) is configured the same on all machines through 1 Sophos policy. Why can the clients update successfully from mgmt1 but mgmt1 cannot connect to itself and update properly? windows error 1311 means ERROR_NO_LOGON_SERVERS or simply there are currently no logon servers available to service the logon request.Likely establishing connection is failing due to connectivity or local/domain policy or wrong credential or account lockout, hard to ascertain but good to check the (e.g.If this setting is False or No but the Enable user policy polling on clients is configured as True or Enable user policy on clients is configured as Yes, users will not receive user policies until the computer is connected to the intranet.
For more information about managing clients on the Internet, see the Planning for Internet-Based Client Management section in the Planning for Communications in Configuration Manager topic.
The following configuration defines Sophos as the antivirus engine and sets parameters, such as the data file update interval, notification options for administrators, fallback options, and file size limits.