Upgrading Neurons for ITSM from an Earlier Release

landscapes during an upgrade, you can upgrade the development (staging) or testing (uat) landscapes and test them without affecting the production landscape after you have verified that the development (staging) or testing (uat) landscape upgrade was successful, go ahead with production landscape upgrade reporting feature you must upgrade both and the reporting feature at the same time the versions of the software for both and the reporting feature must be the same licenses versions of ivanti service management before release 2015 1 used a different licensing structure when you upgrade to release version 2015 1, the system automatically uses the licenses that you used in the previous release in the system configuration wizard, on the configuration application page, there are fields to enter the license files the system populates these fields automatically based on your previous license file see configuring the configuration database docid\ d4udwe3omxjzcyewim 8m dsm integration if your deployment includes a dsm integration, you must configure and verify your dsm integration for the new release although there is a dsm integration service component in the installer, it is only used for dsm integrations prior to ivanti service management release 2015 2 for dsm integrations after ivanti service management release 2015 2, you must use the package from the ivanti app store after you have upgraded , access the software app store and the dsm integration by doing the following log into https //support heatsoftware com/ https //support heatsoftware com/ go to the software app store by selecting app store from the top menu from within the software app store, open the dsm integration package download the dsm integration package for release 2019 1 and the accompanying instructions follow the instructions to configure and verify your dsm integration for more information about dsm, see working with dsm in the online help about upgrading from earlier releases the upgrade to the n version of ivanti service and asset manager should be always performed from n 1 version for example, upgrade of on premise version 2018 1 1 to 2019 1 0 should be done only after the upgrade path of 2018 3 1 skipping of any of the released version of the application during an upgrade might fail the application upgrade or the application might stop working post the upgrade 2019 2 is a cloud only release and has no updates for on premise customers the system upgrade log file name under c \logs\releasetool will be “applypatchconfigdb2019 3 1 log” for config database which is expected for 2020 1 release to upgrade to release , you must upgrade your system to every service management release between your currently installed release and release 2020 3 in sequential order see the table below upgrade from release details install release 2013 1 x the current ivanti service management version and the inventory management component, if present see uninstalling the inventory management component docid 9b9udlutmoiufd2ifg469 2013 2 2 2013 2 x 2014 1 1 2014 1 x 2014 2 1 2014 2 x 2014 3 1 2014 3 x 2015 1 2015 1 x nothing 2015 2 2015 2 x 2016 1 2016 1 x 2016 2 2016 2 x 2017 2 2017 2 x 2017 3 x 2017 3 x 2018 1 x 2018 1 x 2018 3 x 2018 3 x 2019 1 x 2019 1 x 2019 3 x 2019 3 x 2020 1 x 2020 1 x important steps to be performed click here docid 9b9udlutmoiufd2ifg469 to view the steps 2020 2 x 2020 2 x nothing 2020 3 x 2020 3 x 2020 4 x 2020 4 x 2021 1 x 2021 1 x 2021 2 x 2021 2 x 2021 3 x 2021 3 x 2021 4 x 2021 4 x 2022 1 x 2022 1 x 2022 2 x 2022 2 x install the patch hotfix bug 997037 994439 onprem zip https //forums ivanti com/s/article/ivanti neurons for itxm v2022 3 download (install this patch after upgrading to 2022 3 and on fresh installation) 2022 3 x 2022 3 x 2022 4 x 2022 4 x 2023 1 x 2023 1 x 2023 2 x 2023 2 x 2023 3 x 2023 3 x refer to installing neurons for itsm docid\ pcweaszdr01o2tnoqujvp 2023 4 x for example, if you are currently on ivanti service management release 2014 1 x and you want to upgrade to ivanti service management release 2018 3, you must do the following uninstall ivanti service management release 2014 1 x and the inventory management component, if present see uninstalling the inventory management component docid 9b9udlutmoiufd2ifg469 install ivanti service management release 2014 2 x uninstall ivanti service management release 2014 2 x install ivanti service management release 2014 3 x uninstall ivanti service management release 2014 3 x install ivanti service management release 2015 1 x install ivanti service management release 2015 2 x install ivanti service management release 2016 1 x install ivanti service management release 2016 2 x install ivanti service manager release 2017 3 1 install ivanti service manager release 2018 1 x install ivanti service manager release 2018 3 x install ivanti service manager release 2019 1 x install ivanti service manager release 2019 3 x install ivanti service manager release 2020 1 x install ivanti service manager release 2020 2 x important steps to be performed click here docid 9b9udlutmoiufd2ifg469 to view the steps install ivanti service manager release 2020 3 x install 2020 4 x install 2021 1 x install 2021 2 x install 2021 3 x install 2021 4 x install 2022 1 x install 2022 2 x install 2022 3 x click here for details docid 9b9udlutmoiufd2ifg469 install 2022 4 x install 2023 1 x install 2023 2 x install 2023 3 x install 2023 4 x upgrading from ivanti service management release 2017 3 x if you are upgrading to version 2018 3, you must first upgrade to version 2018 1 1 you do not have to uninstall ivanti service management release 2017 3 x if you have a multiple server environment, you must shut off the notifications to the web servers before you upgrade the system this is because when you make metadata changes as part of the upgrade, the system tries to synchronize them, but because the versions are different, the system hangs or takes a lot of time see step 2 below perform these steps on the system that hosts the components back up the following items configuration database (configdb) application database attachment folder (if used) (optional, if your system uses multiple servers) deactivate the web servers by doing the following a log into the configuration database see the configuration database guide for for information about using the configuration database b open the web servers workspace the system displays a list of web servers c open a web server record d clear the server is active check box e click save f repeat for all of the web servers access the installation folder on the ivanti product cd or zip file and run ivantiservicemanager exe right click and select run as administrator to ensure proper installation the installer checks for the prerequisite software components if any of those components is not installed, the system prompts you to install them now click install at the prompt installation of the prerequisite software can take several minutes if you are prompted to restart the system, click yes in the upgrade confirmation dialog box, click yes the system displays the welcome dialog box the installer checks for space and other requirements before displaying the next button in the welcome dialog box, click next the system displays the license agreement dialog box choose i accept the terms in the license agreement and click next the system displays the destination folder dialog box click next to accept the default installation folder, or click change and select a different folder the system displays the setup type dialog box your selection of features from the setup type dialog box depends on the role of the individual host in your deployment plan for the demonstration or proof of concept deployment docid\ og5jz8st0ni2e q5nxpdw , choose complete, click next, and install all components for the minimum production deployment docid\ fqapqyzkylgs3uctcvhnn , choose complete, click next, and install all components for the enterprise production deployment docid\ kbcwcoxa3psvd frmvsjm , your choice depends on the role of the host production processing server choose custom, click next, and install all components except for the operations console staging or uat processing servers choose complete, click next, and install all components web servers choose custom, click next, and only install the ivanti service manager application server for the enterprise production deployment docid\ kbcwcoxa3psvd frmvsjm , note the following if your deployment includes different processing servers for production, staging, and uat, you must install the license manager in every one of those landscapes you can choose complete and install all features on all of your servers, but doing that takes up more disk space than necessary when installing components, note the following to not install a component, click the down arrow next to the server icon next to the category name, highlight the component, right click, and select this feature will not be available if your deployment includes dsm, you do not need to install the dsm integration service because that component has been incorporated into ivanti service management since release 2015 2 click next the system displays the ready to install the program dialog box click install the system begins installing and displays a status dialog box, showing the installation progress of each module over the next few minutes click ok if the system displays a dialog box saying that reboot is required after installation if the system displays a dialog box saying that some of the files that need to be updated are currently in use, choose automatically close and attempt to restart applications and click ok when the installation is completed, the system displays the system configuration wizard go through the pages in the wizard making any changes that might be necessary if you already have an existing administrator account, you do not need to create a new account just enter the information for your existing administrator account on the upgrade system page, do not check do not create backup prior to upgrade unless you already made a backup hidden for 2017 1 and 2017 2 needs to show in 2017 3 notice that the system table version and metadata package version for the configuration database are not the latest versions see upgrade system page needs to show in 2017 3 docid 9b9udlutmoiufd2ifg469 upgrade system page needs to show in 2017 3 click the top upgrade system button when prompted, enter the administrator role credentials for the configuration database and click ok if your deployment has additional databases to upgrade, repeat steps 15 and 16 until a all of your databases have been upgraded configuration database application database (ivantism) b all of your environments have been upgraded production staging uat development (optional combination of staging and uat) click finish restart the host server (optional) if you also installed the reporting feature, you must upgrade it to the match the release number of your system access the installation folder on the ivanti software product cd or download folder and run reportingservice exe to upgrade reporting feature log in to the configuration database and activate the web servers that you deactivated in step 2 upgrading from ivanti service management release 2014 3 or earlier about upgrading from ivanti service management release 2014 3 or earlier docid 9b9udlutmoiufd2ifg469uninstalling the inventory management component docid 9b9udlutmoiufd2ifg469 about upgrading from ivanti service management release 2014 3 or earlier beginning with ivanti service management release 2015 1, the inventory management component is known as ivanti heat discovery as a result, before you can upgrade to the current version of , if you are upgrading from release 2014 3 or earlier, you must first uninstall the inventory management component uninstalling the inventory management component perform these steps on the system that hosts click the arrow at the bottom of the start menu to view the apps menu mouse over the uninstall ivanti service management icons to find the one for the inventory management component click uninstall ivanti service management in the confirmation dialog box, click yes upgrading from ivanti tryvium 2020 1 release to 2020 2 release the following steps should be performed before installing 2020 2 from 2020 1 release log in to with the administrator role open the configuration console under security controls, select security and sessions under concurrent session, change the value of named user, privileged user, and non privileged user to 0 save the changes and refresh the page and re validate the values are changed now you can install 2020 2 after installation is complete, you can change the concurrent users values as it was earlier