Jump to content

WernerB

Members
  • Content Count

    2
  • Joined

  • Last visited

Community Reputation

0 Neutral

My Information

  • Location
    West Coast
  • Agent Count
    1500 - 2000 Agents
  1. WernerB

    Everyday, All Day Patching

    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
  2. 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.
×