<![CDATA[Centralized Agent Upgrades from server]]>I see this:
https://www.netxms.org/documentation/adminguide/upgrade.html#centralized-agent-upgrade

However if you have a mix of win32 and win64, how do you determine what's already installed so you're upgrading with the right version?

Testing, I see when I use the wrong version I get: "Package is not compatible with target machine" when trying to install a x32...so, must me a x64 agent.

Trying to install the x64 agent, I get: Unable to start upgrade process.

Any additional ideas/howto's?

]]>https://forum.netxms.org/topic/5162/centralized-agent-upgrades-from-serverRSS for NodeFri, 13 Nov 2026 11:47:42 GMTFri, 14 Jul 2017 03:49:11 GMT60<![CDATA[Reply to Centralized Agent Upgrades from server on Thu, 20 Jul 2017 13:14:16 GMT]]>Great thanks for those scripts Tursiops. Still have to enable debug, and post the logs to try and narrow down the cause of the failure.

]]>https://forum.netxms.org/post/22736https://forum.netxms.org/post/22736Thu, 20 Jul 2017 13:14:16 GMT<![CDATA[Reply to Centralized Agent Upgrades from server on Fri, 14 Jul 2017 05:11:57 GMT]]>Hi,

I use containers with auto-apply templates. Something like this:

if ( ( $node->isAgent ) && ($node->platformNAme == "windows-i386" ) ) return true;

and the matching

if ( ( $node->isAgent ) && ($node->platformNAme == "windows-x64" ) ) return true;

Then simply apply the correct packages to those containers.

That won't fix your "Unable to start upgrade process" though.
I've seen that a few times when the upgrade does go through, but the agent version in the Console doesn't update until the next configuration poll.

Cheers

]]>https://forum.netxms.org/post/22689https://forum.netxms.org/post/22689Fri, 14 Jul 2017 05:11:57 GMT