Can we have a parameter that says that we only get notifications when a remote PC has been off line for say 15 minutes, and we only receive a reconnection notification if it has been off line for more than 30 minutes?
We have setup the triggers that seem to be working well. However due to temporary fluctuations in the internet connections we receive disconection notifications with almost immediate reconnections only a few seconds apart.
We have a trigger that notifies us when machines go offline or online however when we need to restart the ScreenConnect server it spams us. Could we have a delay when the server starts before triggers start working? In the same area could we have the option to have the server disable triggers when the ScreenConnect server is being shutdown?
Please add the ability to have a delay option in your triggers! I use the Offline Machine Notifications extension which is great but doesn't allow for HTML notifications. If that could be adjusted that would be a great start however there is so much power in your guys triggers. If there was a delay on something being triggered not only could you use this for offline machines but also you could delay cmds and have auto fixes through control. Hmm maybe even give Automate a run for it's money.
I see, makes sense now. The biggest thing here is just having the ability to delay triggers. Then you could really do a lot with this.
I have a nice HTML online alert for this as well. Set HTML as True and drop this code in body ;-)
I've got you on that one, create a new trigger servers online
Event Filter:
Event.EventType = 'Connected' AND Connection.ProcessType = 'Guest' AND Session.GuestOperatingSystemName LIKE '*server*' AND Session.HostConnectedCount = 0
Add as SMTP Mail
Subject:
Server Online
Body
{Session.Name} started responding at {Event.Time}
Glad this has been picked up! For us the best result would be just a simple text box where you can put in seconds before a trigger actually triggers (allow a different time for each created trigger).
So if I had 2 triggers one for "servers" and one for "clients" I could set a ~60 second timer for "servers" just to remove any internet blips and reboots and a ~300 second for "clients".
Im not sure if it's changed yet but the reason we don't use the extension was that it didn't include when a machine comes back online.
As a side note, my ticket was merged here and another large problem we have is if the Control server reboots it floods us with every machine coming online. Would it be possible to delay triggers on the Control Server all together for like 60 seconds while it settles from a reboot?
Please add the ability to have a delay option in your triggers! I use the Offline Machine Notifications extension which is great but doesn't allow for HTML notifications. If that could be adjusted that would be a great start however there is so much power in your guys triggers. If there was a delay on something being triggered not only could you use this for offline machines but also you could delay cmds and have auto fixes through control. Hmm maybe even give Automate a run for it's money.
I want to use trigger definitions about the guest to send email notifications about a Guest when a Guest connections. More specifically, definitions such as Session.GuestLoggedOnUserName and Session.GuestMachineName.
Because triggers fire immediately, these definitions do not have time to update and they come through blank in an email. I brought this up here: http://product.screenconnect.com/topics/1154-sessionguestloggedonusername-and-sessionguestmachinename-blank-on-first-trigger-email/#comment-3155
If I could set a short delay before the trigger fires, giving time for these Guest-specific definitions to update, it should solve the issue. I am only looking to have seconds in my instance.
for instance, if a server is offline for 30+ days, have an is activate a trigger event