HaloITSM

HaloITSM Guides

Documentation to assist with the setup and configuration of the HaloITSM platform

Guides > Upgrading Halo

Upgrading Halo

To upgrade the web-app,


Download the upgrade files from '?' (top right of the web app home screen) > Show Release Details > click on the icon for your required version.

OR

Obtain the new file from one of the following direct links:

Stable (Recommended)
Release candidate (When available)
Beta


There are two Upgrade methods listed in detail below.


Scripted Upgrade Steps


1. Extract the zip file of the upgrade files.

2. Go to your existing WebApp directory and copy the directory path.

3. Go to the extracted upgrade files and go to the scripts directory.

4. Right-click on upgrade.bat and select Run as Administrator. NB: If you have the 'Upgrader.exe' in your Web App directory, run this instead.

5. The script will ask you for the web app directory path, paste the path you copied earlier here (e.g. C:\NetHelpDesk\NewWeb)

6. The script will stop IIS, back up the old files, move the new files, run Upgrader.exe and then restart IIS.


Copy and Paste Upgrading 


To upgrade the web-app manually, please follow these steps on your server which has the web-app installed.


1. Go to IIS (make sure it is IIS, and not IIS 6.0):

2. Go to your web-app site(s) in IIS as per the screenshot below and stop it [green option on the right hand side of the screen]. Please note, that it is likely going to be called WebApp or NewWeb, or just Halo. A good way to check you are in the right place is to right-click on the site, and click explore [green on the left].

3. Copy and place all of the files from inside the version folder of the archive, to your NewWeb [WebApp] directory (located in the last step), overwriting the old ones.

4. Run Upgrader.exe in the root of the WebApp [NewWeb] directory, where you have just copied the files.

5. Restart the site(s) in IIS [blue on the right in the screenshot above].

6. Close and reopen the browser.


Troubleshooting


If you notice any irregularities in the new version, or the version numbers don't match or haven't changed, then the first thing to do is reload and clear the cache by pressing Ctrl-F5. Unlike other browser options that clear the cache, pressing Ctrl-F5 also clears the server-side cache, so it's best to use this over your usual browser-cache clearing routine.


If after carrying out your last steps your Web App does not work, then you may be missing a .json MIME type at the server level.



Navigate to Server Level in IIS, in MIME types, and if the .json MIME type is missing then click 'Add...' and enter the values as per the screenshot below.



If you have the default deployment configuration (api and auth apps within a single site/folder) you can use the automatic upgrade, if not you must use the manual method.


Popular Guides

Pin It on Pinterest