Jump to content

Search the Community

Showing results for tags 'password'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

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

Categories

  • 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

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me


Location


Agent Count


INTERESTS


OCCUPATION


ICQ


WEBSITE


WLM


YAHOO


AOL


FACEBOOK


GOOGLEPLUS


SKYPE


TWITTER


YOUTUBE

Found 8 results

  1. The root password is something that is easy to forget about until you really need it. Then it becomes a wild goose chase looking through password managers, documentation systems, and any other place that password might be used. This guide is meant for the situation where database maintenance is required and the root password is unknown. Items worth noting Every super admin account in Automate has the same permissions in the database as the root user. If your server has been around for a while (pre 10.5) it might be plain text in the registry under the key HKLM\Software\WOW6432NODE\LabTech\Setup There's nothing special about the root account -- it's very similar to Administrator in Windows. Best security practice is to create a new account with the super permission and not use root (unfortunately in the CW Automate world this best practice is difficult to implement). IMPORTANT: This guide is actually going to instruct you how to create a new account with the super and grant permissions -- we won't actually be resetting the root password. The root password used at server install is encrypted and stored in the registry and is used by Automate patches and other support utilities. If you change the root password you're going to break things in Automate down the road. An example, the 2020.2 patch: Now, without further ado, the new super account creation process. To begin, here's a screenshot to show that we're locked out of a new MySQL 5.7 instance: [In case you're wondering, MySQL 5.7 randomly generates a root password if one is not specified, and it's recorded in the error file.] Create a text file with the following commands, and save it as a .sql file: CREATE USER 'rootbeer'@'localhost' IDENTIFIED BY 'abc123!'; GRANT ALL PRIVILEGES ON * . * TO 'rootbeer'@'localhost' WITH GRANT OPTION; GRANT PROXY ON ''@'' TO 'rootbeer'@'localhost' WITH GRANT OPTION; FLUSH PRIVILEGES; I'll be calling the account 'rootbeer' and using an insecure password for the sake of demonstration. Good security practice is strongly advised. Stop the service LabMySQL Open an administrative command prompt, and navigate to the bin folder of your MySQL install, wherever mysqld.exe is located. Start MySQL passing the script you created in step one as the init-file parameter. mysqld.exe --console --init-file C:\path\to\reset.sql When the server starts it should show in its output that it ran the script. Press CTRL+C to shutdown the server once you see this. As you can see in the other window, we're successfully able to login. Start LabMySQL again. Login as your new super account. As you can see here, ours has all global privileges and the DBA role. Hopefully this guide has been useful to you. If you ever need support for the Automate database and want a professional DBA opinion feel free to reach out to us: https://automationtheory.org/
  2. Hey everyone, Not sure if this is the best place but i was hoping to see if anyone had done any integration with CWA and Thycotic Secret Server. The goal would be to rotate SVC account passwords,domain account passwords, AuthAnvil Breakglass passwords. I don't see much documentation on this topic and I know about the API but was wondering if anyone has been down this road before. Any insight/tips/tricks is most appreciated.
  3. Hello, I am trying to change the Domain Administrator Password with a shell script (net user user_name * /domain) run as user with administration rights the script works on all PCs in a the domain except the DC. If i try it on the DC directly in the command line I can change the password if i run the command line as administrator with the same User it does work. Is there a possibilty to run the shell as a User and with Administrator rights? Or is there an other way to fix this?
  4. I am working on a script to add a user and make it admin .. this is done.. but is there a way to add the password to the password list for the customer location in labtech with the script? It would help on so many levels.. Anyone have a pointer on this? I want to run it once a month to update the passwords and for each customer group.. ltadmin create and hide.xml
  5. Can someone give me some indication of how labtech utilizes credentials... when a script or patch or command is issued.. what credentials are used? when you install an agent on a remote system.. if it is not joined to a domain.. how does labtech get the elevated credentials ?
  6. can someone give me some indication of how labtech utilizes credentials... when a script or patch or command is issued.. what credentials are used?
  7. I installed the Expiry plugin and users are listed with the number of days left until password expiration. The issue I am having is the email is being sent with "Domain Password Expiration Notification" in the subject line and "Ok" in the body. It should email the users a specific template made in html with the user's name, how many days left, and a link to reset the password. Any idea why this would be happening?
  8. Hi we are looking to address a critical security flaw lets anyone gain root access to a Mac running macOS High Sierra. We would like to make sure the root account is set with a password as that is the recommended best solution for anyone running OS High Sierra. Any thoughts on how one may be able to achieve this from the dashboard? When I check System > Users the user box is blank. Here is an article discussing the security flaw: http://bgr.com/2017/11/28/macos-high-sierra-login-bug-hack-how-to-fix/
×
×
  • Create New...