Je suis finding that le plus users ignore le "Il y a updates ready to be installed, click here to install" message that WSUS pushes out. Until now we n'ont pas forced le install mais Je suis thinking about changing le group policy to enforce updates nightly. Cela va sometimes require a reboot qui Je veux to enforce through GP as well.
Je sais there will be push-back depuis le users mais am wondering si this is defendable best practice. It seems like le right thing to do to ensure PCs are up to date et secure.
Faut-il forcer un redémarrage après avoir déployé des mises à jour Windows ?
Re: Faut-il forcer un redémarrage après avoir déployé des mises à jour Windows ?
I would juste like to get on mon auto-reboot soapbox for a second: c'est been mon experience that automatically/forcing a reboot is generally a *bad* idea.
We system admins often have somewhat of a complex about making sure le latest patch has been applied *the second c'est installed parce que OMG jusqu'à alors le system is unpatched*. Cependant, you must realize that system admins at least theoretically are there to activez le people who use le system to do leur work.
If you automatically reboot once a patch is installed, and, say, le workstation's system clock has been reset, thinking c'est 2 AM, et certains poor Dilbert loses work, you've made a huge gaff. In mon opinion, c'est a much bigger gaff than having a temporarily unpatched system on le network.
In mon experience, having certains sort of un-dismissable message telling le user to reboot is usually a better idea. Let them finish leur work et reboot over lunch, ou ask them to shut down leur workstation at night, ou something that fits into votre organization nicely.
That being said, quand I helped to administer 12 computer labs in a college, we had defined downtime quand we knew for certain that nobody was going to be using tout of le machines parce que le doors were locked. That is a situation in qui autorebooting is surely ok; c'est juste le autonomous forced automatic work stoppage that irks me.
We system admins often have somewhat of a complex about making sure le latest patch has been applied *the second c'est installed parce que OMG jusqu'à alors le system is unpatched*. Cependant, you must realize that system admins at least theoretically are there to activez le people who use le system to do leur work.
If you automatically reboot once a patch is installed, and, say, le workstation's system clock has been reset, thinking c'est 2 AM, et certains poor Dilbert loses work, you've made a huge gaff. In mon opinion, c'est a much bigger gaff than having a temporarily unpatched system on le network.
In mon experience, having certains sort of un-dismissable message telling le user to reboot is usually a better idea. Let them finish leur work et reboot over lunch, ou ask them to shut down leur workstation at night, ou something that fits into votre organization nicely.
That being said, quand I helped to administer 12 computer labs in a college, we had defined downtime quand we knew for certain that nobody was going to be using tout of le machines parce que le doors were locked. That is a situation in qui autorebooting is surely ok; c'est juste le autonomous forced automatic work stoppage that irks me.