Firewall driver update doesn't notify users to reboot in OfficeScan (OSCE)

- Updated:
- 6 Mar 2017
- Product/Version:
- OfficeScan 11.0
- OfficeScan XG.All
- Platform:
- Windows 10
- Windows 10 32-bit
- Windows 10 64-bit
- Windows 2000 Advanced Server
- Windows 2000 Professional
- Windows 2000 Server
- Windows 2003 32-Bit
- Windows 2003 64-Bit
- Windows 2003 Datacenter 64-bit
- Windows 2003 Enterprise
- Windows 2003 Enterprise 64-bit
- Windows 2003 Server R2
- Windows 2003 Standard
- Windows 2003 Standard 64-bit
- Windows 2008 32-Bit
- Windows 2008 64-Bit
- Windows 2008 Datacenter
- Windows 2008 Datacenter 64-bit
- Windows 2008 Enterprise
- Windows 2008 Enterprise 64-bit
- Windows 2008 Server Core
- Windows 2008 Server R2 Enterprise
- Windows 2008 Standard
- Windows 2008 Standard 64-bit
- Windows 2008 Web Server Edition
- Windows 2008 Web Server Edition 64-bit
- Windows 2012
- Windows 2012 Datacenter
- Windows 2012 Datacenter R2
- Windows 2012 Enterprise
- Windows 2012 Enterprise R2
- Windows 2012 Server Essential R2
- Windows 2012 Server Essentials
- Windows 2012 Server R2
- Windows 2012 Standard
- Windows 2012 Standard R2
- Windows 2012 Web Server Edition
- Windows 2016
- Windows 2016 Server Core
- Windows 2016 Server Datacenter
- Windows 2016 Server Standard
- Windows 7 32-Bit
- Windows 7 64-Bit
- Windows 8 32-Bit
- Windows 8 64-Bit
- Windows 8.1 32-Bit
- Windows 8.1 64-Bit
- Windows Vista 32-bit
- Windows Vista 64-bit
- Windows XP Home
- Windows XP Professional
- Windows XP Professional 64-bit

Summary

The firewall is not getting enabled on the agents as they are pending a reboot. However, checking Agent Management in the OSCE management console, Restart Required shows "No".

Details

This is currently the SPEC. The reason why the the firewall is not updated is because of the setting below:

Global Agent Settings > Firewall Settings:
'Update the OfficeScan firewall driver only after a system restart'

One option is to disable the setting above, but please note that this can cause a slight disconnection from the network. Do not do this in critical environments.

Rating:

Category:

Troubleshoot; Install; Update

Solution Id:

1116837

Feedback

Did this article help you?

Thank you for your feedback!

What was the problem with this article?

The image(s) in the article did not display properly.

The article did not provide detailed procedure.

The article is hard to understand and follow.

The video did not play properly.

The article did not resolve my issue.

Others. Please specify.

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:

We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support

Thanks for voting.

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:

We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.