Kaseya VSA Deployment Procedure

This document explains how AutoElevate's official Kaseya VSA deployment procedure works and how to install the procedure.

IMPORTANT: This procedure will pass the appropriate Company & Location names to the MSI agent installer, allowing our system to auto-create Companies & Locations during deployment. There is no need to manually create any Companies or Locations in the AutoElevate Admin Portal first.

If you are using the AutoElevate BMS PSA ticketing integration, you will most likely need to setup Company & Location variables as well. (Please see the "Company & Location Variables" section below)

Procedure Installation

1. Download the Kaseya VSA .xml procedures that are attached at the bottom of this document.
   
   Note: There are 2 procedures attached: "autoelevate-agent-deployment-procedure.xml" & "autoelevate-agent-deployment-procedure_silent-no-prompts.xml". Use the "Silent (No Prompts)" procedure if you will be setting up Company & Location name variables for better automation (recommended).
2. Import the procedures. More info on importing Kaseya VSA procedures can be found here.
   
   
3. You should now see the AutoElevate Agent Deployment procedures in the correct folder.

License Key Variable

1. Copy your license key from the AutoElevate Admin Portal.
   
   • Navigate to the "Settings" screen and click the "Copy to Clipboard" link on the "License Key" item in the "General Section".
2. Add your AutoElevate license key as a variable in the VSA Variable Manager. More info on the VSA Variable Manager can be found here.
   
   
   • Click the "Manage Variables" button:
     
     
     
     
   • Create a < New Variable > named AUTOELEVATE_LICENSE_KEY and paste the license key copied from the AutoElevate Admin Portal into the "Set Variable Value" box (select "Public" if you want other VSA users to be able to access this variable):
     
     
     
     
   • Select all of the "Org / Machine Groups" that you want this variable to apply to (you will typically want to "Select All" here) and press the "Apply" button: 
     
     
     
     

Company & Location Variables (Optional but recommended for BMS PSA integration users)

At this point, you could technically begin to deploy. You can input the Company & Locations names on each procedure execution, which may be good for one-off installations but for a more long-term sustainable approach (to avoid variation & misspellings in your inputs), it would be better to set up the appropriate variables to accomplish this automatically.

Why should I go through the extra steps of setting up these variables? If you don't setup the variables and don't input the names at procedure execution, then the script will by default pass along the "Org / Machine Group" name as the "Company Name", and it will default the "Location Name" as "Main". This will be faster in the short term but may not be desirable since the "Org / Machine Group" names can be quite unfriendly (ie. "aekaseyademoclientxyz123.root" instead of something like "AE Kaseya Demo Client XYZ 123")

More importantly, if you are using Kaseya BMS as your PSA, the "Company Name" & "Location Name" will need to match the "Account" & "Location" names in BMS in order for the "links" to be properly made and tickets to be properly created. Therefore, we recommend setting up the appropriate "AE_COMPANY_NAME" & "AE_LOCATION_NAME" variables for each "Org / Machine Group" in the VSA Variable Manager so that the defaults are not used.

Company Variable Setup

1. Click the "Manage Variables" button (just as you did earlier for the License Key).
   
   
2. Create a < New Variable > named AE_COMPANY_NAME and enter a friendly name for a specific Company into the "Set Variable Value" box (if using Kaseya BMS as your PSA integration, make sure the name matches the corresponding Account record in BMS) (select "Public" if you want other VSA users to be able to access this variable).
   
   
3. Select all of the "Org / Machine Groups" that you want this variable to apply to (you will want to only select the groups that apply to this specific Company) and press the "Apply" button.

Location Variable Setup (Only needed if using the BMS PSA integration for ticketing)

If you need to define unique "Locations" for specific "Accounts" (Companies), please use the following instructions:

1. Click the "Manage Variables" button (just as you did earlier for the License Key).
   
   
2. Create a < New Variable > named AE_LOCATION_NAME and enter a friendly name for a specific Location into the "Set Variable Value" box (if using Kaseya BMS as your PSA integration, make sure the name matches the corresponding Location record in BMS) (select "Public" if you want other VSA users to be able to access this variable).
   
   
3. Select all of the "Org / Machine Groups" that you want this variable to apply to (you will want to only select the groups that apply to this specific Location) and press the "Apply" button.

If you only have a single "Location" under each "Account" in BMS that uses a common name, then you can create a variable using the steps above, but instead of only selecting specific "Org / Machine Groups", use the "Select All" button to add it for all groups.

You're ready to deploy!

Congratulations, your AutoElevate Agent Deployment Procedure is ready to use. Schedule it to run and watch your Companies, Locations & Computers show up in the AutoElevate Admin Portal!