Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 8 replies
  • Subscribers 3 subscribers
  • Views 14091 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Update policy not working.

Redpine

The Sophos Enterprise Console, version 5.2.0.644 shows worksations as connected and updating policy as up to date.  However, the policy is set to 240 minutes, but the workstations still update every 60 minutes.  This also causes the workstations to lose their connection to the network during updating.   Can you advise how to change both of these issues?

:41893


This thread was automatically locked due to age.
Parents
  • 0

    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

    :42009
Reply
  • 0

    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

    :42009
Children
No Data
Unfiltered HTML