595 docs tagged with "Software"

This document provides a step-by-step guide on how to remove obsolete PowerShell monitors in ConnectWise Automate by executing SQL queries to manage group agents effectively.

This document details a dataview that displays data from Automate and the Active Directory Plugin, focusing on the last contact status of agents. It assists in verifying if a machine is offline by checking its last communication with either system.

This document outlines the process of alerting domain users when their passwords are set to expire within the next 7 days. It includes associated content, implementation steps, and troubleshooting FAQs to ensure users receive timely notifications.

This document provides a detailed overview of the Active Directory Dataview for Automate, including the columns displayed and the information retrieved from the Active Directory Plugin. It covers machine detection based on agent installation, last logon details, and more.

This document outlines the purpose and functionality of a monitor set designed to identify computers lacking specified Wi-Fi profiles. It details how the monitor set interacts with the relevant dataview and triggers scripts to ensure proper Wi-Fi configuration on managed Windows workstations.

This document provides a detailed overview of a dataview that displays machines where the Microsoft update policy is not set, including various columns that provide insights into the client, location, computer details, and patching status.

This document provides a summary of retired machines within the last 30 days, displaying relevant comments and details such as client name, location, machine name, operating system, manufacturer, internal IP address, and the date of retirement.

This document provides a detailed overview of a dataview designed to audit queued and running scripts in ConnectWise Automate. It outlines the key columns available in the dataview, including script name, current running status, script ID, total execution count, and running percentage.

This document provides a detailed overview of the process to install Adobe Acrobat 2022, including a sample run, dependencies, and the steps involved in the installation process.

This document details a script that can either list available updates or execute updates for Adobe Creative Cloud applications on the specified machine, saving significant time through automation.

This document outlines an internal monitor designed to detect the presence of Adobe Flash on systems where the agent is installed. It includes necessary dependencies and is targeted for Windows operating systems.

This document describes an Autofix script designed to uninstall Adobe Flash Player from target machines using multiple methods. The script aims to save time by automating the uninstallation process and includes options for ticket creation in case of failure.

This document details the procedure for uninstalling Adobe Flash from an endpoint, including logging examples, detection processes, and utility dependencies. It outlines the steps taken during the uninstallation process and confirms the successful removal of the software.

This document provides a detailed overview of the Adobe License information dataview, including its dependencies, columns, and SQL representation for retrieving the relevant data from the database.

This document provides an overview of a dataview designed to locate duplicate machines within ConnectWise Automate. It explains the importance of identifying duplicates, particularly in relation to licensing issues, and outlines the limitations regarding serial number retrieval from various manufacturers.

This document provides a comprehensive dataview that displays the internal drive health status for all ConnectWise Automate agents, detailing various metrics such as drive size, free space, fragmentation, and more.

This document provides a summary of a monitor that identifies machines lacking the latest Automate agent. It determines the maximum agent version by querying the database for the highest version installed based on the operating system. An Autofix feature is available to attempt updating agents.

This document provides guidance on controlling the Kaseya App Blocker by updating the Kaseya INI file. It details the necessary steps and considerations for effective management of application blocking within the Kaseya environment.

This document outlines a monitor designed to update applications based on the provided PackageID, Source, and Application Name. It includes setup instructions, dependencies, and target specifications for effective implementation.

This document outlines a script designed to gather and store the latest version of applications supported by Winget in system properties, using the PackageID as the identifier for each application.

This document provides an overview of the Dataview that displays information gathered by the CWM - Automate script for active and managed configurations. It includes details about dependencies, columns, and their descriptions to help users understand the data presented.

This document outlines the solution for installing and reporting the most recent Cumulative Update (CU) on computers that have not had a CU installed in the last 75 days. It details the implementation of the Reboot Prompter solution for managing reboots on workstations and servers, and specifies the supported operating systems.

This document provides a detailed overview of a dataview that displays all scripts along with their defined saved automation time, including information on script folders, names, client-only status, and notes.

This document provides a detailed overview of a dataview that lists all scripts in the ConnectWise Automate environment, including their folder details, types, execution permissions, and performance metrics. It also summarizes script execution over a defined retention period.

This document provides details about the Automate Database Maintenance Solution script, which handles the cleanup of specific database tables, particularly focusing on the h_agenthistory table. It includes information on required variables, sample runs, and output logging for effective database management.

This document provides a comprehensive guide on using the Offboarding Agent Removal Script in ConnectWise Automate. It details the global and user parameters, the process of checking agent status, and the removal of specified software products. The script is designed to facilitate the offboarding process by managing agent removal efficiently, including ticketing options for failures.

This document outlines the purpose and implementation of tracking estimated time saved for clients through ProVal automation. It includes associated content, initial implementation steps, and content integration instructions for agent procedures, policies, and monitors.

This document provides an overview of how to track the approximate amount of time saved for clients due to ProVal Automation. It includes details on monthly and cumulative values, along with dependencies and field descriptions.

This document provides comprehensive information regarding the servers that have Azure AD Connect software installed, including the specific versions of the software. It outlines associated content such as policies, procedures, and reports related to the Azure AD Connect Version Audit, along with implementation steps for setting up the necessary configurations.

This document outlines the policy for scheduling scans of server endpoints for Azure AD Connect software, ensuring the version number is gathered effectively. It includes dependencies, details of the policy, and relevant configurations for implementation.

This document provides a comprehensive report on all endpoints where the xPVAL Azure AD Connect Version Custom field is populated with a valid software version. It includes dependencies, report type, layout, and sample report details for effective analysis and auditing.

This document provides a comprehensive guide on installing BitDefender Endpoint Security Tools on endpoints, detailing the installation process, logs, dependencies, and the overall procedure.

This document provides a comprehensive guide for completely removing BitDefender Endpoint Security Tools from an endpoint using an agent procedure. It includes implementation steps, optional variables, and the process for ensuring proper uninstallation, along with logging and error handling.

This document provides an overview of the Password Manager Lockdown Status for computers monitored by the Lockdown Browsers Password Manager. It details whether the password manager has been successfully deactivated for installed browsers and identifies any failures in the process.

This document details a dataview that populates the Click-to-Run Office version, auto-update status, and update channel information on a machine, along with basic system information. It includes dependencies for data collection and monitoring scripts.

This document outlines the procedure for checking the presence of the Senteon Agent on an endpoint and updating a custom field named cPVAL Senteon Installed with the status. It includes dependencies, implementation steps, and expected output, ensuring all necessary components are in place for successful execution.

This document provides an overview of a script that installs Chocolatey and manages the installation or upgrade of specified applications. It includes details on dependencies, user parameters, and the process flow, ensuring successful application management through automation.

This document provides a comprehensive guide on using a script to install various versions of Microsoft Office through the Choco Microsoft Office Deployment package, detailing parameters, dependencies, and sample runs.

This document provides a comprehensive guide on using the Chocolatey Wrapper to install and upgrade various software packages efficiently. It covers commands for installing single and multiple packages, upgrading existing installations, and managing exceptions and custom packages in the library.

This document outlines the process of using the Foil wrapper for Chocolatey to install applications. It includes a detailed example of an agent procedure log and the steps involved in the installation process, ensuring that users can successfully deploy applications using Chocolatey and Foil.

This document outlines the process for uninstalling an application using the Foil wrapper for Chocolatey. It includes a summary of the procedure, example logs, dependencies, and a detailed step-by-step process for successful execution.

This document provides a script designed to automate the update process for Chromium-based browsers including Google Chrome, Microsoft Edge, Brave, and Opera. The script can optionally create tickets for failures, enhancing maintenance workflows.

This document provides a comprehensive guide on installing extensions on popular Chromium-based browsers including Chrome, Edge, Brave, Vivaldi, and Chromium. It includes user parameters, task creation steps, and sample scripts for effective implementation.

This document provides a detailed guide on how to remove extensions from popular Chromium-based browsers including Chrome, Edge, Brave, Vivaldi, and Chromium. It includes user parameters, task creation steps, and a sample PowerShell script for automation.

This document outlines an Automate implementation of a script designed to remove enforced homepage settings from Chromium-based browsers, specifically Google Chrome and Microsoft Edge. It details the parameters, sample runs, and dependencies for effective execution.

This document provides an overview of the Automate implementation of the agnostic script for clearing the Chromium cache. It includes user parameters, sample run images, and output details for effective software configuration management.

This document details the process of auditing Chromium extensions installed on an endpoint, including example logs and dependencies. It provides insights into the execution of the audit script and its output, helping administrators maintain control over browser extensions.

This document outlines the procedure to clear enforced homepages in Chromium-based browsers. It details the process of removing specific registry keys that control homepage selection, new tab page control, and session restoration, ensuring a clean browser experience.

This document provides a comprehensive guide on installing the Cisco Secure Client along with necessary configurations and parameters required for a successful installation. It includes details about using URLs or managed files for the installer and outlines the required values for Umbrella installations.

This document provides a comprehensive guide on installing various Cisco Secure Client modules on Windows and MAC machines, including prerequisites, dependencies, user parameters, and detailed instructions for execution and troubleshooting.

This document provides a comprehensive guide for implementing the Cisco Secure Client Package Installation via ConnectWise RMM. It details prerequisites, dependencies, script creation steps, and module definitions to ensure a successful installation of the Cisco Secure Client and its components.

This document provides detailed instructions on how to store and use the parameter for installing the Cisco Secure Client package through a company-level custom field. It includes dependencies, sample values, and outcomes for various installation configurations.

This document provides a detailed overview of a script designed to silently remove the OpenDNS Umbrella Roaming Client. It includes sample run visuals, global parameters, and process steps for effective uninstallation.

This document provides a detailed overview of a script designed to install User-Based Cisco Webex on Windows machines, including sample runs, output logs, and ticketing information for installation failures.

This document provides a script for clearing the cache of installed Microsoft Teams on Windows machines. It includes a caution about forcibly terminating the application if it is running, and instructions on how to restart it manually afterwards.

This document outlines the steps to perform a Browser Saved Password Audit or Clearance using a custom PowerShell script. It includes sample runs, implementation details, and deployment instructions to ensure secure management of saved passwords across different web browsers.

This document describes the custom fields used in the creation of Dynamic Groups for Browser Saved Passwords and their application in the Task for Clearing and Auditing Browser Saved Passwords. It includes details about each field, its purpose, and implementation steps.

A thorough examination of Windows 10 computers and their patching status for each client, including details on supported and unsupported systems, patch compliance, and the status of approved, denied, ignored, installed, missing, and failed patches.

This document outlines the necessary organization name required for deploying Threatlocker. It emphasizes the importance of matching the name with the existing organization in the ThreatLocker portal for successful deployment.

This document outlines the procedure for updating third-party applications using Winget. It includes implementation steps, configurable parameters, and dependencies necessary for the successful execution of the Winget-AutoUpdate solution on endpoints.

This document provides an overview of a client script that manages remote monitors for CPU temperature monitoring. It ensures that installed monitor sets align with the configuration in the EDF and System properties, removing or updating monitors as necessary.

Select Operating System to deploy MSP 360 Online Backup Agent.

If enabled, this option will automatically send a push request to the user's device when they attempt to log in. The default value is blank, which requires the user to manually request the push.

Select the required platform to enable Duo to auto-deploy.

Select Yes to exclude the device/location from DUO deployment automation.

If enabled, it will control whether offline access is permitted. For Duo, offline access allows users to authenticate without a real-time connection to Duo’s service, usually by using previously generated passcodes or other offline methods.

This determines the behavior when Duo's service cannot be reached. If enabled, the system will allow the user to log in (fail open). If disabled, the system will deny access (fail closed). The default is to fail closed.

The Host Key or API Hostname, which is the endpoint in Duo’s service that your application communicates with. This hostname is also found in the Duo Admin Panel and is necessary for setting up the integration.

This is a unique identifier for your integration with Duo’s service. It’s used to link the authentication requests from your application to the correct Duo account.

When enabled, Duo authentication is required only for remote logins via RDP. If not, Duo authentication is required for both console and RDP logins. The default is disabled, meaning Duo protects both.

This is a sensitive piece of information, akin to a password, used in conjunction with the IKEY. The SKEY is used to sign communication between your application and Duo’s service securely.

If enabled, it allows smart card login as an alternative to Duo authentication. If not, it disables the Windows smart card provider. The default is blank, which does not allow smart card login without Duo approval.

0 to disable Offline Access for User Elevation; 1 to enable Offline Access for User Elevation

0 to prevent Offline Enrollment during User Elevation; 1 to Enable Offline Enrollment during User Elevation

0 to respect existing Duo authentication control around logon; 1 to Disable Duo at logon and only prompt during User Elevation; 2 to enforce Duo at logon and User Elevation

The username format sent to Duo. One of: 0 for sAMAccountName (narroway), 1 for the NTLM domain and username (ACME\narroway), or 2 for the userPrincipalName (narroway@acme.corp)

Enable this custom property to require Duo after smart card primary logon, or not to allow smart card logon without Duo approval afterward.

This document explains how to exclude Malwarebytes from the machine level by setting a specific configuration field. It provides details on the relevant field name and its usage within the system.

This is the Account Key that determines which Huntress Account an Agent should be associated with.

Choose the operating system to activate the auto deployment of the Huntress Agent. Auto deployment can be enabled for Windows machines only or for both Windows and Macintosh computers.

Enable this custom field to exclude the location or device from the automatic installation of the Huntress Agent.

By default, the Huntress Organization key is the name of the Organization. Set this custom field if it's different for the Organization.

Tags to assign to the agents.

MBS backup agent URL. Copy the link from MBS portal in Downloads section.

This document provides details on the custom field used to determine if the Senteon Agent is installed on an endpoint. It includes associated content, custom field names, types, and expected output values for the agent status.

This document describes a custom field that tracks the user status on machines, detailing its dependencies and specific field information relevant to machine management.

Choose Yes to exclude the Location/Device from the automatic Vulscan Discovery Agent deployment setup.

Select the operating system to enable Vulscan Discovery Agent deployment.

Specifies the install key for the VulScan Discovery Agent. The Install Key allows agents to be associated with the organization during the agent installation.

This document provides a comprehensive guide on how to create a shortcut in the Public Desktop folder using a script. It includes sample runs, user parameters, implementation steps, and detailed instructions for setting up the task in the Script Editor.

This document provides a comprehensive guide on creating remote monitors for critical drive space on Windows machines, detailing the implementation process, user parameters, system properties, and extra data fields necessary for effective monitoring and alerting.

This document provides a detailed guide on how to install Crowdstrike on an agent using a script. It covers requirements, variables, global parameters, the installation process, and expected output logs.

This document details a script that utilizes the Crystal Disk Info program to automatically assess hard drive health on computers. It updates the Hard Drive Status field in Extra Data Fields with results indicating whether the hard drive is functioning normally or reporting issues. The script also includes ticket creation functionality for detected failures.

This document provides an overview of the Cumulative Update compliance score for Windows computers within the Automate environment. It details the data display for managed patch policies, including the age of updates and the scoring system used to assess compliance across production patching groups.

This document provides a comprehensive overview of the status of the CVE-2016-2183 vulnerability on agents where the remediation script has been deployed, including details on the operating system, last contact, and vulnerability state.

This document provides a detailed overview of a script designed to perform a fresh installation or a removal and reinstallation of the CW Control agent on a Mac device, including the necessary variables and process steps involved.

This solution details the deployment and removal solution of the Malicious Software Removal Tool and provide its implementation process

This document provides a comprehensive guide on how to collect and integrate data from the Unifi controller into the ConnectWise Automate environment, including associated scripts and custom tables for efficient data management.

This solution contains Copilot disabling/uninstall and revert optional addition to revert the copilot back if required

This solution details the deployment and removal solution of the Malicious Software Removal Tool and its implementation

This article outlines the step-by-step process to add the Windows Feature Update option in the Self Help menu, enabling the installation of the latest feature pack for Windows 10 and 11 through a script.

This document outlines a solution to restore the functionality of ConnectWise Automate agents that may be broken or frozen. It details the components involved in automatically identifying and fixing issues, as well as the importance of the CW RMM+ plugin for successful implementation.

This document describes a script designed to store the latest version of SonicWall NetExtender in the system properties, ensuring that the most up-to-date version is easily accessible and manageable.

This document provides a detailed guide on configuring the RMM+ Plugin, including steps to create sessions for machines that have not checked in for a specified number of days. It covers the necessary settings in the client control portal and the Automate control center, ensuring a seamless integration and management of remote sessions.

This document provides a script for installing user-based Cisco Webex on Windows machines, including sample runs, output logs, and error handling for installation failures.

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 installing the CyberCNS agent on a computer, detailing the requirements, variables, global parameters, and the process involved in the installation.

This document outlines the creation and management of dynamic groups for deploying and auditing the Cyrisma Sensor within ConnectWise RMM. It details the necessary criteria for each group and their respective functions in monitoring the deployment status and installed agents.

This document describes a script that creates a distinct copy of the Dataview CSV file each time it runs, saving it to a user-defined folder instead of overwriting the existing file. It does not send any emails and includes additional user parameters for customization.

This document provides a detailed procedure for uninstalling Datto RMM from both Mac and Windows endpoints, including example logs and dependencies for successful execution.

This document provides an overview of the internal monitor that detects computers with daytime patching enabled and identifies available patches for installation. It includes dependencies, target scope, and alert template details.

This document outlines a script designed to facilitate the installation of Windows updates on computers using the Deep Freeze Tool. It verifies the system state, pushes updates, and manages the transition between THAWED and FROZEN states to ensure a seamless update process without disrupting user experience.

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.

Installs, updates, or executes Dell Command | Configure (DCC) on Dell workstations, ensuring the latest version is present and providing command-line automation for DCC operations.

Installs, updates, or executes Dell Command | Update (DCU) on Dell workstations, ensuring the latest version is present and providing command-line automation for DCU operations.

This document provides an overview of a script designed to execute commands using the Dell Command Configure application. It outlines the installation requirements, sample runs, dependencies, user parameters, and the process involved in utilizing the script effectively.

This document details a script that installs Dell Command Configure version 3 or 4 based on the system specifications. The script saves approximately 10 minutes of manual installation time by automatically determining the appropriate version and executing the installation process, including verification and cleanup tasks.

This document provides a comprehensive guide on installing the latest version of Dell Command | Update for Windows Universal using Winget. It covers command usage, exit codes, task creation, user parameters, and sample runs to ensure successful implementation.

This document provides an overview of a script that utilizes the Dell Command | Update application to manage updates on Dell Workstations. It covers installation, upgrade procedures, command line usage, and sample runs, along with user parameters and script states for effective management of system updates.

This document outlines the steps to detect Dell Dockstation on Dell workstations using associated scripts and monitors. It provides a comprehensive guide on implementation and configuration for effective detection and inventory management.

This document provides a script that checks for the installation of Dell SupportAssist software on Windows machines and uninstalls it if found. The process includes verification of the uninstallation, ensuring that the software is no longer present on the system. The automation is designed to save time and streamline the management of software on Windows devices.

This document provides a comprehensive guide for installing the HPE Insight Management Agent on Windows HP machines. It includes details on downloading the installer, global parameters for ticket creation, output logs, and ticketing information in case of installation failure.

This document outlines the steps to create a dynamic group in ConnectWise RMM for filtering Windows machines where the Huntress agent is not installed. It details the necessary dependencies, criteria for filtering, and the process to save the group configuration.

This document outlines the creation of a dynamic group in ConnectWise RMM that filters MAC machines where the Huntress agent is not installed. It includes dependencies, criteria for group membership, and instructions for saving the group.

This document provides a comprehensive guide on a script that queries Cisco for the latest roaming client installation media and installs the software on target Mac or Windows devices. It includes implementation steps, dependencies, variables, and specific considerations for both operating systems.

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 outlines the steps to deploy Perch Log Shipper on Windows machines, detailing associated scripts and monitors needed for effective implementation.

This document provides a comprehensive guide on installing the QuickPass Agent on Windows machines, detailing the necessary prerequisites, parameters, and configuration settings required for a successful installation.

This document provides a comprehensive overview of the script used to deploy the Rapid Fire compliance management application, including prerequisites, variables, user parameters, and ticketing integration.

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 process to detect computers that are missing the Teams Machine-Wide Installer application. It includes details on suggested limits, alert styles, and implementation steps for effective monitoring of Windows workstations.

This monitor detects both Mac and Windows agents that are missing Threatlocker agents.

Vulscan Discovery Agent Installation Script for macOS via NinjaRMM.

Triggers the auto-deployment script for Vulscan Discovery Agent on Macintosh machines where deployment is enabled.

Installs and configures the VulScan Discovery Agent on a Windows machine.

Triggers the auto-deployment script for Vulscan Discovery Agent on Windows servers where deployment is enabled.

Triggers the auto-deployment script for Vulscan Discovery Agent on Windows workstations where deployment is enabled.

Documentation for the Deploy-Teams command to install or update the Teams Machine-Wide Installer to the latest version.

This document provides a guide on how to create a desktop shortcut for all users on a Windows system. It includes sample runs, user parameters, and dependencies for successful implementation.

This document provides a comprehensive guide on creating a desktop shortcut in the Public Desktop using the New-DesktopUriShortcut script. It includes example logs, process details, and output files generated during execution.

This document details a script designed to initiate the Windows Upgrade Assistant for upgrading a target system to the latest version of Windows 10, including dependencies, variables, and the overall process involved in executing the upgrade.

This is a task to run Soji from the self help menu in the Ninja tray icon and display the results as a toast notification to the end user

This document outlines the procedure for uninstalling the Dot NET 7 Desktop Runtime application from endpoints, including detailed logs and steps for verification of successful uninstallation.

This document outlines the implementation of the Disable-DotNet3 agnostic script within ConnectWise Automate, providing a sample run and detailing the necessary dependencies for successful execution.

This document outlines the use of Client and Agent Level EDFs along with an internal monitor to ensure that DUO software is installed for all agents within a client. It includes sample runs, dependencies, global parameters, and the process for installation.

This document outlines the procedure for installing and upgrading Duo for Windows, including detailed logs of the execution steps and their statuses. It provides insights into the commands used, the success of each step, and the overall effectiveness of the installation process.

This document outlines a monitoring setup designed to identify computers with outdated versions of the DUO Authentication Proxy application installed. It includes specific details on check actions, server address, check types, and execution commands necessary for effective monitoring.

This document provides a detailed overview of a script designed to install or update the DUO Authentication Proxy application to the latest version. The script can be executed manually or as part of an Autofix from the specified monitor set in ConnectWise Automate. It includes sample runs, dependencies, variables, and ticketing information for handling update failures.

This document provides detailed information about the custom fields used in the DUO Auth Proxy Deployment Solution, including dependencies, field types, and step-by-step instructions for creating custom fields within the system.

This document outlines a monitor designed to detect online Windows agents with outdated DUO Authentication for Windows Logon. It also identifies agents with specific client EDF settings and exclusions not applied at the location or computer level.

This document outlines the implementation of a monitor designed to fetch the latest version of DUO Authentication for Windows. It updates a system property with the latest version available through WinGet, allowing systems to identify outdated installations. The monitor is intended for global use and updates monthly.

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 provides a comprehensive guide on updating the Duo Authentication Proxy application to the latest version, including implementation steps and associated content for effective monitoring and execution.

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 solution is designed to configure the automatic deployment of the Duo Auth application on Windows and Macintosh machines that are missing the agent, using the NinjaOne platform.

Installs and configures the latest version of Duo Two-Factor Authentication for macOS.

Triggers the auto-deployment script for Duo on Macintosh machines where deployment is enabled.

This script will install or update DUO if the currently installed instance is older than the latest released version. It matches the hash of the installer from the official website before deploying it.

Triggers the auto-deployment script for Duo on Windows servers where deployment is enabled.

Triggers the auto-deployment script for Duo on Windows workstations where deployment is enabled.

This script performs the installation/upgrade of the DUO Desktop to the latest version.

This solution contains the content for the auto-deployment/on demand execution of the DUO Desktop application

This document provides a comprehensive guide on how to install or update DUO for Windows Login. The script checks if the currently installed version is older than the latest release, verifies the installer hash, and downloads the latest installer from the official DUO site before deploying it.

This document explains how to detect the system locale in Windows environments using a detection string. It highlights the importance of understanding locale settings for applications that depend on system outputs, particularly in scenarios where date formats and language settings vary by region.

This document provides an overview of how to include the PowerShell version in a serial key. It outlines the detection string used, the comparator, and the applicable operating systems for this method.

This document provides instructions on how to enable or disable the Edge Sidebar on a target machine, including sample runs, variables, and output details.

This document outlines the procedure for installing Egnyte on an endpoint, including how to manage custom fields for reboot requirements and rescheduling the installation process if necessary.

This document outlines the agent procedure for updating and installing the Egnyte software, including the steps taken to kill all Office applications prior to installation and prompting for a reboot afterward. The example agent procedure log provides detailed insights into the actions and results of the installation process.

This document provides a PowerShell script that enables Internet Explorer mode for a specific site within the Microsoft Edge browser. It outlines the necessary variables, user parameters, and the process for implementation, ensuring that users can easily configure their settings for seamless browsing.

This document provides an overview of whether the C2R Office Auto Update feature is enabled on machines, as gathered by the Microsoft 365 Click-to-Run Get Details task. It includes details on the relevant field, its level, type, default value, and editability.

This document provides detailed information about the C2R Office version installed on a machine, as gathered by the Microsoft 365 - Click-to-Run - Get Details task. It includes a summary, detailed field descriptions, and relevant screenshots.

This document details the storage of the install date for the latest cumulative update performed by the Out of Date Cumulative Update (Autofix) task. It includes a table describing the relevant field properties and two screenshots for reference.

This document outlines the storage of the output from the Out of Date Cumulative Update (Autofix) task, detailing possible values, field names, and their descriptions. It also includes screenshots for reference.

This document provides a detailed overview of how to set the Update Channel for Microsoft 365 Click-to-Run using CW RMM. It outlines the available options, dependencies, and provides a table of relevant field details, along with screenshots for reference.

This document provides details on how to store the status of whether the Windows 11 Upgrade has failed after executing the Windows 11 Installer (Beta) task. It includes field definitions and screenshots for better understanding.

This document outlines the steps to update the Windows edition for Windows 10/11 workstations to Enterprise. It includes dependencies on KMS host setup, implementation details for exporting and importing components in Datto RMM, and expected output upon successful execution.

This document outlines the process for checking if a machine is running an evaluation copy of Windows, verifying available re-arms, and executing a rearm if necessary. It includes implementation steps for exporting and importing the component in Datto RMM, usage instructions, and expected output.

The eShare Install script facilitates the silent installation of eShare software on the target machine without requiring a reboot. This document provides a summary, sample run logs, dependencies, and the installation process.

This document outlines the process of deploying Evo Agent from CW Automate.

This document outlines an internal monitor designed to execute the Microsoft Office Click-to-Run Update script on online machines with Microsoft Office 365 installed. It ensures the update script runs regularly, executing after hours if not run in 15 days and during the day if not run in 30 days.

This internal monitor executes the Configure Winget Auto Update script on Windows machines where the solution is enabled. It detects changes made to the client-level EDFs and runs the script on the relevant computers. If a computer was previously included in the solution and then excluded, the script will be executed with the Uninstall parameter.

This document outlines the internal monitor that executes the Microsoft 365 - Click-to-Run - Get Details script on online machines with Microsoft Office 365 installed. It targets machines that have not run the script for over 14 days and selectively focuses on those under a Managed Mode policy in Automate.

This document outlines the process for executing a scheduled task that creates Winget Update All tasks on Windows 10 and 11 workstations. It details the necessary client-level and location-level EDFs for managing task initiation and exclusions.

This document outlines a monitor that executes the Sentinel One Settings Verification script every 14 days on Windows and Macintosh computers with the Sentinel Agent installed, processing up to 100 machines per hour.

This document outlines the internal monitor that executes the Software Configuration script for Microsoft 365 to set the update channel to Current on eligible Windows machines. It details the criteria for execution based on the status of the update channel, auto-update settings, and Click-to-Run Office version, along with the necessary dependencies and alert template for execution.

This document outlines the internal monitor that executes the Microsoft 365 Update Channel script on online machines with Microsoft Office 365 installed. It details the criteria for execution and dependencies required for proper functionality.

This document outlines a solution that alerts administrators if a computer or multiple computers have an incorrect Webroot Keycode assigned. It includes dependencies and target information for effective implementation.

This document outlines the process for executing the Winget App Audit script weekly on Windows machines, including dependencies and target settings for effective monitoring and management.

This document outlines a procedure to check if endpoints are domain-joined and reports on the detection of external DNS. It includes associated content for custom fields and agent procedures that facilitate this check.

This document outlines the process to classify Windows 10 and 11 computers that are on the latest build version while still having values in associated custom fields. It includes dependencies, criteria setup, and group creation steps for effective management in ConnectWise RMM.

This document explains how to create a custom field for tracking the reasons for failure during the installation of the latest feature update for Windows 10/11. It includes details on field configuration and usage.

This document provides a comprehensive overview of a script designed to search for files and folders on a computer. It allows users to specify a search term using the "ToSearchFor" parameter, supports regex input for advanced searching, and details the process, dependencies, and output of the script.

This document provides a comprehensive guide on using a PowerShell script to install and optionally enforce a specific extension in Mozilla Firefox, detailing dependencies, user parameters, and the process involved in ensuring a successful installation.

This document provides a detailed overview of a script designed to remove and optionally block a specified extension in Mozilla Firefox. It includes information on dependencies, user parameters, and the processing steps involved in executing the script, ensuring users can effectively manage Firefox extensions.

This document outlines the Automate implementation of the agnostic script SWM - Software Configuration - Clear Gecko Cache, including a sample run and output details.

This document outlines the solution to fetch basic information about the computer from CW Manage and display it in a CW Automate dataview. It includes implementation steps and associated content for successful execution.

This document outlines the implementation of the EPM - Data Collection script for gathering data on Chromium extensions. It details the process of creating necessary scripts, executing the agnostic script to collect data, and logging the results for analysis.

This document outlines the implementation of the agnostic script for collecting data on Firefox extensions within ConnectWise Automate. It details the dependencies, process steps, and the expected output including script logs and a custom table.

This document outlines a script that collects all installed extensions from Google Chrome, Microsoft Edge, Brave, and Mozilla Firefox browsers. It acts as a wrapper to execute existing scripts for gathering browser extensions and provides a process for refreshing software inventory and checking for installed browsers.

This document describes a script that retrieves the latest installed Cumulative Update and Full Build Number for a Windows computer. The data is stored in a custom table for Automate implementation, providing essential update information for system management.

This agent procedure checks the update channel for Microsoft Office on macOS endpoints and updates the corresponding custom field. It outlines the necessary steps to implement the procedure, including dependencies, export/import instructions, and expected output for successful execution.

This document outlines the procedure to check and update the Microsoft Office update channel using VSA RMM. It details the various update channels available, the dependencies required, and the implementation steps to successfully export and import the agent procedure.

This document outlines the procedure to retrieve drive information configured by StorageCraft on an endpoint. It includes details on dependencies, process execution, and output logging.

This document details the implementation of the Get-WifiProfile script within ConnectWise Automate, providing instructions on its execution, required parameters, and output generated, including log files and data views.

Documentation for the Get-ChromiumExtensions command to gather information about extensions installed on Chromium-based browsers for each user.

This document outlines the process for collecting information regarding existing crash dumps on target endpoints using a PowerShell script. It includes sample runs, expected return types, dependencies, and detailed variable descriptions necessary for successful execution.

Documentation for the Get-CriticalDiskInfo command to gather data pulled from the CrystalDiskInfo application and return it to RMM.

Documentation for the Get-CrystalDiskInfo command to gather data pulled from the CrystalDiskInfo application.

Documentation for the Get-CWABackup command to return all Labtech*.zip files from any Labtech backup location.

Documentation for the Get-CWControlAgentSession command to connect to ConnectWise Control via the built-in Plugin API in Automate to obtain a list of computers with their last check-in date and current state.

Documentation for the Get-CWControlUsers command to return a list of users and their respective properties on the ConnectWise Control server.

Documentation for the Get-DCUScanResult command to fetch the scan result from dcu-cli for Dell machines.

Documentation for the Get-FirefoxExtensions command to gather information about extensions installed on the Mozilla Firefox browser for each user.

Documentation for the Get-OfficeActivationStatus command to retrieve activation information for any licensed Office products on the endpoint.

This document provides a comprehensive guide on how to convert HTML documents to Markdown format, including tips and best practices to ensure the integrity of the content during the conversion process.

This document outlines a solution designed to search for PST files on a computer and save relevant information into a custom field within ConnectWise Automate. It includes associated content links and implementation instructions.

This document outlines the procedure for updating custom fields via the agent. It includes dependencies and details about the specific fields that can be updated, including their types and descriptions.

Documentation for the Get-UnifiController command to retrieve and return data from a Unifi Controller.

This document provides an overview of the Kaseya Onboarding Audit script, which performs an extensive audit of Kaseya VSA configurations and outputs the results to an Excel spreadsheet. It details the requirements, process, parameters, and output locations for the audit results, ensuring users can effectively utilize the script for auditing purposes.

Documentation for the Get-VSAAuditReports command to perform a Kaseya Onboarding Audit and output results to an Excel spreadsheet.

This document provides a comprehensive guide on how to update OS custom fields within ConnectWise Automate, detailing the necessary steps and considerations for effective implementation.

This document outlines a script designed to manage Wi-Fi profiles on end-user machines, including retrieval, removal, and addition of profiles. It provides detailed instructions on usage, including parameters for adding and removing profiles, as well as important updates and examples.

This document outlines an Automate implementation of a script designed to remove the registry policy that enforces a specific homepage in Google Chrome. It includes a sample run, dependencies, and output details.

This document provides an overview of a script designed to remove the enforcement of a homepage in the Edge browser. It details the process, dependencies, and expected output, ensuring users can effectively manage browser settings without manual intervention.

This document outlines the procedure for removing Google Drive from an endpoint, including a detailed example of the agent procedure log and the steps involved in the uninstallation process.

This document provides a comprehensive guide on how to retrieve an iLO health report using a PowerShell script. It includes requirements, client-level password entry instructions, sample runs, dependencies, and ticketing capabilities for failures encountered during execution.

This document outlines the procedure for deploying HP Image Assistant to endpoints, including downloading, extracting, and installing the software. It provides detailed logs of the agent procedure for transparency and troubleshooting.

This document outlines the procedure for deploying HP Support Assist to endpoints, including the download, extraction, and installation processes. It provides a detailed example of the agent procedure log and the necessary dependencies for successful execution.

This document outlines a script that downloads and installs the HP Support Assistant when a user is logged in. It verifies the installation and logs the outcome, aiming to save time by automating the installation process.

This document outlines a script designed to manage the installation and uninstallation of the Huntress application on target machines, detailing action parameters, processes, and expected outputs.

This document outlines the agent procedure for uninstalling the Huntress EDR agent, updater, and related components. It provides a detailed implementation guide, including dependencies, process steps, and output log locations for successful uninstallation.

Reset Huntress Managed Microsoft Defender and reset Microsoft Defender to defaults

This document provides a detailed guide on how to re-register the Huntress Agent in the portal for the endpoint using a custom script. It includes step-by-step instructions for creating the script, setting up variables, and handling script execution and logging.

This document outlines the process for creating a PowerShell script to repair the Huntress Agent. It includes detailed steps for setting up the necessary variables, downloading the repair script, and logging the output of the operation.

This document provides a detailed guide on how to uninstall the Huntress agent from a Windows machine using a PowerShell script. It includes dependencies, script creation steps, and deployment instructions.

This solution is designed to configure the automatic deployment of the Huntress Agent on Windows and Macintosh machines that are missing the agent, using the NinjaOne platform.

This document provides a detailed overview of a script that downloads and installs the Huntress Agent silently on a Windows machine, saving significant time through automation. It includes global parameters, process steps, and sample output.

This document provides a detailed report on the installation status of Sentinel One and Huntress for various locations. It includes information on whether the installations are allowed, the count of agents installed, and the count of missing agents for both Sentinel One and Huntress at each location.

This document outlines the CW RMM task for installing the Huntress Agent, detailing the custom field used to track installation failures. It provides guidance on creating the custom field necessary for monitoring and ticket creation based on installation results.

This document provides a detailed guide on creating a custom field for the Huntress Organization Key in ConnectWise RMM. It includes instructions on how to set up the field, its properties, and its importance in associating Huntress Agents with their respective organizations.

This monitor will check if the Huntress Agent is orphaned, and then it will try to repair it.

This document outlines the Idle Monitor solution designed to track end user activity by monitoring computer idle times and usage. It includes implementation steps, associated content, and best practices for effective monitoring.

This document outlines the steps to implement a remote monitor for uninstalling Anydesk from specified groups using SQL queries. It provides detailed instructions on obtaining group IDs, constructing the SQL query, and executing it within a RAWSQL monitor set.

This document provides a step-by-step guide on how to uninstall VLC Player using ConnectWise Automate. It includes instructions for setting up the necessary scripts and alert templates, obtaining group IDs, and executing the SQL query to create a remote monitor that handles ticket creation for the uninstallation process.

This document outlines the installation process for populating a MySQL database with a list of potential Log4Shell affected software. It includes instructions for both on-prem and hosted partners, detailing necessary parameters, dependencies, and expected outputs.

Documentation for the Import-Log4JTable command to install and populate a MySQL table with a list of potential Log4Shell affected software.

This document outlines a script designed to address the issue of incorrect drive inventory in ConnectWise Automate when upgrading or swapping agents’ hard drives or SSDs. The script is intended to be executed through a specific remote monitor template for optimal results.

Automates installation, updating, and execution of Dell Command | Configure (DCC) on Dell workstations. Ensures the latest version is present and provides command-line automation for BIOS configuration operations with comprehensive error handling and logging.

Installs, updates, or executes Dell Command | Update (DCU) on Dell workstations, ensuring the latest version is present and providing command-line automation for DCU operations.

HP Image Assistant Automation Script for managing updates on HP workstations.

Automates installation, updating, and execution of Dell Command | Configure (DCC) on Dell workstations. Ensures the latest version is present and provides command-line automation for BIOS configuration operations with comprehensive error handling and logging.

Installs, updates, or executes Dell Command | Update (DCU) on Dell workstations, ensuring the latest version is present and providing command-line automation for DCU operations.

This document provides an overview of the process for writing the ProVal Stack Machine Custom Fields to a new client environment using the VSAAPI ProVal Module. It outlines the requirements, process, payload usage, parameters, and expected output.

This document provides a comprehensive guide on a PowerShell script that checks for Windows updates and installs all available updates, including drivers, with a focus on PC staging to ensure a new machine is fully updated. The script includes parameters for ticketing and system properties management.

Detects windows machines where Evo Agent deployment is enabled and application is not installed.

This script installs the Evo Credential Provider on a Windows machine using the arguments set into the client-level EDFs.

This document provides a comprehensive guide on how to install fonts from a specified directory or file using a script. It includes sample runs, user parameters, and detailed instructions for task creation and execution.

This document outlines the automated procedure for installing and configuring Google Credential Provider for Windows (GCPW). It includes steps for checking prerequisites, installing necessary software, setting allowed domains for login, and configuring an optional enrollment token. Detailed logging and verification steps are also provided.

Deploy Huntress agent on Macintosh machines

Triggers the auto-deployment script for the Huntress Agent on Macintosh machines where deployment is enabled.

This script automates the installation, repair, uninstallation, or reinstallation of the Huntress Agent for Windows machines.

Triggers the auto-deployment script for the Huntress Agent on Windows machines where deployment is enabled.

This document provides a detailed guide on installing Microsoft 365 Apps for Business using an XML configuration file. It includes steps for creating a script, setting parameters, and executing the installation process, with options for customization and logging.

This document outlines the process for implementing a ConnectWise RMM script to install the Microsoft Visual C++ Redistributable. It includes user parameters, task creation steps, and a sample PowerShell script for execution.

This document details an Automate implementation of the Invoke-VcRedistModule script, designed to install the Microsoft Visual C++ Redistributable. The script installs the supported redistributable by default but allows for user-defined parameters to customize the installation process.

Installs the MSP360 PowerShell module and the MSP360 Online Backup Agent (MBSAgent) using a URL from NinjaRMM Custom Field cPVAL MSP 360 Url.

This compound condition is designed to execute the "Install MSP360 Online Backup" script on Windows servers where the "Online Backup" application is not installed and deployment is enabled via the "cPVAL Deploy MSP360" custom field.

This compound condition is designed to execute the "Install MSP360 Online Backup" script on Windows workstations where the "Online Backup" application is not installed and deployment is enabled via the "cPVAL Deploy MSP360" custom field.

This document provides a script that installs the New Microsoft Teams on both Windows and Mac computers. It includes steps for uninstalling the existing classic version on Windows and requires users to log in again to complete the installation process.

This document provides a comprehensive guide on installing Perch Log Shipper using either a user-provided ClientToken or retrieving the token from a client-level EDF. It includes sample runs, dependencies, implementation details, variables, user parameters, and the process for successful installation.

This document provides a comprehensive guide on deploying Perch Log Shipper on Windows machines, including sample runs, user parameters, task creation steps, and script details.

This document details a modified script for the Webroot Plugin installation, enabling automatic deployment through ConnectWise Automate. It outlines the script functionality, dependencies, variables, and process for both installed and non-installed software scenarios.

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 a detailed procedure for installing the Windows Update PowerShell module, including example logs of the agent procedure execution and dependencies required for successful installation.

Documentation for the Install-CiscoSecureClient command to install the Cisco Secure Client and selected modules.

This document outlines a wrapper script designed for installing fonts using an agnostic software installation method. It includes steps for preparing font files, running the script, and verifying the installation process.

Documentation for the Install-GCPW command to automate the installation and configuration of Google Credential Provider for Windows (GCPW).

This document provides a comprehensive guide for installing ImmyBot on endpoints using preconfigured variables within the VSA environment. It covers dependencies, implementation steps, usage of the installation script, and detailed parameter descriptions.

Documentation for the Install-MSTeams command to install Microsoft Teams using the Teamsbootstrapper.exe and optionally upgrade existing installations.

Documentation for the Install-PerchLogShipper command to install Perch Log Shipper on Windows computers.

Documentation for the Install-SnapAgent command to install SnapAgent on Windows computers.

This document provides guidance for users seeking assistance with converting HTML content to Markdown format. It outlines the steps to provide HTML content for conversion and offers support for any related queries.

This document provides a script for installing and updating the FileZilla Client to the latest version based on the configurations set in the Globals and Parameters tab. It outlines the necessary parameters and provides a sample run for reference.

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 provides a detailed overview of a script designed to install or update NordPass on machines. It includes global parameters, output details, ticketing information, and troubleshooting steps for common issues encountered during installation or update processes.

This document outlines the process for detecting machines where the Internet Explorer feature is enabled or where Internet Explorer is installed. It includes a detection string and applicable settings for Windows operating systems.

This document outlines the process for determining whether a Windows machine is enrolled in Intune, including the necessary detection string and implementation steps for importing the role into the system.

Documentation for the Invoke-LSUClientUpdate command to install applicable and silently installable updates on Lenovo machines.

Documentation for the Invoke-VcRedistModule command to manage the installation, uninstallation, and listing of Visual C++ Redistributables.

Documentation for the Invoke-WingetProcessor command to manage software packages using Winget in PowerShell.

This document details a script designed to check and uninstall all installed versions of Java from a target machine. It automates the process by creating and executing a RemoveJAVA.cmd file, streamlining software management and saving time in system maintenance.

This document provides a detailed guide on how to install the LanSweeper agent, including dependencies, user parameters, and expected output. The installation process is outlined with examples and links to additional resources for successful deployment.

This document provides details on the custom field used to store and display the results of the Cumulative Update Audit task in ConnectWise RMM. It includes information about the field type, dependencies, and sample values.

This document provides a detailed overview of the data view that displays the latest installed cumulative update for machines, excluding those for which Microsoft does not release updates. It includes dependencies, columns, and a sample screenshot for reference.

This document provides a comprehensive guide for auditing Windows 10 and 11 computers to ensure they have the latest installed Cumulative Update. It includes steps for implementation, automation, and troubleshooting, along with associated content and internal monitors to streamline the update process.

This document describes a script that utilizes Everything.exe to locate php.exe on a machine and store the results in a custom table. It includes instructions for the first run and regular execution, along with parameter details and output expectations.

This document provides a comprehensive guide to configuring lockdown settings for browsers within a ConnectWise Automate environment. It includes steps for importing client, location, and computer level Extra Data Fields (EDFs), creating searches and groups, and setting up remote monitors to ensure effective management of browser lockdown features.

This document provides a comprehensive report on potential Log4J/Log4Shell vulnerabilities, detailing affected applications based on a curated list from GitHub. It includes dependencies for endpoint protection and outlines the relevant columns for tracking vulnerabilities.

This document provides an overview of the Log4Shell Vulnerability Scan Script, detailing its functionality, dependencies, and the output it generates. The script is designed to identify vulnerabilities in target systems and save relevant information to EDFs for comprehensive reporting.

This document provides a detailed guide on installing the Logitech Unifying Software, including requirements, sample runs, global parameters, dependencies, and process overview.

This document provides a detailed overview of a script designed to fetch the uninstall string from the database and execute the uninstallation of LogMeIn clients from a target machine. The process is automated to save time and streamline the uninstallation procedure.

This document provides a detailed guide on utilizing the LSU Client PowerShell module to install applicable and silently installable updates on Lenovo machines with non-discharging batteries. It outlines the steps for task creation, script implementation, and verification of execution logs.

This document explains the managed variable used to store the partner Microsoft M365 tenant ID, which is essential for configuring various OneDrive group policies. It provides guidance on how partners can obtain their tenant ID and outlines the associated managed variable details.

This document outlines the steps to create a dynamic group that filters Windows machines with the Huntress Agent installed. It includes criteria for software installation and group management instructions.

This script disables and uninstalls the MSRT from the endpoint and provided option to creates ticket if failure detected.

This script performs the endpoint scanning using the MSRT and provided option to creates ticket if failure detected.

This group includes the endpoint where the MSRT scanning required to be enable.

This group includes the endpoint where the MSRT needed to be uninstalled and disabled.

This document describes a script that downloads an uninstaller tool from the Malwarebytes webpage and automates the uninstallation process of Malwarebytes from a target machine, saving time and ensuring successful removal.

This document outlines two agent procedures, ISO Mount Disable and ISO Mount Enable, designed to manage end-user access to mounting ISOs in Windows environments. It includes example logs and a detailed process for modifying registry settings to enable or disable ISO mounting capabilities.

This document provides a step-by-step guide for technicians to manually troubleshoot the Orange Icon issue with the ScreenConnect client in Automate. The Orange Icon indicates a potential problem with the application installation or connectivity to the ScreenConnect Web portal. Follow the outlined steps to resolve the issue effectively.

This document provides a detailed overview of an Automate implementation for the agnostic solution to remove McAfee products from Windows machines. It includes a summary of the script, sample run visuals, dependencies, process steps, and expected output logs.

This document outlines the process for importing custom backgrounds into Microsoft Teams using a ZIP file containing supported image formats. It includes implementation steps, dependencies, and the overall process to ensure successful background uploads for active users.

This document provides a comprehensive guide for auditing the Click-to-Run version of Microsoft 365, including the creation of custom fields, device groups, and scheduled tasks to gather essential information about the installed Office version and its update settings.

This document outlines how to detect computers with differing Microsoft 365 update channels as set in the Client or Computer Level Update Channel. It requires Microsoft 365 Click-to-Run installation and a managed patch policy.

This document details a script that modifies the registry to set the update channel for Microsoft 365 products based on the values defined in the Client or Computer level EDF Update Channel. It includes sample runs, dependencies, and detailed tables for client and computer level EDF configurations.

This document outlines a script that modifies the registry to enable regular updates for Microsoft 365 products according to the current channel updates. It also executes a follow-up script to update version information in the relevant audit data view.

This document outlines a script that modifies registry settings to enable Microsoft 365 products to update on a monthly basis, in line with current channel updates. It also executes a follow-up script to update the relevant dataview in ConnectWise Automate, thereby enhancing the management and auditing of Office versions.

This document details an Automate implementation of a script designed to remove the registry policy that enforces a specific homepage in Microsoft Edge (Chromium). It includes a summary of the script, a sample run, dependencies, and expected output.

This document details the Automate implementation of the SWM - Software Configuration - Set-ChromiumHomepage script, which enforces a specific homepage for the Microsoft Edge (Chromium) browser. It includes user parameters, sample runs, and dependencies for successful execution.

This document outlines a script designed to remove the enforcement of the installation of specified extensions in the Chromium version of the Microsoft Edge browser. The process includes details on dependencies, variables, and the overall operation of the script, ensuring users can effectively manage their browser extensions.

This document outlines a script that adds a registry policy to enforce a specific homepage in Microsoft Edge (Chromium). It details the necessary dependencies, user parameters, and the process for executing the script, along with sample output and logs.

This document provides a guide to updating Microsoft 365 Apps to their latest version, ensuring that users have access to the most recent features and security updates. It includes a sample run and output details for tracking the update process.

This document describes a script that performs repairs on Office products, offering both quick and full repair options based on user parameters. It checks the installation status and bit version of Office before executing the appropriate repair process.

This document details the Office Scrub utility script that automates the uninstallation of specified Microsoft Office products, streamlining the process and saving considerable time. It includes dependencies, user parameters, and output information for effective execution.

This document outlines the procedure for silently removing Microsoft Office when it cannot be uninstalled via winget. It includes example logs from the agent procedure and a link to the Invoke-OffScrub script used in the process.

This document describes a script that downloads offscrub files and uninstalls all versions of Microsoft Office from 2007 to 2016 & O365, handling machine or software corruption and removing app shortcuts.

This document provides an overview of the dataview that displays the update status of supported versions of Click To Run Microsoft 365 Apps. It includes information on the recent execution of the update script and the current application versions installed on various machines.

This document provides an overview of an Automate Wrapper designed to execute the Agnostic Update-Office script. It includes sample runs, dependencies, variable descriptions, global parameters, output details, and ticketing information.

This document provides a detailed implementation guide for redirecting Windows known folders such as Desktop, Documents, Pictures, Screenshots, and Camera Roll to Microsoft OneDrive using group policies. It includes dependencies, usage instructions, and customization options for partners.

This document details a script for collecting OneDrive sync status information from Windows machines, targeting Non-SharePoint Linked Sites. The script utilizes the Onedrive.dll module and requires an active user session to function correctly.

This document describes a script that collects all OST/PST file names and sizes from Windows machines, storing the data in a custom table for auditing purposes. It includes details about the script path, file hash, sample run output, dependencies, and the expected output from the script.

This document outlines the process for installing the Teams Machine-wide Installer and configuring it to install Teams for the current user. It details the creation of a scheduled task that ensures all users logging into the machine will have Teams installed automatically.

This document provides a PowerShell script that removes the autostart entry for Microsoft Teams for all users, helping to streamline the login process by preventing the application from launching automatically.

This document outlines a monitor designed to check for the absence of Dell OpenManage System Management Software on Dell machines, ensuring that critical hardware components are properly managed and monitored. It includes suggested alert templates and ticketing information for effective incident management.

This document outlines the procedure for resetting the value of the Monthly CF in ConnectWise Automate, detailing the process, dependencies, and example logs for successful execution.

This document provides a comprehensive audit summary of newly added computers, software installations, and domain user additions within the client environment for the last month. It includes detailed information about the client and agent status, as well as specific counts and dates for each category.

This document provides a detailed guide on installing an extension on the Mozilla Firefox browser, including user parameters and task creation steps. It outlines dependencies, parameters required for the script, and provides a sample PowerShell script for execution.

This document provides a detailed guide on how to remove an extension from the Mozilla Firefox browser, including sample runs, user parameters, task creation steps, and a PowerShell script for automation.

This document describes an implementation of the agnostic script to remove the enforced homepage policy in Mozilla Firefox using ConnectWise Automate. It includes a sample run, dependencies, and the expected output including script logs.

This document describes an Automate implementation of the SWM - Software Configuration - Set-FirefoxHomepage script, which sets the default homepage for the Mozilla Firefox browser. It includes user parameters, sample run outputs, and dependencies.

This document outlines a script designed to remove the enforcement of a homepage in the Mozilla Firefox browser. It details the dependencies required, the process involved in scanning and removing homepage policies, and the expected output including logs for success and failure tracking.

This document details a script that adds a registry policy to enforce a specific homepage in Mozilla Firefox. It includes information on dependencies, user parameters, and the output generated by the script, which helps manage browser settings efficiently.

This document outlines the procedure for silently uninstalling the "Teams Machine-Wide Installer" and installing the latest version on a machine. It includes example logs and a step-by-step process for executing the procedure successfully.

This solution enables automated deployment of MSP360 Online Backup agents to Windows servers and workstations through NinjaOne, using custom fields to control deployment scope and provide installation URLs.

This document provides a detailed guide on creating a custom fields for the MSRT(Malicious Software Removal Tool) in ConnectWise RMM. It includes instructions on how to set up the field, its properties, and its importance in associating MSRT with their respective organizations.

This document provides a comprehensive guide on using the script to set or reset global or computer level disk thresholds. It includes sample runs, dependencies, variable documentation, user parameters, and expected output.

This document provides an audit of all locations that have different configurations from the global settings in the Ninite Plugin, detailing the discrepancies in application configurations for better management.

This document outlines a script designed to uninstall the NinjaRMMAgent from a machine. It includes a global parameter for ticketing, which, when enabled, generates a support ticket if the uninstallation process fails. The document also provides a summary of the script functionality and sample run output.

This document is crafted to walk you through the utilization of the Offboarding Scripts - Partner script to run the Sub Scripts before retiring the machine from Automate.

This document provides a comprehensive guide to using the Offboarding Wrapper Script for client machines, detailing its dependencies, system properties, and output expectations. This script ensures that all necessary subscripts are executed before removing machines from the client environment, with built-in ticketing for tracking failures and successes.

This document outlines the detection method for identifying if the O365 applications are on the Current Update Channel. It includes settings and detection strings for effective monitoring and compliance.

This document provides a detailed overview of the Office Activation Status Audit process, including example logs, dependencies, and output details for auditing licensed Office products on endpoints.

This document provides a step-by-step guide on how to create a dynamic group for auditing computers with Microsoft 365 installed using ConnectWise Automate. It includes navigation instructions, criteria setup, and completion verification.

This document outlines the process to repair the Office Click2Run Automatic Update on an endpoint using the ProVal Agnostic Solution. It includes example logs and details on the execution of the repair procedure.

This document provides a detailed procedure for performing an on-demand update for Click2Run Office installations on endpoints using an agnostic solution. It includes example logs, dependencies, and output details to assist in the execution and troubleshooting of the update process.

This document provides a detailed guide on how to set the Microsoft Update Channel for a Click2Run Office installation on an endpoint using an agnostic solution. It includes a summary, example agent procedure logs, and expected output for successful execution.

This document outlines the procedure for setting the update channel for Microsoft Office on macOS endpoints, including the available channels and implementation steps for exporting and importing the agent procedure in VSA RMM.

This document provides a comprehensive guide on using the Office Universal Uninstaller script, which downloads offscrub files and uninstalls all versions of Microsoft Office from 2007 to 2016 & O365, handling machine or software corruption and removing app shortcuts.

This document explains how to use a PowerShell script to disable Office updates by modifying a registry value. The process is straightforward and saves time by automating the update disabling procedure.

This document explains how to enable Office updates by running a PowerShell command that modifies a specific registry value. The script updates the registry key to allow for automatic updates, saving time and ensuring that your Office applications are always up to date.

This document provides an overview of the Kaseya Onboarding Audit script, which performs an extensive audit of Kaseya VSA configurations and outputs the results to an Excel spreadsheet. It details the requirements, process, parameters, and output locations for the audit results, ensuring users can effectively utilize the script for auditing purposes.

This document provides a detailed overview of a script that gathers information about the status of the built-in OneDrive backup functionality for the currently logged-in user, highlighting its efficiency and dependencies.

This document outlines the procedure to disallow OneDrive from being used on endpoints through Local Security Policy. It includes a sample run log, the process used to achieve this, and the expected output from the agent procedure.

This document describes a script designed to uninstall OneDrive from Windows machines, including global parameters for ticketing on failure, sample run outputs, and details for logging and ticket creation.

This document outlines the importance of enabling folder redirection notifications for OneDrive on endpoints, ensuring users are aware of any issues with their OneDrive not redirecting properly. It includes detection settings and applicable operating systems.

This document describes a script that updates the Outlook options on a computer to open hyperlinks in the Default Browser. It modifies specific Windows registry values related to Outlook settings to ensure that hyperlinks within Outlook open using the Default Browser instead of Microsoft Edge.

This document outlines the functionality and requirements of the OpenDNS Monitor designed for Windows Workstations. It details the conditions under which the monitor triggers failures and provides troubleshooting information. Additionally, it suggests configurations for alerts and dependencies related to the software installation process.

This document outlines a procedure to determine the initial install date of the operating system using PowerShell. It provides a detailed example of the agent procedure log, dependencies required for execution, and the expected output of the procedure.

The Patch Compliance - CU Audit - Workstations report provides a detailed overview of workstation patch statuses for a specific client, evaluating how long each machine has been using an outdated cumulative update and calculating a compliance score based on this data.

This document outlines a script that counts the number of patches that have not been actioned in any approval policy within a client environment. It highlights the time saved by automation and provides details on global parameters and the process involved in executing the script.

This document provides an overview of a data view that displays the patching stage assigned to a machine. It outlines the relevant columns, including client name, location name, machine name, and the current patching stage, while noting that the data is only applicable if the stage delay feature is active.

This document outlines the purpose, dependencies, and structure of the Battery Information Storage for each target machine in ConnectWise Automate. It details the necessary table and its columns for storing battery-related data, including health state, capacity, and manufacturer information.

This document outlines the custom table for storing information about installed browser extensions gathered by specific scripts. It details the dependencies, table structure, and the data captured for extensions in various browsers, including Chromium and Firefox.

This document stores information about applications that may be affected by Log4J vulnerabilities, including supplier details, product names, affected versions, current status, and relevant links for further information.

This document outlines the purpose and dependencies for storing printer driver inventory data in ConnectWise Automate. It details the structure of the database table used for this inventory, including the necessary columns and their explanations.

This document outlines the structure and purpose of the EPM Data Collection for the UnifiController, detailing the dependencies and table schema used for holding device data associated with each controller.

This document outlines the purpose and structure of storing WiFi profiles gathered from the WiFi Profile - Get script for later application using the WiFi Profile - Apply script. It includes details about dependencies and the database table structure used for storage.

This document outlines a script that prevents a computer from sleeping while plugged in, detailing its dependencies, variables, and the process involved in executing the script. It includes a sample run and highlights the time saved by automation.

This document details the implementation of the EPM - Data Collection - Agnostic - Get-PowerPlan script, which gathers data and stores it in the custom table pvl_powerplan_audit. The collected data is then displayed using the corresponding dataview for analysis and reporting.

This document provides an implementation guide for the Remove Power Plan script within ConnectWise Automate. It includes details on file paths, sample runs, dependencies, user parameters, and output logs. Ensure the correct Power Plan name is used for successful execution.

This document details the implementation of the Set-PowerPlan script in ConnectWise Automate, providing guidance on how to modify or create power plans using settings from a CSV file or hash table. It includes sample runs, automation steps, and configuration details for effective management of power settings across client machines.

This document outlines a solution for automating the deployment of a standard power plan to Windows machines, including the ability to audit existing power plans. It provides detailed implementation steps, associated scripts, and monitors to ensure effective power management across systems.

This document outlines a monitor set designed to detect Windows machines where the PowerShell version is older than 5.0. It includes necessary adjustments for functionality and dependencies for implementation.

This document details the implementation of the Disable-PowershellVersion2 agnostic script within ConnectWise Automate, including sample runs and dependencies.

This document outlines the steps to create a custom field in ConnectWise RMM to store Windows PowerShell version information about endpoints. The details are collected using a specific task designed for this purpose.

This document provides a comprehensive guide for creating three device groups related to the PowerShell version auditing solution. It outlines the necessary dependencies, the steps to create the device groups, and the specific criteria for each group based on the PowerShell version status of the devices.

This document provides a detailed guide on updating PowerShell to version 5 on Windows devices. The script checks the current version and performs the update if necessary, while also detailing the conditions under which the update can be applied.

This document outlines an agent procedure used to create a scheduled task that runs PowerShell commands at user logon. It provides a detailed example of the procedure log, dependencies, and the process involved in executing the task.

This document details a script that prevents browsers from prompting to save passwords by modifying the registry settings for Internet Explorer, Chrome, Firefox, and Edge. It includes options to enable password saving and remove currently saved passwords, along with sample runs and variable descriptions.

This document provides an overview of the Dataview that displays installed Printer Driver information obtained from the CWM - Automate - Script - Get - Printer Driver Inventory [DV] script. It includes details about dependencies and the columns available in the Dataview for better management and reporting of printer drivers across client systems.

This document provides a detailed overview of a script designed to manage exclusions in thresholds for targets within a ConnectWise Automate solution. It explains how to implement global and computer-level parameters, including the ability to overwrite existing values. Sample runs and user parameters are included for clarity.

This internal monitor is built to upgrade the DUO Desktop every month if a newer version is released. It also provides an option to install the application with the upgrade.

This monitor is designed to fetch the latest version of the DUO Desktop every month and store it in the system property DUO_Desktop_Latest_Version.

This document provides a detailed overview of custom internal monitors built by ProVal, including their implementation status, alert styles, and execution intervals. It also outlines the color coding used to highlight monitor statuses and script types for easier identification.

This document outlines a new standard for creating tickets for clients, including required global properties, implementation details, and example scripts. It aims to streamline ticket management and improve efficiency in handling client requests.

This document provides a detailed overview of the configurable removal of potentially unwanted applications (PUAs) using an agnostic script. It includes sample run logs, variable descriptions, and the overall process for executing the script effectively.

This document outlines the purpose and structure of the data stored by the Get CWM Configurations script, which gathers information on active and managed configurations from ConnectWise Manage. It includes details on dependencies and the schema of the data collected.

This document outlines the purpose and structure of a custom table designed to store data collected by the EPM - Data Collection script for Microsoft Outlook OST/PST audits. It details the dependencies and the specific columns included in the table, providing a comprehensive overview for users and developers.

This document outlines the purpose and structure of the IdleMon Report Data Storage, detailing the dependencies, table structure, and column explanations for effective data management in ConnectWise Automate.

This document details the "pvl_win_installer_properties" SQL custom table utilized in conjunction with the CWM Automate script for gathering and storing information about Windows Installer applications installed on a machine. It outlines the table structure, including columns for application details such as name, version, publisher, and installation paths.

This document outlines the purpose and structure for storing audit data retrieved by the Winget App Audit script. It includes details about the dependencies, the specific database table used for storage, and descriptions of each column in the table.

This document outlines the procedure to install the QuickPass agent on Windows machines where it is not already installed. It includes associated content, implementation steps, and configuration details necessary for successful deployment.

This document provides a detailed guide on how to re-register the Huntress Agent on Windows machines using a PowerShell script. It includes file hashes, dependencies, variables, client-level and location-level EDFs, as well as sample run images and output logs.

This document outlines the custom fields used in the Reboot Schedule Solution, detailing their configurations, dependencies, and steps to create and manage them effectively within the system.

This script enables extensions for various Chromium-based browsers including Google Chrome, Microsoft Edge, Brave, and Vivaldi. It provides options for targeting specific browsers or all available browsers while considering policy settings and dependencies.

This document provides a detailed guide on how to reinstall the Huntress Agent on Windows machines, including necessary dependencies, variables, and client-level and location-level EDFs required for the process.

This document provides a comprehensive guide on how to remove applications using an agent procedure that allows for normal and forceful uninstallation methods. It includes details on variables, dependencies, and the process for executing the removal of applications, ensuring a customizable approach for various uninstall scenarios.

This document outlines the procedure for removing unwanted ScreenConnect clients from Windows machines, including associated scripts, monitors, and SQL queries for auditing purposes.

This document provides an overview of a script designed to facilitate the removal of specified software packages from a computer system, including functionality for uninstalling bloatware. It outlines the necessary precautions, command execution steps, sample runs, dependencies, and user parameters for effective usage.

This document provides a detailed guide on how to create and implement a script in ConnectWise RMM for uninstalling specified applications from devices. It includes sample runs, user parameters, and step-by-step instructions for setting up the task and handling outputs effectively.

This document provides a detailed overview of the custom field used in the "Remove Application" script to track the success or failure status of application removal. It includes steps for creating the custom field and its specific attributes.

This document provides a detailed overview of a script designed to remove Automate Server Monitoring content from the environment, including options to remove the ProSyncClient Plugin. It includes user parameters, process steps, and warnings about the script’s potential destructiveness.

This document outlines the implementation of the agnostic Remove-BitdefenderEndpointSecurity script, detailing its dependencies, process, and expected output for removing Bitdefender Endpoint Security from target systems.

This document outlines the implementation of a script to remove homepage settings from popular Chromium-based browsers including Edge, Chrome, and Brave using ConnectWise RMM. It includes user parameters, task creation steps, and sample runs.

This document provides an example of a PowerShell script designed to streamline system configuration tasks. It covers various settings and configurations that can be automated to improve efficiency and consistency across systems.

This document provides a detailed guide on removing all McAfee products from an endpoint using a ConnectWise RMM implementation of the agnostic script Remove-McAfeeSoftware. It includes sample runs, dependencies, task creation steps, and the complete script for execution.

This document provides a detailed guide on how to remove specified paths from the Environmental Path variable at the Machine scope using a ConnectWise RMM implementation of the agnostic script Remove-PathVariable.

This script uninstalls the SentinelOne agent from a Windows system. It dynamically detects the installation directory of the SentinelOne agent and executes the uninstallation process.

This document provides an overview of the process to remove stagnant agents from Kaseya VSA based on specific filters defined in a JSON file. It includes requirements, dependencies, usage examples, and detailed parameters for the removal process, along with logging and notification options.

Documentation for the Remove-Application command to remove an application or list of applications either by normal means or forcefully.

Documentation for the Remove-DattoRmmAgent command to fully remove Datto RMM from an endpoint.

Documentation for the Remove-McAfeeSoftware command to remove all McAfee products from an endpoint.

Documentation for the Remove-Sophos command to completely remove the Sophos Agent Endpoint from the system.

This document provides a detailed guide on using a script to repair the Huntress Agent on Windows machines, including file hashes, dependencies, variables, and client-level EDFs.

This document outlines a script designed to repair and reset Windows update settings, aiming to resolve potential patching issues on Windows devices. It details the script’s dependencies, global and user parameters, process, and expected output, including logging of successes and failures.

This document provides a summary of the dataview that displays information about agents that have been repaired using the Automate Agent - Auto Repair script. It includes details on dependencies, columns, and the data captured for each repaired agent.

This document outlines the process to restrict vendor access to clients in Automate, including the necessary configurations and steps to implement the solution effectively.

This document provides a detailed overview of a script designed to unpack and install the RingCentral Phone application on Mac devices, including its dependencies, process, and expected output.

This document outlines the implementation of scheduled tasks for updating installed applications using Winget on Windows 10 and 11 machines. It details the necessary custom fields, device groups, and tasks required to automate the update process effectively.

This document provides a detailed guide on how to create a scheduled task on an endpoint using PowerShell. It includes example logs, FAQs, and a process overview to help users understand the steps involved in setting up a scheduled task effectively.

This document outlines the process of creating a scheduled task that attempts to restart the VSA Agent every 15 minutes to ensure that VSA agents remain online and notify users of any issues. It includes sample run logs, dependencies, and the process involved in setting up the task.

This document details a script designed to set the "Vendor Restricted" custom property in the CW Control Portal, allowing for the restriction of machine access based on vendor settings. It outlines the necessary system properties, user parameters, and dependencies required for successful execution.

This document provides a detailed guide on uninstalling all instances of ScreenConnect from an endpoint using WMIC commands. It includes a sample run log, process description, output details, and instructions for exporting attachments.

This document provides a comprehensive guide on uninstalling the N-Able (Windows Agent) application, including the script to perform the uninstallation and clean up all traces of the application from the system.

This document provides a comprehensive overview of the Invoke Winget Processor script, designed to install and update applications available in the Winget package manager. It includes details about the script path, file hash, sample run, variables, and parameters utilized within the script.

This document provides an overview of the dataview that lists all scripts in the environment, detailing their script folders, types, permissions, and other relevant attributes. It includes a summary of the columns available, such as script name, folder paths, permissions for viewing and editing, and additional script characteristics.

This document outlines three dataviews designed to showcase the performance, historical, and descriptive details of scripts within an environment. It includes instructions for implementation, associated content, and answers to frequently asked questions regarding the dataviews.

This document outlines the process for setting standard permissions to stock scripts in ConnectWise Automate, including associated content, implementation steps, and FAQs related to script permission alignment.

This document details a script that displays the results of selecting "Find Script" for all scripts in ConnectWise Automate. It includes dependencies, implementation steps, and a breakdown of the columns in the output.

This document provides a detailed guide on installing the IdleMon service, including prerequisites and expected outputs. It also includes a link to the official documentation for further reference.

This document outlines the procedure for downloading and installing the Senteon Agent on endpoints. It includes details on dependencies, implementation steps, and expected output upon successful installation.

This document outlines the steps to uninstall the Senteon Agent from an endpoint using the Remove - Application agent procedure template. It provides details on the implementation process, including exporting and importing the agent procedure within the ProVal VSA environment.

This document outlines the process for installing and uninstalling the Senteon Agent application on endpoints, including the necessary dependencies and associated content for effective implementation.

This document outlines the managed variable used to store the Senteon ID/Name of the partner organization. It provides details on how partners can obtain this information from the Senteon portal and its usage in agent procedures during installation.

This document provides details on managing the Senteon registration code for agents, including how to retrieve the necessary code from the Senteon portal and its usage in the agent installation process.

This document details the managed variable used to store the Senteon ID/Name of the Tenant for agent registration. It provides guidance on obtaining the necessary information from the Senteon portal and explains the variable’s purpose in the agent installation process.

This document provides a comprehensive guide on how to obtain the site key and URL associated with a target endpoint in ConnectWise Automate, and compare it to the value set in the Client-level EDF named "SentinelOne SITE_TOKEN". It includes variables, parameters, configuration, and output details.

This document outlines the process for verifying that computers are using the correct Sentinel Agent associated with their respective clients. It includes implementation steps, associated scripts, and monitors for effective management.

This document provides a comprehensive guide for deploying the SentinelOne agent, detailing the use of agent tokens at various levels, implementation instructions, and process steps to ensure successful installation and configuration.

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 script automates the deployment of the Todyl Agent on Windows machines by downloading the latest installer, running the installation silently, and validating that the agent has been successfully installed.

This document provides a step-by-step guide on how to create a dynamic group in Kaseya VSA for Windows machines that have the Sentinel Agent installed. It includes detailed instructions and images to assist in the setup process.

This document provides a detailed guide on how to set an enforced homepage in popular browsers such as Brave, Chrome, and Edge. It includes implementation steps, user parameters, and sample runs to ensure proper configuration.

This document describes a script that downloads Autologon.exe from the Sysinternals website and configures it to enable automatic user login after system reboot. It includes user parameters, process details, and expected output.

This script modifies the registry settings for Outlook to adjust the MaxLargeFileSize and WarnLargeFileSize parameters based on user-defined values or defaults. It ensures that the MaxLargeFileSize is set to 100,000 MB and WarnLargeFileSize to 95,000 MB if no values are provided.

This document provides a detailed guide on removing registry entries that may prevent Windows updates and restoring the default Windows Update settings to fully re-enable updates for users. It includes step-by-step instructions for task creation and implementation using a PowerShell script.

This document outlines the process for configuring power plan settings using a CSV file. It details the necessary template, the validation of parameters, and how to create or modify power plans based on user-defined settings. It also provides examples of how to utilize the script for different scenarios, including local and remote CSV file usage.

This document provides a detailed guide on a script that automates the download and installation of the ShadowControl client on a target machine, including steps for subscribing to the appropriate ShadowControl server and cleaning up after installation.

This document outlines the process for downloading and installing the ShadowControl client on a target machine. It includes automatic subscription to the ProVal ShadowControl server and ensures the downloaded installer is deleted after completion. Note that this script is specifically designed for ProVal Shadow Control instances.

This document details a script that fetches the uninstall string from the database to uninstall ShadowControl and unregister it from the server, streamlining the uninstallation process and saving time through automation.

This document details a script that allows users to hide or unhide hidden files based on a specified input parameter. The script improves efficiency by automating the process of file visibility management, saving users valuable time.

This document provides an overview of a script that returns a custom object listing all installed fonts on a system by querying the registry. It details the process, usage, and output format of the script.

This document details a script designed to deliver a one-time, customized message to users, featuring optional branding through an image URL. It outlines the requirements, user parameters, process, and examples of usage.

This document outlines the implementation of a Simple Notification App that delivers a one-time customized message to users, featuring company branding through an optional image URL. The script is designed for easy setup and execution, ensuring that notifications are displayed promptly on the user’s screen.

This document provides a detailed overview of a script designed to uninstall Skype from devices. It outlines the process, dependencies, and expected outcomes, ensuring users can efficiently remove the application while saving time through automation.

This document outlines the steps required to deploy the SnapAgent on Windows machines using the Agnostic SnapAgent installer. It includes associated scripts, monitors, and alert templates necessary for successful installation and monitoring of the SnapAgent.

This document outlines the procedure for enabling the SNMP Windows Optional feature on an endpoint, including example logs and a detailed process description.

This document describes a script that fetches the uninstallation string for a specified application from the database and attempts to uninstall it. It includes user parameters, process details, and output logs, making it a useful tool for managing software uninstallation efficiently.

This document describes a script that fetches the uninstallation string from the database for a specified application and attempts to uninstall it. The script utilizes silent switches for a seamless process and logs the results for verification.

This document provides a comprehensive guide on how to install the Exclaimer application on both MAC and Windows operating systems. It outlines the dependencies, process, and expected output of the installation script, helping users save time through automation.

This document provides a dataview to identify machines with Open DNS (Umbrella Agent) installed and checks for the presence of a wireless network card. It aims to help in finding devices unnecessarily using Open DNS when configured at the router/firewall level. By identifying endpoints without wireless capabilities, organizations can reduce costs associated with the Open DNS solution.

This document provides a comprehensive overview of well-known remote access software installed on systems. It includes detection capabilities for various popular remote access tools, along with a detailed column description of the data collected.

The document provides step-by-step instructions for creating an ImmyBot software based on a ProVal document.

This document outlines an internal monitor designed to check machines for installed antivirus software, specifically excluding those where the Webroot plugin is set to auto-deploy. It includes prerequisites and target deployment information.

This document describes the Soji execution script designed for ConnectWise Automate, detailing its functionality, dependencies, user parameters, process steps, and output results. The script facilitates the execution of the Soji application while managing necessary installations and logging outputs effectively.

This document provides a comprehensive guide on creating the Soji disk cleanup Task in ConnectWise RMM. Soji is a smart disk cleanup utility designed to enhance system cleanliness on Windows, utilizing native System.IO file and directory management along with COM references to the deprecated cleanmgr tool.

This document provides a comprehensive guide on creating the Soji disk cleanup Task in ConnectWise RMM. Soji is a smart disk cleanup utility designed to enhance system cleanliness on Windows, utilizing native System.IO file and directory management along with COM references to the deprecated cleanmgr tool.

This document outlines the implementation process for running the Soji Disk Cleaner on selected endpoints within Datto RMM. It includes dependencies, implementation steps, and output details to ensure successful execution.

This document provides a comprehensive guide on installing and updating the SonicWall NetExtender application using Winget. It includes associated scripts, internal monitors, and alert templates necessary for effective deployment and version detection of SonicWall NetExtender.

This document outlines a monitor that schedules a script to collect the latest version details of the SonicWall NetExtender application monthly, updating the system properties without deploying the application itself. It is designed for Windows 10/11 workstations with a patch policy.

This document provides a detailed overview of a script designed to uninstall the Sophos endpoint from a Windows-based device, including prerequisites, processes, and expected outcomes. The script verifies the status of Sophos Tamper Protection and ensures a clean uninstallation process, followed by a system reboot.

This document provides a comprehensive guide on removing the Sophos Endpoint Agent from an endpoint, including example logs, dependencies, and the process involved in the uninstallation. It details the use of SophosZap and necessary configurations for successful removal.

This document provides a detailed overview of the process to uninstall Splashtop using WMI detection and removal methods. It includes a sample run log and describes the output generated during the uninstall procedure.

This document provides a comprehensive guide for technicians on how to detect and lockdown machines marked as stolen within a ConnectWise Automate environment. It includes implementation steps, associated scripts, and internal monitors to effectively manage stolen systems.

This document provides a role definition to help track down machines with StorageCraft ImageManager v7.5.X 32-bit installed. It includes detection strings and settings for identifying the software on applicable operating systems.

This document provides a role definition for tracking machines with StorageCraft ImageManager v7.5.X 64-bit installed. It includes detection strings, comparators, and applicable operating systems to ensure accurate identification of the software version.

This document provides a method to detect if StorageCraft ImageManager version 7.6.X 32-bit is installed on Windows systems. It includes a detection string, comparator, and applicable operating systems for accurate identification.

This document provides information on detecting the installation of the 64-bit version of StorageCraft ImageManager v7.6.x on Windows machines, including the detection string and applicable operating systems.

This document outlines a role that checks if the primary build number for ShadowProtect SPX is version 7. It provides details on how this data can be utilized for effective backup management based on the software version present on an endpoint.

This document provides a comprehensive overview of a script designed to install or update the SonicWall NetExtender application on target devices using Winget. It includes sample runs, variable descriptions, and process details to ensure effective deployment.

This document details the process of gathering configuration field data from the xPVAL Azure AD Connect Version and displays all endpoints that have a valid version. It outlines dependencies, layout specifications, and filtering criteria for effective reporting.

This document outlines a script designed to remove the Dell Optimizer application from Dell computers. It includes instructions for setting a user parameter to control whether the computer should reboot automatically after the application is uninstalled.

This document provides a comprehensive guide on installing or updating Microsoft Office 365 using a preconfigured DRRMConfig.xml file. It outlines the requirements, process, and implementation steps necessary to ensure a successful installation on Windows environments.

This document provides a detailed guide on the installation and upgrade of the Liongard Agent, including service configuration options and necessary parameters for successful execution.

This document outlines the process and implementation details for a script designed to uninstall any version of Driver Booster from a Windows machine. It includes instructions for importing the script, running it with a specific monitor, and executing it independently.

This document provides a comprehensive guide on installing Cisco AnyConnect along with its desired components using an agnostic script. It includes argument options, implementation steps, sample runs, dependencies, user parameters, and the overall process of execution.

This document provides a detailed guide on using the Microsoft Office Uninstall component, which runs the Office Scrub utility to remove specified Microsoft Office products from a Datto RMM instance. It includes implementation steps, usage instructions, and expected output.

This document outlines the steps to perform an automated uninstallation of Pulseway, including necessary cleanup procedures and integration with Datto RMM. It provides detailed implementation instructions and expected output for successful execution.

This document provides a detailed overview of a script designed to remove the Kaseya Agent and Live Connect applications from Windows computers, including a sample run and variable descriptions.

This document provides an overview of the script that automatically updates all installed versions of Visual Studio, including VS 2022, 2019, and 2017 for both Enterprise and Community editions. It details the process of checking for installed applications, downloading updates, performing upgrades, and logging the results.

This document outlines a script designed to update the installed version of Visual Studio Code to the latest available version. It includes details on user requirements, prompts during the update process, and variables used within the script.

This document outlines the process for installing the Symantec Agent on a Windows machine using a script. It includes details on dependencies, the installation process, and the expected output, highlighting the time saved by automation.

This document provides a PowerShell script designed to uninstall Symantec Endpoint Protection from a target machine, detailing the process, dependencies, and expected output.

Documentation for the Test-InternetSpeed command to run an internet speed test via the Ookla SpeedTest CLI application.

This document outlines a script that retrieves API keys from the client password tab to enable learning mode for ThreatLocker. It includes details on dependencies, variables, parameters, and instructions for use, ensuring secure handling of API keys.

This script installs the ThreatLocker agent on Windows and Mac operating systems.

The Purpose of this solution is to deploy a threatlocker agent on both Windows and Mac machines.

This document provides a comprehensive guide on how to install Threatlocker on both Windows and Mac operating systems, including task creation, script implementation, and scheduling for auto deployment.

This document provides a comprehensive overview of the Threatlocker Learning Mode Dataview, detailing its dependencies, columns, and the information it captures regarding the learning mode settings applied through the specified script.

This document provides a detailed overview of a script designed for creating tickets based on missing patches in a ProVal environment. It outlines the dependencies, process, and an example of a generated ticket, emphasizing that the script should be monitor-driven and not manually executed.

This document provides a comprehensive guide on running the Remove-Sophos.ps1 script on Automate managed devices, detailing prerequisites, parameters, and expected outcomes for successful execution.

This document outlines the setup for a remote monitor designed to uninstall Anydesk from Windows machines. It includes details on suggested configurations, alert styles, and ticketing information for effective monitoring and issue resolution.

This document outlines the purpose and dependencies of the Windows Duo Agent Exclusion Monitor, which is designed to detect Windows machines with Duo installed and manage exclusions based on client, location, or computer-level settings.

This document provides details about a specialized script designed to uninstall the DUO application from systems. It includes sample runs, dependencies, global parameters, and ticketing information for failed uninstallation attempts.

This document details a script designed to uninstall the eClinicalWorks Client and its associated eCWDependencies applications from a computer. If the uninstallation fails, the script generates a ticket for further assistance.

This script uninstalls the Evo Credential Provider from Windows machines.

This document outlines a script designed to uninstall all HP bloatware from Windows workstations, detailing its operation, global variables, output, and ticketing system for failures during uninstallation.

This document provides a comprehensive guide on uninstalling Microsoft Office products using OffScrub. It details accepted versions, user parameters, task creation, and the execution of the script, ensuring users can effectively manage Office installations.

The script allows the uninstallation of Microsoft Office products via OffScrub. Accepted Versions: All, 2003, 2007, 2010, 2013, 2016, and C2R. Leaving the parameter blank will remove all installed versions.

This document details the implementation of the Invoke-VcRedistModule agnostic script for uninstalling Microsoft Visual C++ Redistributable using ConnectWise Automate. It provides an overview of the script functionality, sample runs, user parameters, and expected output.

This document provides a script for uninstalling New Teams from Windows machines, specifically designed to work with logged-in users. It includes details on file paths, hashes, global parameters, output, and ticketing information for failures.

This document provides a comprehensive guide on how to uninstall the SentinelOne agent from a Windows system, including steps for handling Anti-Tamper features. It outlines the requirements, process, and payload usage for executing the uninstallation successfully.

This document provides a detailed overview of a script designed to uninstall Microsoft Teams Classic from Windows machines, including parameters, output, and ticketing information for failures.

This document outlines the procedure for setting up a remote monitor to automate the removal of TeamViewer from Windows machines. It includes details on suggested configurations, ticketing information, and import instructions for the monitor.

This document outlines the setup for a remote monitor designed to uninstall VLC Media Player from Windows workstations, including configuration details, ticketing information, and import instructions.

This script assists in the uninstallation of a specific Windows update by allowing the user to input the KBID. It includes an option to authorize a system restart if necessary while also striving to prevent an immediate reboot unless required by the update.

Documentation for the Uninstall-LiveConnect command to uninstall LiveConnect and remove associated directories.

This document provides a detailed overview of a script that cleanly uninstalls the Live Connect software, which is used for Kaseya Remote Control. It outlines the process, requirements, and output of the script, as well as updates made to enhance its functionality.

Documentation for the Uninstall-N-Able command to perform the uninstallation of the N-Able Windows Agent.

This document provides an overview of a script designed to install specified patches on Windows machines, detailing parameters for rebooting, sample runs, and expected output logs.

This script automates the process of uninstalling all versions of Microsoft Office from 2007 to 2016 and O365. It downloads necessary offscrub files and handles machine or software corruption, ensuring complete removal of Office app shortcuts for the specified versions. Save time and effort with this efficient solution.

This document details a script designed to pull the highest agent version in a ConnectWise Automate environment and update any outdated agents. It highlights the time saved by automation and provides a sample run for reference.

This document provides a detailed guide on how to run the Office Click-to-Run client to update Microsoft 365 Apps using ConnectWise RMM. It includes sample runs, task creation steps, and necessary dependencies for successful implementation.

This document provides a step-by-step guide on how to create a device group for the Update Orchestrator solution in ConnectWise RMM. It includes dependencies, creation instructions, and criteria for grouping devices based on OS type.

This document outlines the process to automate the update of all installed Visual Studio versions using a ConnectWise RMM implementation. It includes step-by-step instructions for task creation, script setup, and execution, ensuring a seamless update process for users.

Documentation for the Update-AdobeCC command to list or update products for Adobe Creative Cloud.

Documentation for the Update-Office command to update Office 365 to the latest version.

Documentation for the Update-PowerShell command to update PowerShell Desktop to the latest version.

Documentation for the Update-PowerShellGet command to install or update PowerShellGet to the latest version available in the PowerShell Gallery.

Documentation for the Update-VeeamVulnerabilitiesPatch command to patch Veeam vulnerabilities in Versions 11 and 11a.

This document provides an overview of the Update Veeam Vulnerabilities Patch, detailing the requirements, process, payload usage, and output locations for effectively patching vulnerabilities in Veeam versions 11 and 11a.

Documentation for the Update-VisualStudio command to update all installed Visual Studio versions automatically.

This document provides an overview of how to set the custom field value for the OS Build on machines using the VSAAPI module. It includes requirements, process details, parameters for the script, and output information.

This document provides a detailed overview of a script that removes a user profile from an endpoint. It includes prompts for user confirmation and the username to remove, along with an example agent procedure log demonstrating the script in action.

This document outlines the procedure for silently removing VLC from systems where it cannot be uninstalled via winget. It includes example logs and the command used for uninstallation.

This document provides a reliable and accessible solution for application management using Chocolatey, detailing the implementation of associated agent procedures for software installation and uninstallation.

This document outlines the compatibility requirements for ProVal content on Mac and PC, detailing the necessary OS versions and PowerShell requirements for successful execution. It includes example logs from agent procedures, dependencies, and the processing steps involved in determining compatibility.

This document outlines the necessary parameters required for using VSAToolbox, a set of tools designed to interact with a Kaseya VSA server API. It includes details on dependencies, example data, and the correct format for API arguments.

This document provides a method to purge Kaseya agents that are older than a specified number of days using the API. It outlines the necessary parameters including user authentication, the URL of the VSA, and any exceptions to the deletion rule.

This document provides a guide on how to update OS build custom fields for Windows 10 using a web check via API. It covers the necessary parameters such as URL, username, and authentication method required for the process.

This document outlines the process of pushing custom fields to targeted machines or endpoints from the organization’s custom field set within Kaseya VSA. It includes details on updating machine records for patching, antivirus, monitoring, and third-party fields, along with the required parameters for executing the update.

This solution is designed to configure the automatic deployment of the Vulscan Discovery Agent application on Windows and Macintosh machines that are missing the agent, using the NinjaOne platform.

This document outlines the steps required to uninstall the Webroot application from endpoints using Kaseya VSA. It includes implementation details, required dependencies, and expected output logs for both successful and failed uninstallation attempts.

This guide provides step-by-step instructions on how to log in to the Webroot Portal and manage entities, including creating custom groups and obtaining necessary codes for Webroot agent deployment.

This document provides a step-by-step guide on how to log in to the Webroot portal, navigate to the site list, and set the Site KeyCode necessary for the client solution to function correctly.

This document provides a detailed overview of a script that applies WiFi configuration for a specified SSID, including dependencies, user parameters, and the process involved. It highlights the time saved by automation and includes a sample run of the script.

This document provides a comprehensive guide on how to convert HTML content into Markdown format, detailing the necessary steps, tools, and best practices for effective conversion.

This document provides a comprehensive guide on the updated script for managing Wi-Fi profiles, including features for adding, removing, and auditing profiles on end machines. It highlights the necessary updates, implementation steps, and associated content to ensure effective management of Wi-Fi profiles while enhancing security.

This document provides a detailed overview of the Set Admin Account script, which creates or updates a target admin user on a domain controller or local machine and saves the credentials to the passwords list for the Automate client. It includes usage instructions, parameter details, update notices, and sample runs.

This document provides a detailed overview of a dataview designed to audit cloud drive software and its versions on machines, ensuring compliance and up-to-date software management.

This document outlines a dataview that retrieves information about software installed on servers, specifically targeting Dell and HP server management software. It details the columns included in the dataview, such as client name, location, agent name, manufacturer, software status, software name, installation date, size, and version.

This document outlines a script designed to remove the Windows 10 Upgrade Assistant application from a target machine, detailing the process, dependencies, and expected outcomes.

This document provides a detailed overview of the available user profile sizes on a Windows machine, including dependencies, columns, and their descriptions for better understanding and utilization.

This document provides a comprehensive guide on implementing a script to set the active desktop wallpaper for all users from a local path or a URL. It includes options for enforcing the wallpaper on login and resetting to previous wallpapers.

This document outlines the reattempt procedure for Windows 10 feature upgrades that have failed, utilizing a specific agent procedure designed to handle upgrades without rebooting the system. It details the policy name, applied view, assigned organizations, and active policy objects.

This document provides a step-by-step guide on how to import the Procedure XML and PS1 file for ProVal Automation, including the addition of machine configuration for Windows 10 Build Result.

This document provides a detailed report of Windows workstations that have been upgraded to the new Win10/Win11 version within the last 30 days. It includes essential information such as client names, locations, computer IDs, upgrade dates, and the old and new OS versions.

This document provides a comprehensive overview of a solution designed to display information about applications installed on a machine, including their name, version number, and installation date. It describes the functionality of the script that gathers this information, how it is stored in a custom SQL table, and how users can access it through a dataview for effective management and monitoring of installed software.

The CWM - Automate - Script - Windows Installer Properties [DV] gathers and stores properties of applications installed on a machine, providing users with a structured overview of software management through SQL tables and dataviews.

This document provides guidance for users seeking assistance in converting HTML content to Markdown format. It emphasizes the need for the actual HTML content to facilitate the conversion process.

This document provides a comprehensive overview of how to gather the Windows Product Key from the designated role in ConnectWise Automate. It outlines the dependencies, the columns of data collected, and the significance of each data point in managing client systems.

This document outlines a role that utilizes PowerShell to retrieve the Windows Product key and verify its format, ensuring it adheres to the specified regex pattern. It includes detailed settings and applicable operating systems for effective implementation.

This document describes a script designed to collect available restore points on systems without the Target Restore Point EDF set and to restore systems when the EDF is configured. It details the process, dependencies, and output of the script, emphasizing the time saved through automation.

This document outlines a role created to detect the installation of the Windows Server Backup feature. It includes the detection string, comparator, and applicable operating systems for effective monitoring.

This document outlines a script designed to repair and reset Windows update settings, aiming to resolve potential patching issues on Windows devices. It details the script’s dependencies, global and user parameters, process, and expected output, including logging of successes and failures.

This document describes the Update Orchestrator Autofix Script, designed to prevent unauthorized reboots and patch installations on endpoints by renaming the reboot file. It operates as an autofix for the Update Orchestrator Service Status Detection monitor, ensuring that updates are managed with prior approval.

This document provides a detailed overview of the Windows Update Report Dataview, including its dependencies, columns, and descriptions of each column. It is essential for displaying a list of patches installed or available on local machines, populated by specific scripts and solutions.

This document provides a comprehensive solution for managing software installations, updates, and uninstalls using Winget. It includes associated tasks for installing, uninstalling, and upgrading applications on endpoints, ensuring efficient software management.

This document provides a detailed overview of a PowerShell script that exports the list of installed applications in JSON and CSV formats using the Winget command. It also includes functionality to email the generated reports to specified addresses, with options to customize the output format and recipients.

This document provides a detailed guide on using a script to install applications via winget from a JSON file. It also includes instructions for creating tickets for failed installations, ensuring a streamlined software deployment process.

This document provides a detailed guide on how to install a Winget package on a target endpoint, including sample runs, dependencies, and parameters required for the process.

This document provides an implementation guide for deploying the Teams Machine-Wide Installer application using a script based on the SWM - Software Installation - Script - Winget. It includes parameters, sample runs, and output logs for effective deployment.

This document provides a detailed overview of a script designed to remove a Winget package, including its parameters, dependencies, and sample run output.

This document provides a detailed overview of a script designed to update all Winget packages found on an endpoint. It includes sample runs, dependencies, global parameters, and output information.

This document provides a summary of the Winget App Audit script, detailing the information displayed for applications supported by Winget. It includes dependencies, explanations of key columns, and insights into application management and updates.

This guide provides a comprehensive overview of implementing the Winget Auto Update solution, including the necessary auditing and automation content, configuration steps, and monitoring setup to ensure that winget-supported applications are kept up to date and their statuses reported effectively.

This document provides a detailed guide on how to create and execute a PowerShell script to install applications using Winget on Windows devices. It includes parameters, dependencies, and step-by-step instructions for script creation and deployment.

This document outlines a suite of 5 agent procedures designed for managing WinGet packages on endpoints using ProVal Agnostic Script. It includes instructions for installing, uninstalling, updating, exporting, and importing WinGet packages, along with usage examples and log outputs.

This document provides a detailed guide on how to uninstall an application using Winget on Windows devices. It includes parameters, dependencies, and a complete PowerShell script for implementation.

This document outlines a PowerShell script that utilizes Winget to upgrade all available packages on a Windows endpoint. It checks for prerequisites, installs Winget if necessary, and executes the upgrade process in a silent manner, ensuring all compatible software is updated efficiently.

This document outlines a procedure that uses the WinSAT agent to capture and store various performance scores into custom fields. The scores include CPU, Disk, Graphics, and Memory, providing valuable insights into machine performance.

This document provides an overview of the Azure AD Connect version installed on endpoints, detailing its dependencies and field descriptions for effective auditing and management.

This document explains how the OS Install Date field is updated by the agent procedure on an endpoint, detailing its dependencies and providing a summary of its functionality.

This document outlines the creation of a custom field that indicates whether an endpoint is compatible or provides reasons for incompatibility, including various conditions such as outdated operating systems or PowerShell versions.