Upgrading AssetTrack

1. Prepare for the upgrade

Coordinate the upgrade with users

Although an AssetTrack upgrade should have minimal impact on users, it's a good idea for users to "start with a clean slate" as much as possible. To this end, inform all AssetTrack users of the an upcoming upgrade window (conservatively a 2-hour outage) and advise them of the following recommendations:

• All AssetTrack Mobile users should upload their collected data to AssetTrack and, if possible, refrain from data collection until they get notification that the upgrade was successful and AssetTrack is available.
• All AssetTrack Console (Queue) users should coordinate with AssetTrack users so that they can "clear the queue" as much as possible prior to the upgrade. If they cannot clear all of the data (because it’s tough to coordinate or because validation/publishing problems prevent it, you can still proceed with the upgrade. You will be able to publish the data after the upgrade even if it was collected under the older version.

Back up the AssetTrack database

Make a "Full Database" backup your AssetTrack database.This is typically done using SQL Server Management Studio and may require SQL Server administrator (sa) access to the SQL Server. 

Back up the AssetTrack Server directory

1. Access the server where AssetTrack Server is installed, typically using Remote Desktop.
     
2. Locate the AssetTrack directory. The default location is:
             C:\Program Files\AMI\AssetTrack Server\ 
     
3. Copy and paste the entire directory so that there is a folder called Copy of AssetTrack Server.
   This will allow you to downgrade quickly should it become necessary to do so.

Back up the Import Service directory (for repository-integrated customers only)

e.g. CA ITAM, CA Service Desk, HP Asset Manager, ServiceNow

1. Access the server, typically using Remote Desktop
     
2. Locate the Import Service directory. The default location is:
             C:\Program Files\AMI\Import Service\
     
3. Copy, and paste the entire directory so that there is a folder called Copy of Import Service.
   This will allow you to downgrade quickly should it become necessary to do so.

2. Apply AssetTrack database patches

As of version 3.2.621.144, the installer upgrades AssetTrack's SQL server database automatically. This applies when upgrading from all releases after 3.1.49.0. Because the installer is needed to apply the update, you must have the original version of AssetTrack web installed matching up to the database. For example, if you are currently running 3.5, the AssetTrack web version 3.5 must be installed alongside the SQL database patched up to 3.5 before kicking off a new install in order for the patches to be configured automatically.

From time to time you may be required to patch your AssetTrack SQL database when a new AssetTrack software version is released. This could happen if you are installing AssetTrack web to a new environment or If you are upgrading from an old version of AssetTrack. You may also be required to apply more than one patch to catch up with the current version you are attempting to install.

3. Upgrade AssetTrack Server

To update the AssetTrack server application, simply execute the latest AssetTrackSetup.exe program on the AssetTrack Server machine and follow the same installation steps as were required when performing an initial installation. The installation program will overwrite your existing AssetTrack Server installation and run the appropriate database patches.

When AssetTrack Setup detects that an existing AssetTrack Server instance is already installed, you will receive the following warning:

Click Yes to proceed and update your AssetTrack Server software to the new version.

4. UpgradeAssetTrack mobile devices

Once AssetTrack Server is upgraded, it will begin advertising an upgrade all AssetTrack Mobile devices when they connect to AssetTrack Server.

You should instruct your AssetTrack Mobile users to run the Update Agent on each mobile device to update AssetTrack Mobile software to the latest version.

5. Upgrade the Import Service - for repository integrated systems only

1. On the server where the Import Service is installed, open Add/Remove programs from the control panel.
    
2. Depending on which repository that you're integrated with, the Add/Remove program entry may be called one of the following:       
   • Unicenter Integration Components for AssetTrack
   • AMI Import Service

   Locate the entry that is suitable for you and uninstall it.
     

3. From the control panel, click Administrative Tools, and then click Services.
     
4. Look for the AMI Import Service. If you find this service Stop and disable the service.
   Note that this will only be present on the server if it was ever running an AssetTrack version that was earlier than 3.0.2171.
     
5. Use the provided installer to reinstall the Import Service.
   It should match up with the name of the item that you uninstalled above.
     
6. Once you've installed the Import Service, you can configure it using the Settings link at the top right corner of AssetTrack Server's web interface.
     
7. Locate the file C:\Program Files\AMI\Import Service\DebugImport.bat and double-click it to test the importer manually.
   An import run can take up to 30 minutes depending on the amount of data in your repository, but at the end of it, you should see that the import completed successfully. 

6. Ensuring APM Components are installed on the AssetTrack Server in multi-server installations (APM 11.3.4 - integrated systems only)