Upgrade to version NPM v9.1

Hello all,

We are currently running NPM v8.5.1 and planning to up to v9.1. Over all has there been a good experience with upgrading? If not are there any known issues?

I was hoping someone could provide solid documentation on the upgrade procedure.

Is NPM v9 - service pack 2 compatible with NPM v9.1? Any help would be greatly appreciated.

thanks

Find more posts tagged with

upgrade_9.1_procedure

Accepted answers

All comments

FormerMember

Is NPM v9 - service pack 2 compatible with NPM v9.1? Any help would be greatly appreciated.

NPM v9 SP2 is superceded by NPM v9.1. There's no issue of compatibility.

kweise

Primom,

Overall, our upgrade to NPM v9.1 went very smoothly. We have two pollers and an additional web server. I stopped all services on both polling servers, upgraded our primary Orion server first, then upgraded our additional polling engine. Finallly I upgraded our additional web server. I've seen some user posts on here that reported some issues during their upgrade, especially with pass through authentication. Here is a link to an exchange I had with a user that proved usefull before doing my upgrade.

Hope this is helpful to you.

FormerMember

My big problem was that the NPM service timed-out when restarting. Tried running the NPM configurator again but the same thing happened. Just restarted manually and its still working.

primom

thank you all for you responses they are greatly appreciated. Would anyone know of any online tutorials of an upgrade from 8.5 to 9? i only see 8.0 to 8.1

viol8tor

Upgrade problems to look out for: - In my experience, every update has an annoying habit of not respecting your custom IIS settings. (I setup host header parsing so I can get to NCM and NPM on port 80.) So, every time the configuration wizard runs, I have to reconfigure the IIS settings. One other annoyance is NPM updates tend to turn on some of the "packaged" Advanced Alerts you turned off. I especially like when the "High Transmit Percent Utilization Alert" - with a default threshold of 2% kicks in. Nothing warms the cockles of my heart more than seeing my NPM console get flooded with Interface Utilization errors.....