Jump to content

Automation Theory

Members
  • Content Count

    44
  • Joined

  • Last visited

  • Days Won

    3

Automation Theory last won the day on June 9

Automation Theory had the most liked content!

Community Reputation

11 Good

My Information

  • Agent Count
    > 6000 Agents

Converted

Recent Profile Visitors

263 profile views
  1. @Todarivah Yes, it is. EDFs are defined in the extrafield table. You'd use an insert statement to create the new EDF -- but to use it you'd need to get the newly generated ID column value, which is an autoincrement column in the database. Once you have the ID you can use an insert statement into the extrafielddata table to set that new EDF to a value for the particular entity you created it on. Generally it's not a common use case to programatically generate EDFs in the long term. If you're looking to do some initial setup there's no issue, but as others have mentioned there are other way
  2. Your other option here is to create a maintenance window (standing maintenance mode applied on a schedule) and then define it on a group/location level. This tends to be a unique requirement for clients, but in theory you could make it an auto-join group with a search and EDF if you anticipated other clients would have similar needs in the future.
  3. A couple years ago I worked with a CW consultant who mentioned a "core-only" migration of Automate -- that is moving over only the tables needed to make the application run. I couldn't find the list of tables posted anywhere, so I wanted to post them here. Please note that there's an awful lot of items missing here (think of this like a "reset my server, keep my agents and users" measure). I'd advise anyone thinking about this that groups, scripts, monitors, searches, EDFs, and Connectwise Control are all missing. So too are all the tables for Patch Manager -- so with that, most partners
  4. @aXz It's definitely possible to restore, but I'd advise grabbing the nightly DB zip file backup (as @SteveYates suggests) if you have it and selectively importing only that table. If you're a single server then it's also not a big issue to restore the whole VM -- but if you're a split server your web service passwords will be out of sync (fixable with the right tools).
  5. @dspac Yes; this is known as the "perms loop" in Automate. It will delete any account with the wildcard host specifier (for split servers; localhost for non-split servers) in MySQL that does not match an application user. However, you can get around this by specifying a hostname (as follows): CREATE USER 'username'@'hostname' IDENTIFIED BY 'password'; You can change 'hostname' to be the IP address or DNS name of the source of your MySQL connection. Let me know if it gives you any issues (I'm a MySQL DBA).
  6. 2019 isn't officially supported by ConnectWise since MySQL 5.7 isn't officially supported on Server 2019, but with that said I myself along with others haven't had any issues with the combination. As far as in-place upgrading I can't think of any issues off the top of my head, but I myself haven't performed that exact operation. [Also, FWIW I think 2012 can go directly to 2019; but I'd spot check the docs -- the last time I did this it was a 2008 R2 --> 2012 --> 2019.] With that, as long as you have good backups I think it's safe to try. Automate infrastructure is a specialty
  7. Sorry I haven't replied earlier -- you might be having MySQL issues, but buffer and size aren't among them. Automate servers are write-heavy into MySQL since they update inventory from all the agents. It's normal that you're seeing that behavior. As a DBA I'm going to disagree with some of the above advice; check out my post here: https://automationtheory.org/top-5-myths-about-the-automate-database/ Chopping out data from your DB won't do a lot (especially since yours is so small; my prod with ~10k agents is ~55GB). I'd move to SSD's, and start with a buffer pool that's at least 80%
  8. Update: We've posted the above information with some additional details to our website: https://automationtheory.org/reverse-proxy-for-connectwise-automate/ We've also added header modifications to the beta appliances; it will add the search engine de-list header as described here, add best practice security headers, and remove headers that reveal the server/framework version that the Automate server is running. You can check your current production server headers here: https://observatory.mozilla.org/
  9. @tlphipps If you'd like to test it you can use the Chrome developer tools; go to the network tab and reload a page in the webUI. Then click an item and look at the headers section:
  10. Hi Everyone, In light of recent events, I'm rushing a product to beta. I've created a hosted appliance for Automate-stack network security that does the following: Reverse proxies web traffic (Automate and Control) Uses an IPS to scan incoming traffic and drop malicious content (including certain forms of SQL injection) Implements IP blocking based on GeoIP, Tor node status, and other reputation technologies Obfuscates your server with a jibberish FQDN Let's talk technical brass tacks. This solution works for all TCP and UDP traffic (UDP is VPNed back to the se
  11. @jhand Others have reported the email going to spam; seems to depend how aggressive the filter is. It should come from support@auto...theory.org and it normally sends immediately after you confirm. I can definitely resend it if it hasn't arrived.
  12. Thanks @BlueToast ! It was definitely an interesting balance keeping the UI clean -- and it resulted in a lot of keyboard shortcuts. The documentation page (linked in the download email) lists them all. We hope that this plugin gives a best-in-class user experience for MySQL access, especially for hosted Automate partners.
  13. Hi Everyone, Here at Automation Theory we think access to the Automate database is very import for every Automate admin, along with some basic statistics for monitoring database load and what the app is doing with the DB (and that you shouldn't have to pay for it!). We're excited to announce the launch of a FREE plugin we call Database Commander. It shows important MySQL load/performance demographics and has a query editor, complete with table name autocomplete and syntax highlighting. Features: Live MySQL load and performance data Syntax highlighting
  14. @J_anon1234 As far as I know SQL Spy is 100% read-only, and it is designed for read-only monitoring. I wouldn't worry about it. However, even if it were read/write the query would simply fail if it was improper SQL syntax.
  15. @TonyPags Empirical results are always good, especially when they are the ones we want. I'm glad to hear that all is well with your server! On the topic of signup: In my production stack I err on the side of getting an agent installed -- I don't use the blacklist for software MACs; I let the trigger take care of inventory data and I send a script out to scrape the physical MAC and update the DB with that value (I don't want to have a tech on the phone trying to fight an agent install that will never work). However, this is a matter of preference, and what is appropriate will depend
×
×
  • Create New...