Video Screencast Help

Status of "Restart required"

Created: 17 Sep 2013 • Updated: 17 Sep 2013 | 13 comments
diabolicus23's picture

I'm migrating a lot of clients with AutoUpgrade tool. Everything worksk fine but the "Restart required" status reported appears as not correct.
I've a huge number of clients with the following situation:

In client status summary, I see "No" as Restart Required.SEP_Restart_1.jpg

But if I check the client properties:

Other clients report, correctly, "Yes" in the summary.
Why does this happen? And how could I create a report that tells me exactly how many clients have the status of Restart Required?

Comments 13 CommentsJump to latest comment

Rafeeq's picture

The same would reflect on the SEPM home page with restart required. 

diabolicus23's picture

The number of restart required in homepage is compliant with the PCs with Restart Required as YES.

All other PCs are reported as "to be restarted" only by double clicking them.

Mithun Sanghavi's picture


What version of SEPM 12.1 are you currently running?

This was a known issue with earlier version of SEP 12.1.

Please migrate SEPM and all the SEP clients to the Latest vesion of SEP 12.1 RU3 as it resolves the issue - 

Symantec Endpoint Protection client fails to report reboot status to Symantec Endpoint Protection Manager after upgrade to 12.1.2

Fix ID: 2871345/3069464

Symptom: The Symantec Endpoint Protection Manager console shows "Restarted Required" as "No" for clients that have not restarted after the upgrade to 12.1 RU2. The deployment status in the Symantec Endpoint Protection Manager console displays the message, "To provide complete protection Symantec Endpoint Protection requires this computer to restart." The Symantec Endpoint Protection user interface on the client also shows that a restart is needed.

Solution: Modified the upgrade process to send the latest opstate data to the Symantec Endpoint Protection Manager server.


New fixes and features in Symantec Endpoint Protection 12.1.3

Check this Thread with similar query -

Hope that helps!!

Mithun Sanghavi
Associate Security Architect


Don't forget to mark your thread as 'SOLVED' with the answer that best helped you.

diabolicus23's picture

SEPM is on 12.1 RU1 MP1

I cannot upgrade it till this night smiley so tomorrow I'll check with faith.

SameerU's picture


Please upgrade to SEP 12.1.3


diabolicus23's picture

I can confirm this, after the upgrade nothing has changed.

Still a lot of machine (let me say, around 60%) reports No in the summary and Restart Required in their properties.

S_K's picture

just to add, once the machines has downloaded the upgrade package, it reports Restart required "YES" and on the next heartbeat it shows "No" and you can only see that restart is needed when you click Edin Properties on the machine

S_K's picture

Sorry for the spam, just found the answer on my ticket that I opened some time ago with Symantec regarding this issue:

"the bug as been fixed in RU3, that's means that any migration from RU3 to future versions will be safe of this problem. Unfortunately in your case because you are migrating from a previous version there is no way to know if the machine needs to be rebooted or not from the SEPM if the defect occurs. So the only way to be sure that the clients are completed the installation is scheduling a reboot for this machines or setting the package settings to prompt the user to reboot the machine"

diabolicus23's picture

A little bit annoying but at least we've the answer.

Do u know if they will write this in a public KB (in order to explain the behaviour to the customer)?

diabolicus23's picture

Does something know a SQL query in order to read directly from the DB which machines have this status?

I need that list because I've to schedule a reboot for those machines only.

S_K's picture

not sure if they will write KB. But if you keep track of the machines to which you apply the upgrade package, give them some time (depending on the heartbeat interval) so they can download the package and then reboot.

diabolicus23's picture

Not so easy in a big environment with huge number of groups, subgroups and so on...