This feature is only supported on Windows devices with desktop app version 4.10.0 or later.
Events can be used as hooks to scripts that automate parts of your workflow as an admin. This doc lays out how to identify Events, how to set up Event Hooks for post-connection scripts on Windows devices, and how to apply this feature to your own workflow.
Any time a user connects or disconnects from a Service Tunnel via CSE's desktop app, the desktop app automatically generates an Event in Windows devices' OS Event Log, published under the CSE service. For each type of Event, there is a specific Event ID.
When the CSE desktop app Service Tunnel changes state (i.e., a user connects or disconnects to Service Tunnel), it writes the following events:
| Event Published | |
|---|---|
| Log | Application |
| Source | CSEService |
| Event ID | 9001 |
| Event Published | |
|---|---|
| Log | Application |
| Source | CSEService |
| Event ID | 9002 |
CSE's desktop app (Windows version) writes a custom event to the Windows OS Event Log upon connection and disconnection to Service Tunnel. Admins can create a Scheduled Task to listen for an event and execute a script (or a sequence of scheduled tasks) once the event has been identified.
For instance, when the CSE service publishes an Event ID 9001, it means a user has connected to Service Tunnel, and the admin can schedule a sequence of tasks that run as a result of the user connecting to Service Tunnel.
Users may want to map their local drive to a remote corporate drive, to enable file sharing on their network. Admins can hook a script to a CSE-generated Event so that a user who connects to their Service Tunnel can then automatically connect to a remote corporate file server to retrieve files.
Admins may want to have their group access policies synced each time users connect to their Service Tunnel. Using an event hook, admins can automate a script that syncs their Active Directory group policies each time a user connects to their Service Tunnel on their device.