Sophos updating policy not set

C:\Program Files\Sophos\Aut) extracts of interest User-Protection/quot-Sophos SAU-lt-hostname-gt-quot-account-locks-out/td-p/16469 User-Protection/Sophos-Enterprise-Console-wont-update-with-a-twist/td-p/26849 ", is changed?In the alc log you (Launch SAV - on the main page you can see "view updating log" ) I would think you will have the error: Time: 11/07/2012 Message: There was a problem while establishing a connection to the server.For more information about how to discover users, see the Configure Active Directory Discovery for Computers, Users, or Groups section in the Configuring Discovery in Configuration Manager topic.Because the Application Catalog receives the list of available software for users from the site server, this setting does not have to be configured as True or Yes for users to see and request applications from the Application Catalog.Updates are copied manually on to the mgmt1 server from CD.Putting the server online is not an option and therefore the Sophos servers are not an option for providing updates. When the "Check for updates..." option is clicked, the dialogue box displays that it cannot connect to server (depsite the server being itself and all other machines configured in the same way work).Hi, We're running a VM infrastructure of Windows Server 2008 R2 and Windows 7 clients.Our Management Server (mgmt1) is hosting the latest release of Sophos Enterprise Management Console.

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.