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

Reply
L1 Bithead

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

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?

L4 Transporter

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

@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. 

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!

The Live Community thanks you for your participation!