Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 3 replies
  • Subscribers 1 subscriber
  • Views 6514 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

Awaiting Policy from Console - Reboot Required - Update Servers

Semex

Hey guys,

Heres the issue I see.

I have sophos endpoint server that I use for updates for the end clients, and use Sophos as the Secondary Server.

Once I deploy the antivirus software to the machine the staus is:

-Awaiting Policy from Console

-Reboot Required

Ok so at this state the software is on the machine, my sophos endpoint server is set as the Primary update server, but nothing in the Secondary server.  (until reboot)

So my question is:

Since my users hardly reboot their computers, and most are laptop users that just put the computer to sleep.  I want to be able to push this secondary server to the computer before a reboot is required.  Here is why.

So lets say they put their computer to sleep.  Go away from the office turn it back on, it will not hit our internal update server.  Lets say they do reboot while they are away, they won't be able to get updates till they are back in the office, maybe weeks away beacause it still has not hit the primary server for policy updates to recieve the secondary server.

Any way I can get around this dilemma.

Thanks

Jeff

:43283


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

    Hello Jeff,

    as the users must be "in" when you deploy the software and you likely somehow "coordinate" the process (what would happen if they decide to close the lid just after you've started deployment) the easiest way would be to ask them to please reboot before they leave and inform you that they have so you can check and tell them that it is "safe" to leave.

    BTW: Using Comply with ... might result in the policy to be transferred even before the reboot.

    There are some other options: a custom package with a pre-configured policy, or copying/setting the configuration with a script (which requires that you "catch" them after install and before they leave and is not as convenient as the console).

    Christian

    :43311
Reply
  • 0

    Hello Jeff,

    as the users must be "in" when you deploy the software and you likely somehow "coordinate" the process (what would happen if they decide to close the lid just after you've started deployment) the easiest way would be to ask them to please reboot before they leave and inform you that they have so you can check and tell them that it is "safe" to leave.

    BTW: Using Comply with ... might result in the policy to be transferred even before the reboot.

    There are some other options: a custom package with a pre-configured policy, or copying/setting the configuration with a script (which requires that you "catch" them after install and before they leave and is not as convenient as the console).

    Christian

    :43311
Children
No Data