Upgrading from one build of Track-It! 20xx to another
Warning
(2020 Release 03) The method of storing technician records has changed for Track-It! 2020 Release 03 and later. After upgrading to Track-It! 2020 Release 03, all existing SQL login accounts for groups and technicians that were created during the initial Track-It! installation are removed. These SQL login accounts are no longer needed because we have redesigned the authentication process in Track-It! 2020 Release 03. For more information, see Dependency on Microsoft SQL login accounts.
Note
(2020 Release 03) After upgrading to Track-It! 2020 Release 03, technicians that use Track-It! credentials must change their password when logging in to Track-It! for the first time after upgrade. You must change the password irrespective of the configured password policy.
The following upgrade paths are supported for Track-It! 2020 Release 03:
- 2020 Release 02 (RTM Build) to 2020 Release 03 (RTM Build)
- 2020 Release 01 (RTM Build) to 2020 Release 03 (RTM Build)
- 2019 Release 03 (RTM Build) to 2020 Release 03 (RTM Build)
The following figure illustrates the supported upgrade paths from earlier Track-It! releases to Track-It! 2020 Release 03:
Before you begin
We strongly recommend that you create a backup of the database of your current Track-It! release before upgrading.
Best practice
We recommend that you configure backups to occur daily.
For more information, see
How to backup Track-It! 2020 database
. For more information about Microsoft SQL Server Database maintenance and related best practices, see
Database maintenance and Best practices
.
To perform an upgrade
- As an administrator, log on to the system where you want to upgrade Track-It!.
- Based on the release you want to install, click one of the following options to download the installer file to a preferred location:
- Double-click the installer to extract the setup files.
By default, the extraction location is C:\Program Files (x86)\Track-It! <version number> Setup. - On the Track-It! versionNumber Setup page, click Next.
- To start the upgrade, in the Track-It! dialog box, click Yes.
(2020 Release 03) When you upgrade to Track-It! 2020 Release 03, the following SQL log files are created by default:- SMSQLTRC.LOG
SMSQLERR.LOG
These files are located at C:\Program Files (x86)\BMC\Track-It!\Logs.
- (Optional) Choose the language in which the earlier version of Track-It! was installed.
- On the Welcome to the setup wizard for Track-It! page, click Next.
- On the License Agreement page, click Yes.
- On the Select Components page, select the appropriate check boxes, and click Next:
- Select the Upgrade Application Server check box.
- By default, the Install BMC Client Management for Asset Management check box is selected.
If you do not want to install BMC Client Management, ensure that you clear the check box. If you have already installed BMC Client Management, the check box is disabled. - Select the Upgrade a Track-It! database check box.
- If the Install BMC Client Management for Asset Management check box is selected, on the Select License File page, upload a license file or select the Use temporary license file check box to use a trial license that is valid for 30 days.
- If the database information is not populated automatically, on the SQL Server Database Information page, perform the following actions:
- In Server field, enter your server name.
- In the Database field, enter your database name.
- To enable the server to dynamically select a port, select the Dynamically determine port check box.
- (Optional) Clear the Dynamically determine port check box, and in the Port Number field, enter a custom port value.
- Click Next.
- (Optional) If the setup determines any users are using the Track-It! application, to terminate the user session, click Yes.
- (Optional) If you created a backup set of your current database of Track-It!, click Yes.
Note
The method of storing technician records is changed for Track-It! 2020 Release 03 and later. After upgrading to Track-It! 2020 Release 03, all existing SQL login accounts for groups and technicians that were created during the initial Track-It! installation are removed. These SQL login accounts are no longer needed because we have redesigned the authentication process in Track-It! 2020 Release 03.
When you upgrade to Track-It! 2020 Release 03, the passwords of all technicians who use Track-It! credentials are reset to system default. After the upgrade is complete, these technicians must change their password at first login.
The passwords of technicians who use Windows Integrated Authentication or Pass-through Authentication are not affected by the upgrade.
- On the SQL Server Administrator Login page, enter the administrative login credentials for the database and click Next.
- On the Administrator User Information page, complete the fields and click Next.
On the Start Copying Files page, review your settings and click Next to start the upgrade process.
The upgrade process might take some time.Note
After you upgrade to the new release of Track-It! successfully, you must:
- Restart your server and clear the browser cache.
- If needed, apply the required licenses. For more information, see Applying a license file.
(2020 Release 03) If the total number of technicians and groups is more than 150, then the following message is displayed during the upgrade:
(2020 Release 03) If records with same technician and group name are found in the Track-It! database, delete them.
The upgrade stops until you delete these records. The following message is displayed:Technician and Group modules have records with the same login name: loginNames Delete these Groups and Technicians before attempting upgrade again.
- (2020 Release 03) If SQL login accounts with same built-in SQL Server schema names are found in the SQL database, delete them.
The upgrade stops until you delete these SQL login accounts. The following message is displayed:Technician and Group modules have records with the same login name as of built-in SQL Server schemas: loginNames Delete these Groups and/or Technicians before attempting upgrade again.
- (2020 Release 03) If the SQL login accounts are not removed during the upgrade, run the SQLLoginElimination utility to remove them. For more information, see To remove the SQL login accounts by using the SQLLoginElimination utility.
The following message is displayed:WARNING:
The SQL login accounts are not deleted, however the upgrade will continue.
After successful upgrade, you must delete the SQL login accounts. For related procedure, see Knowledge Article https://communities.bmc.com/docs/DOC-132231.
The error logs for the removal of SQL login accounts are recorded in the NAMSYSLOGS table and the error, warning, or debug logs are recorded in the NAMSYSSQLELMINATIONLOGS table.
Comments
Log in or register to comment.