How important the reboot after upgrading the traps agent from 4.1.3 to 4.2.3 agent version

[RichardP11]

Hi Community,

I would like to ask how reboot is important after upgrading the Traps Agent?

We have a issue on rebooting it because the target servers are production.

These are the Windows operating system:

Microsoft Windows Server 2008 R2 Enterprise
windows_2003_r2_server_standard_edition_service_pack_2
windows_2008_r2_server_enterprise_edition_x64_service_pack_1
windows_2008_r2_server_standard_edition_x64_service_pack_1
windows_2012_r2_server_datacenter_edition_x64
windows_2012_r2_server_standard_edition_x64
windows_2016_server_datacenter_edition_x64
windows_2016_server_standard_edition_x64

Any tip?

[efrancis]

@RichardP11 

It is not a hard requirement to reboot. But if the servers are production boxes, ideally (after testing, always test upgrades in a sandbox before upgrading production systems.) the upgrade would be deployed during a patching cycle. The reboot allows the agent to benefit from any new drivers or modules that require a component to load on boot.