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.
We have customers who need to know if their computer (Remote) is off line for more than 15/30 minutes.
initial extension revision here: http://forum.screenconnect.com/yaf_postst9819_Extension--Offline-Machine-Notifications.aspx#post34665
due to potential concerns with scaling, the timer is currently limited to 2 minutes. this can potentially be increased depending upon feedback.
Hey Kurt,
Have you tried out the Offline Machine Notifications Extension? It would allow you to add a time delay to your trigger.
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