Admin Tools 2.0 Enterprise Installation Instructions

Owned by Blake Bilbo, created
Last updated: Feb 06, 2024 by George Singley
3 min read

NOTE: If you are replacing Admin Tools 1.x with version 2.0 or later, you will need to remove the original Admin Tools service before proceeding. This can be accomplished by performing the following:

Open a command prompt as an administrator in the app-server folder located in the root of the application.

Run nssm remove "Admin Tools Server"

For On-Premise Installation:

  1. Unzip the Admin Tools build to the proper location
    This can be under C:\inetpub\wwwroot\admintools or any location you wish. Be sure your windows file path is less than 256 characters when extracting our products otherwise there may be failures when unzipping the files. After unzipping, add this location as an application in IIS.

  2. Install AdminTools/installs/MongoDB-windows-*.exe
    If MongoDB isn’t installed on their server, install MongoDB using the mongodb-windows-x86_64-5.0.9-signed.msi file from the AdminTools/installs folder that was unzipped in step 1. Follow MongoDB's installation wizard to install (default options are fine). If there are any issues, see the MongoDB Installation Guide.

  3. Install Required IIS Modules
    In the AdminTools/installs/standalone folder, there are two files - rewrite_amd64_en-US.msi and requestRouter_amd64.msi. These IIS modules must be installed in the order just listed for Admin Tools for Enterprise to work properly. They are used by the application to create a reverse-proxy to forward requests through IIS to the server application.

  4. Install & Start Windows Service
    a. Run as administrator the AdminTools/installs/install_server.bat file
    b. Click the three dots next to the Path setting. Navigate one directory up to the main Admin Tools folder and navigate to the /app-server directory. Then select the index.exe file and click the open button.
    c. Click the Install service button
    d. Run the services application on Windows and make sure that “AdminTools Server” is running. If not, start the service.


    If you have already installed the service, you can run the edit_server.bat file

    If you need to delete the service, run the remove_server.bat file

  5. IIS: Enable Application Request Router proxy
    a. Under connections, click on the server entry under the start page
    b. In the center panel under the IIS section, double click on the Application Request Routing icon


    c. Click the enable proxy checkbox in the center panel, then on the right panel click the apply button.



  6. You can now open a browser to (https://yourdomain.com/admintools) and use the application.

NOTE: If you attempt to sign in to the application and see the “Invalid Redirect URI” error message popup. This means that the Redirect URI settings for the Admin Tools item in your ArcGIS Enterprise has not been configured, please refer to How To Register Admin Tools for an OAuth App ID (Non-IWA Installs) from step 6 onwards to fix this.

Changing the port of your Admin Tools Service

Admin Tools by default runs internally on port (9180). For a situation such as you are running a beta version of Admin Tools 2.0 with 1.0 still running on 9180, you may need to change the port and run as a second service. To change the port:

  1. Temporarily stop the Admin Tools 2.0 service if it is running.

  2. In the AdminTools base directory, edit the web.config file and change line 33 from:
    <action type="Rewrite" url="http://localhost:9180/{R:1}" />
    TO:
    <action type="Rewrite" url="http://localhost:9181/{R:1}" />

  3. Save this file and exit your text editor.

  4. Under the AdminTools/app-server/config directory, edit the nodeconfig.json file and change line 2 from:
    "port": 9180,
    TO:
    "port": 9181,

  5. Save this file and exit the text editor.

  6. Restart the service or use AdminTools/installs/install_server.bat to create the service.