Documents on deploying software and services in various environments
View all tagsThis document provides a comprehensive guide on the implementation of the Automate Deploy Group Policy Object (GPO) for ConnectWise Automate. It explains how to create both a startup script GPO and a scheduled task GPO to effectively deploy the Automate agent across devices in a network. The document includes details on user parameters, dependencies, implementation steps, and frequently asked questions.
This document outlines a script that clears existing Disk Monitors from an agent and reinstalls new Disk Monitors, intended for use during the initial deployment of service plans for servers and workstations. The process saves approximately 5 minutes by automating the removal and reinstallation of disk monitors.
This document describes a monitor that detects agents based on the presence of the "Compliance Management Installer Key" and ensures that deployment is enabled. It highlights the importance of not excluding any locations or computers from this monitoring process.
This document provides detailed instructions for the deployment and uninstallation of the Network Glue Collector, including associated scripts and monitors. It outlines the necessary steps for implementation and configuration within the ConnectWise Automate environment.
This document provides a comprehensive overview of the GPO Import Process, detailing the available Group Policy Objects (GPOs) for deployment through the specified script. It includes dependencies and a description of the columns in the dataview.
This document provides details on a script designed for the automatic deployment of BitLocker initialization to agents detected by the Internal Monitor for BitLocker. It includes sample runs, dependencies, user parameters, and output details.
This document provides a comprehensive guide on the SnapAgent installation script, detailing its dependencies, variables, and ticketing features for efficient deployment and monitoring. It includes sample runs, variable documentation, and logging information to assist in successful implementation.
This document outlines a monitor designed to detect online Windows agents where the SnapAgent is not installed. It includes dependencies on specific EDFs for installation confirmation and exclusion criteria, as well as ticketing control through the SnapAgent Installer script.
This document outlines the steps to deploy the Cyrisma Censor Application using a custom task in ConnectWise Automate, including script implementation, scheduling, and logging.
This document outlines the steps to create a monitor that generates a ticket for CRI Agent deployment failures, ensuring timely alerts for critical non-impact issues.
This document contains the custom fields that are used in the CW RMM to Ninja migration
This solution is built to perform the CW RMM to Ninja migration.
This document outlines a PowerShell script designed for creating and managing the Automate agent deployment via Group Policy Objects (GPO). It includes steps for installation, repair, and replacement of the agent, ensuring that it remains up-to-date with a new Installation Token. The guide targets Domain Controllers and provides detailed implementation steps, variable definitions, and expected outputs.
This document provides a comprehensive guide on utilizing the Template - MSI Deployment for creating a software installation script that employs a .msi file. It includes detailed steps for exporting, duplicating, renaming, and configuring the script, as well as setting dynamic properties and ensuring successful deployment.
This document provides a comprehensive guide on deploying, monitoring, and auditing the Cyrisma sensor application, including associated tasks, custom fields, and monitoring strategies.
This document outlines the procedure for deploying Dell Command | Update to an endpoint. It includes steps for downloading the software, installing it, and performing a scan and update based on the configuration specified in the DCU_Config.ps1 file. The document also provides example logs and dependencies for the procedure.
This document outlines the purpose and functionality of the internal monitor designed to detect Windows and Macintosh machines that are missing the Huntress Agent and have deployment enabled. It includes details on dependencies, client-level, location-level, and computer-level EDFs, as well as the alert template for deploying the Huntress Agent.
This document outlines a monitor designed to detect Windows machines that are missing the Perch Log Shipper. It details the necessary client-level EDF settings required to initiate the installation on targeted machines, including the deployment and installation codes needed for successful implementation.
This document provides a comprehensive guide on deploying the Perch Log Shipper on Windows machines, detailing the necessary client-level and location-level EDFs, dependencies, and output generated during the installation process.
This document outlines the steps to deploy Perch Log Shipper on Windows machines, detailing associated scripts and monitors needed for effective implementation.
This document outlines the process to deploy the Rapid Fire Compliance Management software using client-level EDFs with specific location and computer-level exclusions. It includes associated scripts, monitors, and implementation steps to ensure a successful deployment.
This document outlines the creation of a dynamic group for machines eligible for Threatlocker deployment that do not currently have Threatlocker installed. It details the criteria for both Windows and Mac systems, ensuring proper identification and grouping for deployment.
This document outlines the steps to automatically deploy the DNS filter agent to client machines using associated scripts and monitors in the ConnectWise Automate environment. It includes detailed instructions for setup, implementation, and ticket creation.
This document outlines the steps to create a dynamic group for DUO Authentication for Windows Login Deployment in ConnectWise RMM. It details the necessary custom fields and conditions required for the group setup.
This document provides a comprehensive guide on creating a dynamic group for agents where DUO Auth for Windows Login is installed. It includes details about the group creation process, dependencies, and criteria for the group.
This document provides a comprehensive guide on how to install or update the DUO Authentication Proxy application to the latest version. It includes sample runs, dependencies, task creation steps, and implementation guidance to ensure successful deployment.
This document provides a comprehensive guide on setting up a dynamic group for the DUO Security Authentication Proxy deployment in ConnectWise RMM. It details the necessary custom fields, group creation steps, and criteria for agent inclusion based on specific conditions.
This document provides a comprehensive guide to automate the installation and update of DUO Authentication for Windows Login, including the necessary custom fields, device groups, and tasks for efficient deployment and auditing.
This document outlines the process for automating the installation and update of the DUO Authentication Security Proxy, including the necessary custom fields, dynamic groups, and tasks for effective management and auditing.
This document details a custom field used to store the result of the SentinelOne deployment task within ConnectWise RMM. It includes dependencies, field details, and a screenshot for reference.
This document explains how to create a custom field to exclude a machine from Huntress Deployment, specifically utilized by the ConnectWise RMM Device Group for deploying Huntress. It includes images and detailed instructions for setting up the custom field as a flag at the endpoint level.
This document provides details on setting a custom flag to exclude an endpoint from SentinelOne deployment. It includes information on dependencies, field names, and editable options to ensure proper configuration.
This document provides a comprehensive guide for deploying and managing the Huntress Agent on both Windows and macOS machines, including installation, uninstallation, and repair processes, along with associated content for effective monitoring and management.
This document provides a comprehensive guide on deploying Webroot to agents using the Webroot site keycode client-EDF. It includes sample runs, dependencies for obtaining the necessary Webroot information, detailed descriptions of the required EDFs, and the expected output of the script.
This document provides an implementation of the agnostic script for deploying Microsoft Teams. It includes a sample run and output details, focusing on the software installation process through an agnostic approach.
This document outlines an internal monitor that detects all computers whose associated client has the Enable Webroot Deployment EDF checked, while ensuring there are no associated location or computer exclusions. It includes dependencies and target operating systems.
This document details a script that is part of a GPO deployment process, capable of generating a silent installer URL. It can be executed standalone or as part of a larger deployment strategy. The script saves time by automating the installer generation process and requires specific dependencies to function correctly.
This document presents comprehensive information about Network Probes (Gen1 and Gen2), including details on subnet settings, scan configurations, and deployment options. It also provides recommendations for the best computer to use when a network probe is not present at a location.
This group contains the endpoint where the Ninja deployment failed.
This group contains the endpoint where the Ninja Deployment succeeded.
This group contains the endpoints where the Ninja RMM deployment is enabled, the software "NinjaRMMAgent" is missing, and the custom field "Ninja Deployment Result" is blank.
This script deploys the NinjaRMMAgent to MAC OS, based on the article provided below: https://ninjarmm.zendesk.com/hc/en-us/articles/27524794230669-NinjaOne-Agent-Installation-Agent-Tokenization. It depends on the Authorization token, which will be kept in the company or site custom fields.
This script deploys the NinjaRMMAgent to Windows-supported OS. It depends on the Authorization token, which will be kept in the company or site custom fields.
This document outlines a task to validate whether the Cumulative Update installed by the Out of Date Cumulative Update (Autofix) task succeeded after a reboot. It includes sample runs, dependencies, variable definitions, task creation steps, and deployment instructions.
This document outlines the setup of an internal monitor for detecting the online Windows agent with SonicWall NetExtender installed, facilitating upgrades and excluding specific locations or agents as needed. It details dependencies and integration with other monitors for effective management.
This document describes the Webroot Keycode Verification Monitor, which checks for online agents where the script has not run in the last 30 days and ensures that Webroot is installed and deployment is enabled. It also covers dependencies and ticketing setup for keycode mismatch detection.
This document outlines the configuration of a dynamic group for deploying the SentinelOne agent across Windows, Linux, and Mac machines, including the necessary dependencies and criteria for group membership.
This document provides a comprehensive guide for deploying the SentinelOne agent on Windows, Linux, and Mac machines, including associated custom fields, tasks, and monitoring setups.
The document provides step-by-step instructions for creating an ImmyBot software based on a ProVal document.
This document outlines a solution for deploying Webroot and auditing keycode status for partners experiencing issues with the Webroot plugin. It includes associated scripts, monitors, and dataviews necessary for effective implementation and management of Webroot security.
The document provides step-by-step instructions for creating an ImmyBot task based on a ProVal document.
This document outlines the process for deploying the Threatlocker agent on both Windows and Mac operating systems. It includes necessary custom fields, device group creation, and task deployment steps to ensure successful implementation.
This solution is designed to configure the automatic deployment of the Threatlocker Agent on Windows and Macintosh machines that are missing the agent, using the NinjaOne platform.
This document outlines a solution for managing and deploying ProVal's Update Orchestrator to prevent unintended patching and rebooting of machines. It details the use of a custom task, device group, and monitor to ensure controlled updates.
This document outlines the procedures for managing Webroot Software within ConnectWise Automate, including installation, configuration, and auditing processes. It covers system requirements, plugin installation, and automatic deployment strategies for both Windows and macOS systems.
This document outlines the setup and dependencies for the Webroot Keycode Verification Monitor, which checks for online agents that have not run the specified script in the last 30 days, ensuring that Webroot is installed and deployment is enabled.