Overview to upgrading to Service Desk or Asset Manager 2018.3

There are a number of stages to upgrade to Service Desk or Asset Manager 2018.3, which you need to run in the following order:

You might not need to run all of these steps. The version number in brackets indicates the version when the change was added: if you are upgrading from that version or a later version, you do not need to follow the instructions for that section.

Steps that have been added or updated since the previous major release are highlighted in bold text.

  1. Back up your current system, see Back up your previous installation (all versions).
  2. Install the latest version of the software, see Upgrade to the new version.
  3. Migrate BridgeIT to connect to Framework rather than Web Access, see Migrating BridgeIT to use Framework (V7.8).
  4. If your installation is English, select the required version of English. See Select the version of English (V7.7, English only).
  5. If you use the Token only logon policy, re-enter the STS credentials, see Reapply STS credentials for the Token Only (STS) logon policy (2016.3).
  6. Upgrade the database (all versions), see Upgrade the database (all versions).
  7. If you have configured the Ivanti Console so that you can select the Framework instance on startup, update the Configuration Center URL, see Update the URL for selecting the Framework instance on the Console login (V7.7.2 – optional).
  8. If you disabled custom CI actions (usually for Asset Manager) in 2016.4 by editing the tps.config file, you need to disable it again using the Configuration Center, see Re-disabling custom CI actions (2017.1).
  9. Log in to the Console as SA to migrate certain internal data (all versions) and then apply the new license (major versions or Asset Manager 2016.2), see Migrating values (all versions) and applying the new license key.
  10. If you use Event Manager or RSS Web Generator, migrate your applications to use Framework, see Migrating Event Manager Web Service and RSS Web Generator web applications (2016.1).
  11. Rebuild the search indexes after the removal of the Asset Management modules in 2016.2 and the addition of Catalog ordering in 2017.1, see Rebuild Service Catalog and knowledge search indexes (2016.2, 2017.1).
  12. If you use Bulk Actions in Workspaces, set the Bulk Action poll period, see Set the Bulk Action Poll Period (2016.1).
  13. Set how many of the results reports from scheduled bulk actions you want to keep, see Set the number of scheduled bulk action results to keep (V7.8.2).
  14. Set the Edit MultiLingual Data privilege for each group and role, see Set the Edit MultiLingual Data privilege (V7.8.2).
  15. Generate multilingual Service Catalog strings if you have a multilingual Service Catalog that uses a language that Service Desk is not localized into, see Generate multilingual Service Catalog strings (V7.8.2 - optional).
  16. Confirm you have set a Minimum Lines property for multi-line text boxes on Web Access windows (V7.7.1), see Set Minimum Lines for Web Access text boxes (V7.7.1).
  17. If you are using the integration with Microsoft SCCM, make sure that the Parameters in Desktop Manager that specify the location of the SCCM executables are correct (7.7.2), see Set the SCCM Parameters in Desktop Manager (V7.7.2).
  18. Set the new properties for Links gadgets for use with BridgeIT dashboards, see Set the new Links gadget properties for BridgeIT (V7.7.3).
  19. Use Configuration Center to start all of your Ivanti services again, see Start the Ivanti services again (all versions).
  20. Re-implement custom background images in Workspaces, see Re-implement custom backgrounds for Workspaces (2016.1).
  21. If required, enable History in Workspaces for all user types (by default only analysts can see History), see Make the History pane in Workspaces available to all user types (V2017.3 – optional).
  22. Import the Asset Manager design transfer, see Import the Asset Manager design transfer (2016.2 Asset Manager).
  23. If you are using TLS 1.2, you need to change the OLE DB Provider for each report to use Microsoft OLE DB Driver for SQL Server. See the Choosing data sources and database fields section of the Crystal Reports help at SAP help for details of how to do this.
  24. Redeploy the clients (all versions), see Redeploy the clients (all versions).
  25. When you have upgraded to V2018.3, apply the latest update, see Applying an update to Service Desk 2018.3.