I updated some Linux systems that are running Change Control from v6.3.0.180 to 6.3.0.749. We're not blocking anything in enabled mode, just monitoring \logging changes. Can I just run the task to put these back into enabled mode or do they need to be restarted first?
Solved! Go to Solution.
Please follow the step below to put the machine back to enable mode
Please follow the step below to put the machine back to enable mode
I already have all that in place and know how to run a client task on a system. My question was whether or not I can re-enable without restarting after the update. The upgrade process has a reboot in between in the guide, but I am wondering if it is required before re-enabling. The reason is that these will be patched tomorrow and then restarted and I'd rather not have to restart them twice.
I guess another thing to ask: Is there harm in leaving them in update mode temporarily, since we are only monitoring, not blocking?
All upgrades require a reboot for the new version. I would recommend rebooting if you upgraded to load the new driver.
You can leave it in update mode if you are not blocking anything.
McAfee Support
Benjamin Ellis
Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
Hi @Jmac24 MACC upgrades require a reboot to load the new kernel driver. Until the systems are restarted, they will continue to run with the previous kernel driver, but yes, you can run in Enable mode until then. It is recommended to restart asap after MACC upgrades though. If this is a Linux server, it's suggested to perform the upgrade during a maintenance window, where a reboot can typically be performed (depending on how you manage your servers).
Corporate Headquarters
6220 America Center Drive
San Jose, CA 95002 USA