This thread has been super helpful and given us many conversation points and feedback. However, the thread is now gotten unwieldy and hard to parse through the feedback. I'm locking this thread and for those of you who are participating in our RCs, invite you to come give additional feedback on my post Orion Platform: Preparing for the Upgrade to 2018.2 in the NPM release candidate forum. Once we are out of RC, I'll be starting a new topic thread for upgrade feedback for NPM 12.3.
Thank you and for those of you with whom I have ongoing conversations, we'll find other avenues to move forward on those topics.
Everything went extremely smooth for me. I upgraded NPM, SAM, NCM, UDT, IPAM, and VIM. Much faster upgrade than normal and didn't run into any issues.
When I was upgrading I found RC versions and also strange we were facing lot of issue but sw tech support team hasn't identified that beta had been installed in my network. Do you know to check this versions issue in Orion polling engine like it's RC or Beta Or SP or GA?
We built out a new server to finally get off of 2008. I was rather dreading this migration and update but it could not have been smoother. I scheduled a 6 hour downtime window and we were back up and running in just over two ( and of course half of that time was waiting for the Website Optimization to complete ) We migrated/updated NPM, NCM, IPAM, SAM, WPM and NTA. No issues.
Thanks. So you built a new box(s) and pointed to old DB?
I’m doing in place. And support is giving me wildly conflicting upgrade plans since the PUA has the known bugs.
Interesting. I'm a version back--NPM 12.0.1. The PUA says it can't handle the upgrade to 12.2. Some internal SW folks told me in a Thwack meeting today that I had to download another set of app installers to get the job done. Then Support told me to just use the PUA to get to 12.1, then use the NEW PUA to go to 12.2.
Sadly I'm dealing with Server 2008 issues, so until I get the new VM licensing for 2012 resolved, I'm on hold for 12.2.
I brought a server on NPM 12.0.1, SAM 6.3.0, NCM 7.5.1, UDT 3.2.4, and SRM 6.3.0 directly to the current releases with the new installer without any issues. There is no need to take an interim step of going to 12.1. One word of warning, the installer will check for incompatibilities with existing modules and will refuse to proceed if any are found. In this case, the client had installed a version of the Patch Manager Orion module that was not compatible with their other existing modules and the new installer wouldn't proceed with it installed. Once the PM module was uninstalled, the upgrade went through without issue.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process. Learn more today by joining now.