Jump to content

szkoda

Members
  • Content Count

    30
  • Joined

  • Last visited

  • Days Won

    2

szkoda last won the day on February 28

szkoda had the most liked content!

Community Reputation

5 Neutral

My Information

  • Agent Count
    Less than 100

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. szkoda

    Simple Website Content Checking Monitor

    custom script - works like a charm! I ended up moving the monitor to another server that is unrestricted outbound.
  2. szkoda

    Simple Website Content Checking Monitor

    Got it working now, oversight on my part, the location where the server is that the monitor is running on was being blocked by the firewall as we only allow 80 and 443 outbound for that particular server.
  3. szkoda

    Simple Website Content Checking Monitor

    I'm using OP's script which works fine for regular URL's but doesn't seem to like http://www.example.com:1234 - I would like to be able to monitor a website with a custom port for specific text (to tell if it is up or down).
  4. szkoda

    Simple Website Content Checking Monitor

    Sorry to resurrect an old thread but anyone know if this monitor should work with a website that is accessed on a custom port? I can get it working on a normal website but not one with a custom port, it just gives the error: "C:\Windows\LTSvc\websiteCheck.vbs(8, 1) msxml6.dll: The server name or address could not be resolved"
  5. I use powershell with the "Execute Script" function to run the below which works solidly for me: $domain = "DOMAIN" $machineName = "@machineName@" $password = "PASSWORD" | ConvertTo-SecureString -asPlainText -Force $username = "$domain\administrator" $credential = New-Object System.Management.Automation.PSCredential($username,$password) Add-Computer -DomainName $domain -newname $machineName -Credential $credential
  6. szkoda

    Finding Disk Monitors

    Do not edit these scripts directly, it will get overwritten when you update LT. Copy the script, rename then edit it.
  7. szkoda

    Endless Refreshing

    Yep we get this intermittently too, have to crash out of CC and go back in to fix. Because of it's randomness it's difficult to log to support.
  8. Disk space gets recorded into the DB for historical reporting but I'm not sure about CPU, Memory etc.
  9. Figured someone might find this useful and surprisingly I got the answer from support! I was looking for a way to see drive history for any agent over any period of time and while Automate stores this information in the DB it does not provide any easy way to view it on the front end (that I am aware of) with a nice pretty graph. The easiest way I have found to extract this info is to use the "Drive Detail" report in the report center and copy then edit it. With the report open in the report designer follow the steps below to edit the report: 1. Open report in Report Designer 2. Click Edit Data Source on the toolbar along the top 3. Click on Drive History and click Edit 4. In the Where SQL box enter the following: DateDiff(Now(), DriveDateRecorded) < 365 This will make the graph on the page display the history of the drive usage on the agent over the past year. You can change the 365 number to any number to get a graph over various days. If you want to show drive usage history between 2 particular dates you can do that with the following statement and edit the dates as required: ((DriveDateRecorded > '2017-03-01') AND ( DriveDateRecorded < '2017-05-01') ) 5. Once you have configured the statement as required press ok to everything then publish the report to the database by pressing the button in the toolbar. No doubt someone will be along shortly to tell me there is an easier way to do it but in case there isn't I thought I would put this out there who's not an SQL wizard (like me).
  10. Thanks for this Gav, works a treat. We have had a requirement from a client to pull historic uptime figures for their servers - i.e. last months uptime, uptime in month x etc. Any ideas how this can be done?
  11. szkoda

    EV - Failed Logins* - making it usable?

    Mind sharing your config?
  12. szkoda

    EV - Failed Logins* - making it usable?

    Stupid question but how do I get this into a remote monitor? Do I need to use External EXE check?
  13. I'm planning on using this for our hosted terminal servers, can someone just confirm I've got the config correct? When I build the query I get no results but I'm not sure if this is because we are super secure or I've configured the monitor wrong?
  14. szkoda

    Automate 12 - Should I Upgrade?

    Not sure if this is a bug or what but if I go into groups on V12 and select a machine then click "Control" it always connects to the same machine - anyone else notice the same? Connecting to machines from the clients screen works fine.
×