View in Browser You can change how you want ThreatLocker to create Policies while your endpoints are in their initial Learning Mode.   Create Group Policies By default, computer groups will be set to 'Create group Policies', meaning the Applications that are found are learned across an entire computer group. For example, if ThreatLocker finds Notepad++ on one of your computers, it will automatically create a Policy to allow it on all computers in that group.

Note: This can either be done on first deployment, or by using an existing deployment script for ThreatLocker on a scheduled basis. If already in possession of an existing deployment script, the section 'ThreatLocker Automate Deployment Script' can be skipped. Creating the Opt-in EDF: Open ConnectWise Automate. Navigate to System-> Configuration->Dashboard->Config->Configurations->Additionals Fields. We will create a New EDF that Opts in an Organization at the Client Level.

View in browser This article is based on documentation from Microsoft and has not been verified by the ThreatLocker team.  Source: https://docs.microsoft.com/en-us/mem/intune/apps/intune-management-extension  Log into the ThreatLocker portal. Make sure you are managing the correct organization, or switch organizations using the Organizations page.  Click on the Computers page. Select Install New Computer. Download the PowerShell Script for the group you are installing. Add into Microsoft InTune.

Threatlocker identifies computers based on two registry keys that are created when the endpoints check into the portal. When we configure the base image for the VDI, we have to make sure the values for the "Computer ID and the Computer Auth" registry keys are set and the process that creates the new machines also copies those original keys to the new VMS to avoid having new machines created in the ThreatLocker Portal every time the VDI environment is destroyed.

View in browser The following steps demonstrate how to deploy ThreatLocker to your clients utilizing a PowerShell script via Atera. Important Notes: PowerShell 4.0 is required for this method to work. It is best to run the script found below against clients one at a time, as you need to pass the Organization Name into the script as a variable. Creating the Script In Atera: Navigate to the Admin area.

View in Browser The ThreatLocker agent can be deployed using ConnectWise Control provided your license supports the ability to run commands. You will need to download the PowerShell script located here. This is the script for Ninja, and will need to be modified by adding the following 3 lines at the top for ConnectWise use: #!ps #maxlength=50000   #timeout=90000   Then you need to modify the script in the following 2 areas:

You may view this article in your web browser, here.  The following steps demonstrate how to deploy ThreatLocker to your clients utilizing DattoRMM. Log into your DattoRMM. Navigate to Components > New Components. Select the 'Applications' Category. Name the new component. Edit the description. Select 'Save'. Select the star on the top left-hand side to toggle favorites (This will allow you to make it a quick job).

View in browser Deploying ThreatLocker using SyncroRMM uses a PowerShell Script. The script found below deploys the ThreatLocker agent and automatically creates organizations in the ThreatLocker portal if they do not already exist.  Adding a PowerShell Script Log into your SycroMSP Account Select Scripts from the Top Menu Select the New Script Button Enter a Name for the Script (E.g. ThreatLocker Deployment Workstations) Mark the Script as a Favorite Check "

View in browser 1) Download the startup script. 2) Unzip the script and open it in the text editor of your choice.   3) Add the deployment unique identifier of the parent (Getting your Unique Identifier from ThreatLocker) to the "Key" variable on line 21. 4) Add the organization identifier of the child (on the organizations page) to the "Company" variable on line 21.  Note: If you are deploying to the parent organization, or you do not have any child organizations, simply use the organization unique identifier of the parent (on the organizations page).

View in Browser ThreatLocker is now available as a Component in the datto ComStore, further simplifying the deployment of ThreatLocker using datto RMM. You will need to retrieve your company's Unique Identifier from the ThreatLocker portal before proceeding. In the ThreatLocker portal, navigate to the 'Computers' page of your organization. Select the 'Install New Computer' button at the top. This will open a window containing your Unique Identifier as highlighted in the screenshot below.

View in Browser. The following steps demonstrate how to deploy ThreatLocker to your clients utilizing ConnectWise Automate. The script given below will attempt to match your clients in Automate to your Organizations in ThreatLocker. Should there happen to be no match found, the script will create a new Organization for you in the ThreatLocker Portal. Note: We advise running this against a single PC first as the naming convention in Automate can lead to unexpected results.

View in browser Log into the Continuum Portal. Navigate to 'Devices' > 'Computers' on the sidebar menu. Select the desired organization you are looking to deploy to. Select Run. Select Command Prompt (CMD) Script from the drop-down menu. Select the desired device(s) > Continue to Setup. Paste in the Deployment Script in the Command Prompt Script. Get the latest Deployment Script for Continuum here.

View in browser Download the latest version of our deployment scripts here Note: Export the XML file from the downloaded ZIP Overview This article will cover the steps to import the ThreatLocker Deployment script into your Kaseya VSA instance. The script will attempt to match your clients in Kaseya to your Organizations in ThreatLocker, and will create a new Organization if it doesn't match. It will also place the devices into either the Workstations or Servers group in ThreatLocker dependant on the operating system.

You may view this article in your web browser, here. The following steps will guide you in deploying ThreatLocker to your clients via N-able RMM.  Creating the Deployment Script Download the latest deployment script here. This contains a .amp file within a zip folder. Login into your N-able RMM dashboard. Select Settings > Script Manager. Select New. Input a Name and Description. Check the "

View in Browser Creating the Deployment Script Log into your N-Central dashboard. Be sure you are managing the root of the N-Central System  (Structure may vary slightly, depending on the version of N-Central ) Select Configuration > Scheduled Tasks > Script/Software Repository. Select Add > Automation Policy.  Download the latest deployment script here. Browse to the .amp file you have downloaded. Select Save.

You may view this article in your web browser, here. The following steps demonstrate how to deploy ThreatLocker to your clients utilizing a PowerShell script via NinjaRMM. This method entails setting a scheduled task at the Policy Level within NinjaRMM. Note: Powershell 4.0 or greater is required. All organizations that do not exist within ThreatLocker will be created upon succesful execution of this script. Adding the PowerShell Script Login to NinjaRMM Navigate to Configuration > Scripting > Create New Script Copy and paste the deployment script located hereinto the NinjaRMM Editor.