 Rank: Member Medals:  Joined: 8/28/2012(UTC)
Posts: 34
Thanks: 7 times
Was thanked: 3 time(s) in 2 post(s)
|
Per subject - I've been trying to setup an e-mail trigger for in the event a PC is stolen or we're asked to advise when a PC connects to the internet and it has our unattended installer on it.
Event.EventType = 'Connected' AND Connection.ProcessType = 'Guest' AND (Session.GuestMachineName = 'ComputerNameHere')
I've tried the ComputerNameHere as the computer name and the FQDN (i.e ComputerNameHere.domain.local) but I've been unable to trigger this.
I could have swore I had this working successfully in previous versions of SC - I'm on 6.8 at the moment.
Am I missing something obvious? Any help is appreciated.
|
|
|
|
|
|
 Rank: Advanced Member Medals: Joined: 9/5/2013(UTC) Posts: 64  Location: Central Kannsas Thanks: 27 times
Was thanked: 5 time(s) in 5 post(s)
|
This is the format I'm using, to watch for stolen computers.
Session.SessionType = 'Access' AND Event.EventType = 'Connected' AND Session.Name = 'Computer Name'
The Computer name above is the name you give it in ScreenConnect or in other words the name of the session.
|
 1 user thanked myers6mm for this useful post.
|
|
|
|
Rank: Member Medals: Joined: 8/28/2012(UTC)
Posts: 34
Thanks: 7 times
Was thanked: 3 time(s) in 2 post(s)
|
Originally Posted by: myers6mm  This is the format I'm using, to watch for stolen computers.
Session.SessionType = 'Access' AND Event.EventType = 'Connected' AND Session.Name = 'Computer Name'
The Computer name above is the name you give it in ScreenConnect or in other words the name of the session. Just tried this and still no joy but the mail alert tests are coming through fine and other event triggers (like new support sessions etc) are working so I know the SMTP details are correct. So weird.
|
|
|
|
|
|
Rank: Member Medals: Joined: 8/28/2012(UTC)
Posts: 34
Thanks: 7 times
Was thanked: 3 time(s) in 2 post(s)
|
Originally Posted by: vexation Originally Posted by: myers6mm This is the format I'm using, to watch for stolen computers.
Session.SessionType = 'Access' AND Event.EventType = 'Connected' AND Session.Name = 'Computer Name'
The Computer name above is the name you give it in ScreenConnect or in other words the name of the session. Just tried this and still no joy but the mail alert tests are coming through fine and other event triggers (like new support sessions etc) are working so I know the SMTP details are correct. So weird. Any ideas what I can do to troubleshoot this? Is there a log I can look at? I tried changing the Filter to just Event.EventType = 'Connected' AND Session.Session.Type = 'Guest' amongst others (ignoring the need for a specific computer name, I just wanted SOMETHING to trigger) and still nothing.
|
|
|
|
|
|
Rank: Member Medals: Joined: 8/28/2012(UTC)
Posts: 34
Thanks: 7 times
Was thanked: 3 time(s) in 2 post(s)
|
Originally Posted by: vexation Originally Posted by: vexation Originally Posted by: myers6mm This is the format I'm using, to watch for stolen computers.
Session.SessionType = 'Access' AND Event.EventType = 'Connected' AND Session.Name = 'Computer Name'
The Computer name above is the name you give it in ScreenConnect or in other words the name of the session. Just tried this and still no joy but the mail alert tests are coming through fine and other event triggers (like new support sessions etc) are working so I know the SMTP details are correct. So weird. Any ideas what I can do to troubleshoot this? Is there a log I can look at? I tried changing the Filter to just Event.EventType = 'Connected' AND Session.Session.Type = 'Guest' amongst others (ignoring the need for a specific computer name, I just wanted SOMETHING to trigger) and still nothing. Well scrap that - it appears no triggers are working at all - even the alerts we used to get about new support sessions so I guess back to the drawing board on that, the filter is probably perfect, just gotta find out why nothing is being triggered.
|
|
|
|
|
|
Rank: Member Medals: Joined: 8/28/2012(UTC)
Posts: 34
Thanks: 7 times
Was thanked: 3 time(s) in 2 post(s)
|
Originally Posted by: vexation Originally Posted by: vexation Originally Posted by: vexation Originally Posted by: myers6mm This is the format I'm using, to watch for stolen computers.
Session.SessionType = 'Access' AND Event.EventType = 'Connected' AND Session.Name = 'Computer Name'
The Computer name above is the name you give it in ScreenConnect or in other words the name of the session. Just tried this and still no joy but the mail alert tests are coming through fine and other event triggers (like new support sessions etc) are working so I know the SMTP details are correct. So weird. Any ideas what I can do to troubleshoot this? Is there a log I can look at? I tried changing the Filter to just Event.EventType = 'Connected' AND Session.Session.Type = 'Guest' amongst others (ignoring the need for a specific computer name, I just wanted SOMETHING to trigger) and still nothing. Well scrap that - it appears no triggers are working at all - even the alerts we used to get about new support sessions so I guess back to the drawing board on that, the filter is probably perfect, just gotta find out why nothing is being triggered. Restarted the ScreenConnect Services on the Server and Triggers are working again. Frustrating as the up-time was only 27 days but is what it is. Thanks for the help with the filter, much appreciated.
|
|
|
|
|
|
Rank: Advanced Member Medals: Joined: 1/29/2014(UTC) Posts: 128  Location: Indianapolis, IN Thanks: 2 times
Was thanked: 21 time(s) in 21 post(s)
|
You can also flip it around. I use this as the trigger: Event.EventType = 'Connected' AND Session.HostConnectedCount = 0 AND Session.Notes LIKE '*ALERTME*' This way you don't have to create a new trigger for each machine, you just drop an ALERTME note on any of them you want to track. I even have a session group to monitor which machines are set to alert, using: Notes LIKE '*ALERTME*' Edited by user Thursday, December 13, 2018 2:00:23 PM(UTC)
| Reason: Not specified
|
1 user thanked SoCo_Systems for this useful post.
|
|
|
|
Rank: Member Medals: Joined: 8/28/2012(UTC)
Posts: 34
Thanks: 7 times
Was thanked: 3 time(s) in 2 post(s)
|
Originally Posted by: SoCo_Systems You can also flip it around. I use this as the trigger:
Event.EventType = 'Connected' AND Session.HostConnectedCount = 0 AND Session.Notes LIKE '*ALERTME*'
This way you don't have to create a new trigger for each machine, you just drop an ALERTME note on any of them you want to track. I even have a session group to monitor which machines are set to alert, using:
Notes LIKE '*ALERTME*' That's a good idea, thanks.
|
|
|
|
|
|
Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.
