Auto updates after hours

  • Thread starter Thread starter David Hogan
  • Start date Start date
D

David Hogan

I can test this out over time, but if anyone knows in advance my following
situation it is appreciated.

My users are not taking their critical updates even when notified. I do
understand their feeling as they receive notification during the work day
and do not want to have stop work to install, reboot, etc. We've tried the
do it at lunch, do it when you are leaving at the end of the day, etc.
Bottom line is no one does it, or they forget or what have you, and I do not
want to turn this into a policy discussion.

My thoughts were to simply schedule all users to receive updates at night
and then reboot their pc in the morning. That poses the threat of their pc
being vulnerable after hours to someone else still in the building. No
problem I just have them log out or lock the pc. I know Windows update runs
as a service, but I can not find anything with web searches that tells me
the effect either choice (Logged out or Locked) has on the update service.

Will it run, will it automatically reboot the pc, is one choice better than
the other, etc.

Any comments and suggestions are appreciated and welcome.
 
We are using SUS at the one location we have 2003 Server, however and I
should have stated this up front, we have 5 other locations on nothing more
than a peer to peer workgroup, all running XP Pro and connected to the
internet through a Linksys router and DSL connection.

Thanks

"Lanwench [MVP - Exchange]"
 
The only other (built-in) option I can see is to set auto update to download
& update automatically.

David said:
We are using SUS at the one location we have 2003 Server, however and
I should have stated this up front, we have 5 other locations on
nothing more than a peer to peer workgroup, all running XP Pro and
connected to the internet through a Linksys router and DSL connection.

Thanks

"Lanwench [MVP - Exchange]"
Another option - what about SUS?
 
Thanks for the reply, but the issue is how to set the pc for after hours,
logged out, or locked and the effect on auto-update with either.

Thanks

David

"Lanwench [MVP - Exchange]"
The only other (built-in) option I can see is to set auto update to download
& update automatically.

David said:
We are using SUS at the one location we have 2003 Server, however and
I should have stated this up front, we have 5 other locations on
nothing more than a peer to peer workgroup, all running XP Pro and
connected to the internet through a Linksys router and DSL connection.

Thanks

"Lanwench [MVP - Exchange]"
Another option - what about SUS?

David Hogan wrote:
I can test this out over time, but if anyone knows in advance my
following situation it is appreciated.

My users are not taking their critical updates even when notified.
I do understand their feeling as they receive notification during
the work day and do not want to have stop work to install, reboot,
etc. We've tried the do it at lunch, do it when you are leaving at
the end of the day, etc. Bottom line is no one does it, or they
forget or what have you, and I do not want to turn this into a
policy discussion.

My thoughts were to simply schedule all users to receive updates at
night and then reboot their pc in the morning. That poses the threat
of their pc being vulnerable after hours to someone else still in
the building. No problem I just have them log out or lock the pc.
I know Windows update runs as a service, but I can not find anything
with web searches that tells me the effect either choice (Logged out
or Locked) has on the update service.

Will it run, will it automatically reboot the pc, is one choice
better than the other, etc.

Any comments and suggestions are appreciated and welcome.
 
Sorry I can't provide more help. I don't know that what you want is
possible...

David said:
Thanks for the reply, but the issue is how to set the pc for after
hours, logged out, or locked and the effect on auto-update with
either.

Thanks

David

"Lanwench [MVP - Exchange]"
The only other (built-in) option I can see is to set auto update to
download & update automatically.

David said:
We are using SUS at the one location we have 2003 Server, however
and I should have stated this up front, we have 5 other locations on
nothing more than a peer to peer workgroup, all running XP Pro and
connected to the internet through a Linksys router and DSL
connection.

Thanks

"Lanwench [MVP - Exchange]"
message Another option - what about SUS?

David Hogan wrote:
I can test this out over time, but if anyone knows in advance my
following situation it is appreciated.

My users are not taking their critical updates even when notified.
I do understand their feeling as they receive notification during
the work day and do not want to have stop work to install, reboot,
etc. We've tried the do it at lunch, do it when you are leaving at
the end of the day, etc. Bottom line is no one does it, or they
forget or what have you, and I do not want to turn this into a
policy discussion.

My thoughts were to simply schedule all users to receive updates
at night and then reboot their pc in the morning. That poses the
threat of their pc being vulnerable after hours to someone else
still in the building. No problem I just have them log out or
lock the pc. I know Windows update runs as a service, but I can
not find anything with web searches that tells me the effect
either choice (Logged out or Locked) has on the update service.

Will it run, will it automatically reboot the pc, is one choice
better than the other, etc.

Any comments and suggestions are appreciated and welcome.
 
Back
Top