***Please note the AutoElevate Agent is designed for and supported on Windows workstations version 7, 8, 8.1, 10 & 11 as well as Server 2008/R2, 2012/R2, 2016, 2019 and will work on RDS, Terminal Services, VDI, and via RDP. ***
***It is recommended that prior to large scale deployments you should first have your ticketing system integration with AutoElevate complete. For limited testing purposes you can deploy agents manually. ***
MSI Agent File
You can download the MSI file, access your license key, and also adjust other settings by clicking on the “Settings” tab under General Info -> Agent MSI - Download.
To manually install the System Agent or using another management tool here is what you’ll need:
- A valid AutoElevate license key which should be provided to you upon Trial registration or purchase.
- The latest AEAgent.msi file which can be downloaded from your account management page.
You can install the Agent MSI manually on each machine which will allow you to specify client company names and locations for each installation. Manual installation is especially helpful if you are wanting to deploy a handful of Agents for testing or demonstration purposes. To install manually you will need to supply the following information during installation:
License Key: Provided to you upon Trial registration or purchase.
Company Name: Enter a client company name such as “Contoso, Inc.”. If the company name entered here does not already exist in the Admin Portal it will be created automatically.
Company Initials (Optional): Enter 2 or 3-character initials for the company which will serve as a quick reference in the Mobile Notification app. So as an example, for Contoso, Inc. you may want to enter “CI”. If this field is not included, we will automatically generate initials based on the name of the company.
Location Name: Enter a location name for the machine to be organized into such as “Laptops”, “Denver”, or “Main Office”. If the Location doesn’t already exist for the company it will be created automatically.
Make sure Company and Location are consistently and precisely entered since each time a machine is installed that has a unique Company/Location a new Company or Location will be created in the Admin Portal. So as an example, if you install one machine as “Contoso” and then another as “Contoso, Inc.” in the Admin Portal you will have 2 separate Companies that will be created. If both machines are installed as “Contoso, Inc.” then both machines will be listed under the same company. To avoid variations in your installations we would recommend installing using the MSI deployment options below combined with a deployment tool (such as ConnectWise Automate, Kaseya, Autotask, SolarWinds, etc.), Group Policy, or deployment script.
Scripted MSI Deployment
To generate an MSIEXEC command that has all the commandline options necessary to install the software, which you then can use with your RMM tool (or other deployment method) you would do the following:
- From the AE Admin Portal, go to the ‘Companies’ tab
- Create a new Company by clicking the “+” button at the top of the screen. Enter a Company Name and initials and click save.
- Create a new Location by clicking the “+” button, entering a location name (locations are machine groups which can be either actual locations or anything other criteria like ‘laptops’, or ‘desktops’) and then click save.
- Once the Location has been created click the icon next to the Location that looks like ‘papers’ and the system will generate an MSI command and arguments that you can use.
To look at the MSI command for a Company that has already been created do the following:
- From the Admin Portal, go to the ‘Companies’ tab
- Click the “view” button (eyeball) next to a Company Name.
- Click the icon next to the Location that looks like ‘papers’ and the system will generate an MSI command and arguments that you can use to build a scripted deployment.
Keep in mind that you will need to modify the file path in this MSI command to match wherever you will be placing the MSI file on the machine.
You will see in that commandline argument AGENT_MODE which can be changed to "live" when you run it so that the agents are forced into Live mode at install.
You can see that the MSIEXEC command that is generated uses the following common installation options:
/i = sets the MSI to install. Options below must be set for successful installation.
/uninstall = sets the MSI to uninstall. Uninstall should be done from add/remove applications but can also be done form the MSI file directly. When done from the MSI the other AutoElevate specific options below such as “LICENSE_KEY” do not need to be specified.
/quiet = silent installation with no user interaction.
/lv = log file with verbose output – specify the log file name that should be created.
The following AutoElevate specific options must be set for successful installation (with the exception of the optional "COMPANY_INITIALS"). Use values specific to your needs and practice:
LICENSE_KEY="123456789ABCDEFGYOURLICENSEKEYHERE" – Supplied to you upon sign-up and/or purchase
COMPANY_NAME="Contoso, Inc." – Setting this value categorizes the workstation in the Web Admin Portal by this company name. For best results match the Company Name to an existing Company Name or reference in your RMM or Ticketing system.
COMPANY_INITIALS="CI" – (Optional) Short initials that will serve as a quick reference in the Mobile Notification app.
LOCATION_NAME="Main Office" – This should match the Location Name or reference in your RMM or Ticketing system.
AGENT_MODE="live" – This can be set to “live”, "policy, “audit”, or “technician” so that the Agent installer can override the current mode or be set to automatically install in the mode of your choice. (*** these mode options are case sensitive and should be in lowercase otherwise this part of the command will fail and the agent will default to audit mode ***)
Here is an example of what the installation command might look like (assuming the AESetup.msi file is located in the “C:\Downloads” folder) for a silent unattended installation and to make a log file called AEInstallLog:
msiexec /i C:\Downloads\AESetup.msi /quiet /lv AEInstallLog.log LICENSE_KEY="123456789ABCDEFGYOURLICENSEKEYHERE" COMPANY_NAME="Contoso, Inc." COMPANY_INITIALS="CI" LOCATION_NAME="Main Office" AGENT_MODE="audit"
New Companies/Locations Driven By MSI Deployment
To create additional companies you can use the same MSI command script and simply change the Company Name, Company Initials, & Location which once used on a new workstation will cause those companies/locations to be setup on the admin portal automatically.
Here is an example of what the uninstall command might look like (assuming the AESetup.msi file is located in the “C:\Downloads” folder) for a silent unattended uninstallation and to make a log file called AEUnInstallLog:
msiexec /uninstall C:\Downloads\AESetup.msi /quiet /lv AEInstallLog.log
Upon successful installation of the AEAgent.msi on the target system, you should have a new service named “AutoElevate Agent” which will start as part of the install and is also set to start automatically at Windows startup. If you check running processes you should see the “AutoElevate Agent” process which is started by the service as well as the AEAlert and AEUACAgent application processes which are spawned and monitored to run anytime a user is logged into the system.
If an Agent has not previously been installed on the machine the AutoElevate Agent will automatically be set to run in “Audit” mode after installation.
When “Audit” mode is active all UAC activity for the user is tracked but there is no change in the user experience. When “Live” mode is active the UAC events are intercepted and replaced by customized AutoElevate dialog boxes.
After on-boarding it is recommended that you run for a period of time in “Audit” mode so you can evaluate the current user behavior, system settings, and activity and then make a corresponding plan of action for each client before switching them to “Live” mode. Please see our guide on Client Onboarding.