We are upgrading traps using this process.
First Uninstall Traps in Control panel then requires password.
Next is use the traps cleaner then requires password.
then lastly install a new Traps agent 4.2.3.
Some of the servers are requiring are reboot and some are not. These are the OS of servers were gonna upgrade.
Could someone help me to know what is the effect of not rebooting and rebooting the server after the fresh install?
FYI: We are using autofac/HPSA to upgrade, We cant use the ESM server to upgrade due to version issues
These are the version
Microsoft Windows Server 2008 R2 Enterprise
Solved! Go to Solution.
@RichardP11 Is there a specific reason to use traps cleaner as a second step? when using traps cleaner the reboot is required to completely unload the drivers, and for final deletion of files that were in use during the time of Uninstall via cytool.
We just want to make sure that the new fresh install traps will work normally after the uninstall. I am not sure also on this steps. Could you suggest? Is the uninstall via control panel is enough?
@RichardP11 Ideally you would use the built in upgrade. You can create a One-Time action to upgrade the endpoint. There can be several reasons an upgrade fails, most of the time it is due to the system needing a reboot, for other system configuration changes to complete. Also, Palo Alto networks Support can help through the upgrade process, should you run into any issues.
Yes We tried that on the actions to upgrade the traps. Sad to say we dont have palo alto support, We just have vendor support.
I tried the actions and it just applied and never delivered. Every task failed. So now we move on using Autofac.
I am not familiar with AutoFac, sorry.
If you are having failures, you should be able to collect a set of support files and send to the vendor support team. Should they be unable to resolve the issue, they can escalate to Palo Alto Support.
That said, if all of the systems fail to upgrade, I would check the uninstall password being used. You can create a one-action and attempt to upgrade your own system. Should it fail, review the logs, it will generally give you an idea of the issue. If it succeeds, you can copy the one-time action and apply to more systems in your environment.
Would that require a reboot when upgrading from ESM?
I remembered that Traps 4.1.3 cant handle upgrades coming from ESM. The vendor said that We should first upgrade to 4.2.X to use that feature.
for upgrades to the 4.2.x range, There is an upgrade plan:
ESM Upgrade Considerations
You can upgrade to ESM 4.2 from any ESM 3.4 or any later release.
Traps Upgrade Considerations
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!