Clear reboot message from console without rebooting machines

HI,

Some good news, this is much improved in SEC 4.7 with SAV 9.7. I was testing this very thing during the beta and found that in that version forcing an update on the machine from SEC would force it to sync the state of the key.  

It should be out shortly now since the beta finished a few weeks ago.

Regards,

Jak

This still happens with alarming frequency even on upgrade to SEC v.10 with Console v.5. We are still at the beginning of deployment, and I'm seeing this in 25% of our Windows PCs. With a problem that frequent, how is it that manually creating a reg key is considered a reasonable resolution to this bug?  How on earth has this bug been permitted to persist for over 5 years? (I find the issue and this "resolution" in the KB going back to 2006.

Hi,

The AutoUpdate service should set the RebootRequired key correctly on shutdown.  I suspect the problem maybe worse with Windows 7, as it has that new, "Force Shutdown" option, if things aren't shutting down in a timely fashion.  I suspect that if the machine is forcibly shutdown, the process never gets the signal and therefore fails to alter the key.  The key should be set on startup I think to be more reliable.  If you take one of the problem machines and shut it down so it shuts down cleanly, does it change the RebootRequired key correctly?  

Jak

Negative. All the affected machines have been manually restarted normally, multiple times. Affected machines are about evenly divided between Windows 7 and XP. On one test machine that was affected early on, which I've avoided doing the manual reg key on (out of sheer obstinence), this has persisted for months, over multiple updates, including upgrade to v.10 last week.

All of the affected machines originally cleared the warning to restart to complete installation. And at least in some cases, this 'stuck' warning only appeared after multiple updates that did not trigger a stuck warning.

I see the same here, it's so annoying! I'd just like the console to not flag them as "alerts and errors". I have about 1200 of my endpoints warning me on this out of 3000. In most cases multiple reboots have been done. I'm not about to edit the registry on all of them. 

It would be nice to filter them out without having to sort the column under the Alert and Detail Tab.

Well I guess in the worst case you could go after the database using PurgeDB.exe.  0000006d  hex = 109 dec, so the following command:

PurgeDB.exe -action=delete -category=errors -HistoryLengthInDays=0 -type=AutoUpdate -code=109

should clear the alerts. PurgeDB.exe is in the Enterprise Console directory from SEC version 4 onwards.   This would run in effect the same command as:

sqlcmd -E -S .\SOPHOS -d sophos50 -Q "UPDATE dbo.Errors SET Outstanding=0 WHERE Source='ALC' AND Number=109"

Where:
.\SOPHOS represents a local SOPHPOS named SQL instance.

SOPHOS50 would be for SEC 5, for SEC 4.7: SOPHOS47, SEC 4.5: SOPHOS45, SEC 4.0: SOPHOS4.

This would set the reboot alert for all machiens to not outstanding.  The ComputersAndDeletedComputers table does have a pointer however to the Errors table so the above command will not clear the warning triangle against the machine.  The purge task the management service performs will fix that up but it may take up to 24 hours to run.  If you can't wait for that, you could run:

SQLCMD -E -S .\SOPHOS -d SOPHOS50 -Q "EXEC ErrorUpdateLatestPointerInAllComputers N'ALC'"

This is the same command the purge task runs to clean things up, note this is for SEC 5, adjust the SOPHOS50 as mentioned above for other versions of SEC.

The only downside being that for machines that haven't rebooted yet you wouldn't centrally know.  Possibly not so much of an issue.

Regards,

Jak