Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

My Information

  • Location
    West Coast
  • Agent Count
    1500 - 2000 Agents
  1. Hey all, I've noticed that a lot of server roles seem to be completely broken and no longer detect on our Automate 2020 server. Things like "Windows Terminal Gateway Server" appear to be querying system caption which just reports back the OS version if I run it manually so it isn't going to detect anything. Does anyone have updated Role definitions for things like server 2012R2+ RD Gateway, RD Web etc that they could share?
  2. @Automation Theory Any recommendations on doing this type of migration with MariadB 10.0 > MySQL 5.6 (as from documentation that is cross compatible) ... or should we look at upgrading Maria to 10.2.x to migrate to MySQL5.7?
  3. Hey all, There's a fair bit of mixed info when googling about hosted Automate (a lot of it looks old and probably not a thing anymore). With a fresh perspective of how it is NOW would you 'do it again' if already in the cloud, or not? What are some points against going hosted Automate beyond a slight performance hit? We are currently weighing the 'silent costs' of maintaining our internal environment (VMs running on in our office) vs moving Automate to Connectwise hosted in cloud and wondering if anyone currently using it that isn't part of the CW Marketing team can share how they feel about the in cloud world and whether there are issues significant enough that could effect decision and value that the hosted offers. Thanks, Werner
  4. @MrRat Looks like there's a 'bug' with the account creation for the LOCAL admin accounts if the generated password is >14 Characters (due to legacy windows 2000 compatibility check net user command does) leading to accounts not being created. Could you alter the command that gets issued by the plugin to include a "/y" at the end of the net user command, this should fix long min password length settings? right now its generating something like: cmd!!!/C net user /add /fullname:"MSP_Name mspadmin" /comment: "MSP Local Service Account - 56" "MSP_admin" "Thisrandomlongpassword" && net localgroup Administrators SD_sdadmin /add Output: No valid response was provided. The password entered is longer than 14 characters. Computers with Windows prior to Windows 2000 will not be able to use this account. Do you want to continue this operation? (Y/N) [Y]:
  5. Setting a long window like that will mean that it will end up waiting 23hrs to reboot. My thought would be to not use patch manager, but something like Powershell Windows Update module, create an automate script to download and add that, run a get, then install, check reboot status, reboot if needed and rinse and repeat either a few times or if you can figure out how to get it to parse output for no remaining updates available to stop there. https://gallery.technet.microsoft.com/scriptcenter/2d191bcd-3308-4edd-9de2-88dff796b0bc
  6. If anyone else is having problems with the SQL Query erroring on the monitor on Automate 12, I reformatted it and seems to be happy for me: SELECT TIMESTAMPDIFF(MINUTE,c.LastContact, IFNULL(LastHeartbeatTime, "0000-00-00 00:00:00")) AS TestValue, c.name AS IdentityField, c.ComputerID AS ComputerID, c.LastContact, h.LastHeartbeatTime, acd.NoAlerts, acd.UpTimeStart, acd.UpTimeEnd FROM Computers AS c LEFT JOIN HeartBeatComputers AS h ON h.ComputerID = c.ComputerID LEFT JOIN AgentComputerData AS acd ON c.ComputerID = acd.ComputerID LEFT JOIN Clients ON Clients.ClientID = c.clientid WHERE (c.LastContact > NOW() - INTERVAL 30 MINUTE OR h.LastHeartbeatTime > NOW() - INTERVAL 30 MINUTE) AND TIMESTAMPDIFF(MINUTE,c.LastContact, IFNULL(LastHeartbeatTime, "0000-00-00 00:00:00")) > 6 OR TIMESTAMPDIFF(MINUTE,c.LastContact, IFNULL(LastHeartbeatTime, "0000-00-00 00:00:00")) < -6 I can't seem to get the powershell to work though, get a null object error.
  • Create New...