Is there a setting that can be turned on to nag the users to reboot the workstation after updates that require a reboot?

Hello TMike,

There must be a key in the registry to define display frequency of the prompt which is display with the message 'you must reboot your computer...'

I found this one but I'm not sure HKEY_LOCAL_MACHINE\SOFTWARE\KasperskyLab\AVP6\Data\RestartTime

I don't want to force a reboot after so many minutes, but I'd like to have a nagging message pop-up every so many minutes with the option to reboot now or later. Is this possible?

Thanks

Well I can tell you, but need to know which nagging message you want? More than likely you want both so I'll outline both here.

The first is when you push installs or new install packages. (Assuming you use the Admin Kit) go to Remote Install....right click on the package in question.......go to properties.........OS Reboot.........and there you go.


The Second one is in the policy that is set....

Go to your active policy.......right click go to properties. click the settings tab......select the "Service" from the drop down and there you go you can go in there and select what you want. =)

The nagging message I'm referring to is when a module update is installed that requires a reboot. I'm not concerned with the prompt to reboot after KAV is first installed... only when an update is installed. I'm not seeing anything in the Service section of the policy that will prompt for a reboot. Where exactly are you referring?

Thanks

Hello,

As far is I know, there's no such settings.
Why do you want to force users to reboot their computer ? They will probably shut down their computer when leaving and restart it the next day. Also protection is still working when reboot is pending...

Um, why would you NOT want to force users to reboot their computers? Users, in general, are computer illiterate and, as Murphy's Law dictates, if they can possibly screw something up, they will. A forced reboot is a necessity to ensure that updated components really are installed. Without a forced reboot, users might leave their computers on for days or weeks at a time without even logging off, and the updates will not be applied.

Without forced reboots, that significantly increases administrator overhead, because now we have to manually check each computer to make sure updates were applied. Sure, we could schedule forced reboots, but if no updates have been installed, why should we have arbitrary mandated reboots?

Quite frankly, not having a forced reboot option is something of a deal breaker. As a Kaspersky reseller, I promise my clients a solution that is fully automated--a set-it-and-forget-it option are far as they are concerned. No forced reboots effectively negates that.

Hello,

Next version of Kaspersky Administration Kit will include a new option to gather all hosts asking for a reboot following a module or iDS update.
If you want user to forget antivirus program on their computer, you can disable notifications and even more hide the "K" icon in the systray. In this case they will not be aware that a reboot is "necessary".

I still think that this option is not necessary, this is not critical for protection.

I'm glad to hear that the forced reboot option following updates will be added in a subsequent release of the KAK.

It most certainly is a necessary feature. If a required reboot is not performed, the client is not covered by the most recent updates. The Kaspersky software will still be protecting the client, but without the most recent updates installed, the client is still at a higher-level of risk than it would be had the reboot been performed. As an administrator for many small-business networks, I have clients who like to leave their computers on 24/7 without rebooting them or even logging off, and since I am a third-party contractor, I can't enforce a scheduled reboot regimen without their permission. So an option for a forced reboot following updates is a necessity.

Thank you. I think this will come to good use for many.

Otherwise, in the workstation policy, Settigns tab -> Service -> Interraction with user -> Advanced

Uncheck info balloons for "Other important events".

So, your users will not get the Reboot prompt balloon event if it's needed after an update.

Cheers,

Alexis