Jump to content

Search the Community

Showing results for tags 'administrator'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • MSPGeek
    • Announcements
    • The Geek Cast
    • Code of Conduct
  • ConnectWise Automate / Labtech
    • ConnectWise Automate / LabTech
    • ConnectWise Automate / LabTech - Development


  • ConnectWise Automate
    • Scripts
    • Plugins
    • SQL Snippets
    • Role Definitions
    • Automate PowerShell Code
    • Reports
    • Internal Monitors
    • Remote Monitors
  • ConnectWise Manage
    • API Interacting Code

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



About Me


Agent Count













Found 2 results

  1. Hi Guys, Trying to get some ideas and thoughts on how everyone has there CW Automate Deployment & Defaults - Login to use for Administrator Access configure. Fairly used to CW Automate after 1+ year plus using the system and I am trying to make minor improvements in our CW Automate environment. This post is to do with using domain admin details in the Deployment & Defaults - Administrator Access. I would like to use local admin credentials instead of Domain admin credentials in the Deployment & Defaults - Administrator Access. This works great for our cloud based tenants no on-site servers, however I am struggling to find an ideal solution to facilitate the use of local admin details for clients with Domain servers. As you might know DC's cannot have local admin details configured on the server so finding a one fit all solution has been a pain. I thought about creating a new location for each client and have the servers in there or the DC but that might mitigate the issue of domain admin used for all devices, however my main aim to remove domain admin details from Automate entirely. Looking forward replies and ideas. Thanks
  2. 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. The attachment has been moved. See https://www.labtechgeek.com/files/file/24-verify-and-manage-workstation-admin-credentials/
  • Create New...