Update policy not working.

Hello Redpine,

workstations still update every 60 minutes

why still - as 60 minutes is not the default; was it set to 60 minutes before? If you check the schedule on a workstation - what's the value there (and how did you check that they actually search for updates every 60 minutes)?

This also causes the workstations to lose their connection to the network

By this you mean whenever they search for updates? A UNC or an HTTP download should not cause a loss of connectivity (should because while there might be network problems the download is likely not the cause - it just makes them visible). Anyway - at which point during the download is the connection lost? Does the download/update ever succeed?

Christian

The previous policy was set to update every 60 minutes.   The update policy from the server was changed to 240 minutes several weeks ago, but many workstations still update on 60 minute cycles, and during the update the connection to the Windows 2012 domain controller and Exchange 2013 server are disconnected.  

The updates do apply on the 60 minute cycle.

I am not sure when the disconnection occurs, it just happens at the same time as the update cycle occurs.

Hello Redpine,

to get this straight: If the Check for updates every is set to 240 minutes in the updating policy's Schedule tab and the correct policy is applied to the clients and the clients comply with the policy (Updating policy column in the Update details tab of the Endpoint view shows Same as policy) then the clients should check for updates every 240 minutes (note that this is independent from the schedule in Configure update manager).

As to the disconnection: Does the update eventually succeed (i.e. are the clients shown as Up to date)? If so, how do you become aware of the disconnection - a balloon tip from the network icon or an error in an explorer window, Outlook or brwoser session? If not - did the updates ever work and when did the issues begin? Not to forget - the CID (and management server) is neither on the DC nor the exchange server, is it?

Christian

Was there ever a resolution to this problem? We are seeing this same problem on our servers.

Hello Anthony Via,

this same problem
the OP mentions two problems: 1) The endpoints updating with an interval different from the one in the policy although they allegedly comply with the policy and 2) the endpoints losing connectivity. As you can see Redpine  didn't answer some of the questions so it's not clear what the actual issue is or was. Hence it's not clear (perhaps to you but not to me) what this problem actually is. Could you please give some details?

Christian

The particular problem I was referring to was servers losing network connectivity during what I thought was the regular updates. It turns out this was only the case during the initial install of Sophos. It looks like the installer runs the Windows Restart Manager to restart some services during install, which was causing a network blip.