How To Update Your Admin Tools With A Newer Version (On-Premises)

Owned by Blake Bilbo
Last updated: Apr 12, 2024 by Kenny Tran
2 min read

There will be times when you will need to update your Admin Tools version with a newer one. After requesting and being provided with a new build from GEO Jobe, please perform the following steps: 

Upgrading from AdminTools 1.x to 2.x

If you are Upgrading from Admin Tools 1.x to Admin Tools 2.x, you will need to re-install the application as new. Please see our Admin Tools 2.0 Installation Guide.

Regarding this Article

This is the minimum steps required for a typical Admin Tools setup with no variables, security or other complications to overcome. It is not meant to serve as a comprehensive solution to any and all installation workflows and environments.

Step-by-Step Guide

  1. Stop the AdminTools Server service in your Windows Services application.
  2. Make sure to back up the old AdminTools folder (typically found in your wwwroot directory) before replacing the files (Tip: We suggest COPYING the existing AdminTools folder to a new location, instead of renaming it. This is in case if custom files are present in your previous install that do not come standard with your build).
  3. Extract and replace all the files from the zip file that GEO Jobe has provided you into your existing AdminTools folder (not the backup).
  4. Go into Internet Information Services app (IIS), and ensure that the AdminTools folder is still converted to an application.
  5. Start that service again after the files are copied.
  6. You should now be running the new version of AdminTools. You can verify this by checking the bottom right corner of the AdminTools page once you have logged into the tools.


Updating Only

This is for the Update/Replacement of a newer version of Admin Tools. If this is your first installation of the tools, please see the following article:

Admin Tools 2.0 Installation Guide

If You Get A "Folder In Use" Error When Overwriting The app-server Folder:

In some instances, nssm.exe may still be holding open the files in the app-server directory.

Finding and stopping the process should then allow the files to be overwritten.