Jump to content

10 files

  1. Script Backup

    This solution will export customizations into a folder hierarchy based on each type of backup. It uses only Automate scripting functions so it is compatible with both Cloud Hosted and On-Prem servers. It should be compatible with MySQL 5.6 and Automate Version 11+.
    Script Backups will be placed in folders matching the script folders in your environment. Each time a script is exported, the last updated time and user information is included, providing multiple script revisions as it is changed over time. This script does not decode the scriptdata, so script dependencies like EDF's or other scripts will not be bundled in the XML export. But if you are just looking to undo a change, the script dependencies should exist already. Scriptlets will not be "versioned", but it will detect when they have changed and will only back up new or changed Scriptlets.
    Additionally, the following item types will also be backed up: Internal Monitors, Group Monitors, Remote Monitors, Dataviews, Role Detections, ExtraData Fields, and VirusScanners.
    The backups will be created at the folder identified by "@BackupRoot@", which you can provide as a script parameter when scheduling if you do not want to use the default path. Target the script against an online agent, and the script data will be backed up to that computer. Future runs will reference the saved "Script State" variable for that agent and will only include the scripts updated since the last successful backup. Backup verification is performed, if a script backup file was not created as expected, the backup timestamp will not be changed allowing the backup to be attempted again.
    The attached .zip bundle contains scripts actually backed up by this solution. Import the "Send Email" script first, and then import the "Backup" script. If there are any problems or you would rather import a script exported by Automate, the "Backup Automate Scripts (and More).xml" is included as well. You do not need to import all three files!
    Just schedule this to run daily against any agent to establish your script archive.
    script version revision archive backup

    128 downloads

       (3 reviews)

    0 comments

    Updated

  2. Suspend script if too many are active

    This script is used to suspend any other scripts that may be running by the same name if too many of it are active on the same client at once. This has the practical effect of sleeping a script, recording it's place in line and checking again in 30 seconds to validate if it's time to try again. 
     
    To use it, set a variable in your script of MaxRuns to however many you want to run at a time, add a 15 second sleep step then use the script run function to call it. This allows it to effectively build the queue and then process them as they come in. Once it's time for that one to resume, it will return to your source script and continue. 
     
    Special thanks to @danialbulloch, who without his help this script would have not happened. He was both the inspiration and the source of the SQL query that makes it all work

    4 downloads

       (0 reviews)

    0 comments

    Submitted

  3. Mass force device redetection across all Network Probes

    Run this against your Automate Server (or any agent really) and it will loop through all of your Network Probes and force a device redetection on all of them. This is the same as doing Commands > Probe > Run Device Detection, unfortunately this behaviour is not exposed in the GUI when you select more than one network probe.

    This is step 2 of pushing updated device detection templates to probes.

    18 downloads

       (0 reviews)

    0 comments

    Submitted

  4. Mass refresh Probe Configs across all Network Probes

    Run this against your Automate Server (or any agent really) and it will loop through all of your Network Probes and push a Probe config update out to all of them. This is the same as doing Commands > Probe > Refresh Config, unfortunately this behaviour is not exposed in the GUI when you select more than one network probe.

    This is step 1 of pushing updated device detection templates to probes.

    19 downloads

       (0 reviews)

    0 comments

    Submitted

  5. Automate Server Public IP Check

    The IP for a Hosted Automate Server is not guaranteed to remain fixed, but if you do not include the IP in your Server Address template setting, your agents will not be able to communicate if DNS isn't working. See https://docs.connectwise.com/ConnectWise_Automate/ConnectWise_Automate_Knowledge_Base_Articles/Server%3A_Moving_to_a_New_FQDN for instructions on configuring alternate server addresses.
    (Official Statement concerning Hosted Server IP Addresses - https://docs.connectwise.com/ConnectWise_Automate/ConnectWise_Automate_Knowledge_Base_Articles/Cloud%3A_Cloud_Server_IP_Address)
    This script is a CLIENT script, which can be scheduled to run once or a few times each day. It will determine which probes are online and begin asking them to resolve the IP of your Automate server, and will continue asking agents until at least 5 agents have responded with the same IP. Once the IP has been determined, any templates that include an IP address but do not include the current IP will be flagged as needing an update. Because this solution is distributed and works without any LTServer commands it is suitable for use in Hosted and On-Premise environments.
    After importing the script, you must set the hostname and email address for notifications inside the script. To schedule the script, go to Dashboard -> Management -> Scheduled Client Scripts and add the script with whatever schedule you like. Here is a suggested schedule:

     

    12 downloads

       (0 reviews)

    0 comments

    Submitted

  6. Trend Micro WFBS Services Removal

    This is the script that I developed to manage removal of our Managed AV. It supports Windows and OSX installations. If it does not detect the product on the Agent it will skip removal attempts. It uses some known package GUIDS and can accept a removal password. It will leverage the Agent Removal script included with the Trend Micro Plugin for Automate if you have it. If the primary removal steps fail, it retrieves an uninstaller tool that Trend Micro released a few years ago (a copy is included in the bundle since they seem to have taken it down) to clean the system. Finally, it will try some batch/vbs script steps that I made to try and disable or cleanup the software manually. It supports a "ForcedRemoval" option that always triggers all the cleanup steps and skips testing if the product is installed.
     

    55 downloads

       (0 reviews)

    0 comments

    Submitted

  7. Remove Continuum Agent Software

    This script will trigger removal for the following applications (in this order):
    ITSupport247*Gateway
    ITSupport247*MSMA
    ITSupport247*DPMA
    ITSupport247*
    ITSPlatform
    LogMeIn
    This is just using a generic PowerShell script I made that searches for applications by name and then runs their uninstaller command. It has no specific knowledge of the applications.
    If the command uses msiexec, it will make sure that the action is uninstall (/x) and it will ensure it runs silently. (adds /quiet /norestart, removes any other /q* parameter). If the command is anything else, it will just add the "/s" parameter if there is not already a parameter like "/s*" in the command.

    123 downloads

       (1 review)

    2 comments

    Submitted

  8. Verify and Manage Workstation Admin Credentials

    This is a script to test and create or reset the Cache/Location Drive user account credentials and Location Admin credentials. If the credentials are domain based (domain\username, username) they will be tested but will not be reset. If the cacheuser is defined, cannot be validated, and is a local account (.\username) it will be created if missing and the password will be reset. After testing the cache user credentials, the Location Admin will be tested. If it cannot be validated and if it is a local account it will be created if missing, the password will be reset and it will be added to the local Administrators group. The password is always set not to expire if it is being reset.
    This script relies on the correct Location configuration of the "Login for Administrator Access" the under the "Deployment and Defaults" tab to obtain the Admin credentials. The Cache User credentials are specified by the Location Drive settings on the General tab for the Location.

    158 downloads

       (0 reviews)

    0 comments

    Submitted

  9. PowerShell Deployment Scripts

    I used the stock PowerShell 2.0 update script, and modified it for PowerShell 3, 4, and 5. I attempted to cover pre-requisites checks to prevent installing on systems with incompatible applications or operating systems. The scripts will check if the KB is reported as installed after the update completes to determine status. This means that the script will report the update was successful even if a reboot is still needed.
    The attached .ZIP has 3 scripts, one for each version, in a single XML bundle. To import the Scripts, select Tools -> Import -> XML Expansion. After import the scripts should appear in the "__Examples" folder. This pairs nicely with the PowerShell Version Roles at https://www.labtechgeek.com/files/file/13-powershell-version-roles/

    213 downloads

       (1 review)

    4 comments

    Updated

  10. Active Directory Plugin - Force Update of AD Information

    This script forces an update of the Active Directory remote plugin and tries to push in the most up to date information. 

    130 downloads

       (0 reviews)

    2 comments

    Submitted

×