Logon timing "Desktop" not working as expected

We have two classes of users, remote users that connect using a VPN and on-site users that are on the local network at one of our branch offices.

The remote users that use VPN have a challenge if we want to use Desktop Authority to push out programs at login. The challenge is when they log into their computer, they are not on network yet so we have two icons placed on these users desktop. 1-VPN Login launches the Cisco Anyconnect SSL VPN client where they can log in and get "on network". the second icon is called 2-Network Login which is a shortcut pointed to \\domain.com\netlogon\slogic.bat. This runs the script logic logon script and it provides them mapped drives, printers, some registry tweaks, etc...

However, we are seeing that an application launcher event for something like msiexec with the arguments populated with /i "\\domain.com\dfs\applications\program\program.msi" /quiet /qn /norestart with validation logic like if C:\Program Files (x86)\Program Name\programfile.exe does not exist - does not run - ever. It only runs on computers that are on the network all the time, like one in our 8 or so office locations.

So thinking its because the timing element "LOGON" will never be true because the VPN users are logged on with cached credentials prior to launching the VPN client... we also selected "DESKTOP" timing event, and in the help file it says "Check this box to execute an element when a client logs on to the computer. The element will execute after the logon process completes."

That sounds exactly like what we need.... the element SHOULD execute after the logon process completes, but it doesn't. The sltrace file just shows this element 79/79 of this case but not the command under it.

What is the best way to get things to run when the slogic.bat file is manually invoked after the machine has already been logged in? Drive mappings work fine. I'm seeing a lot of other things in the sltrace.htm log work fine like file, folder, registry permissions, registry tweaks, printers. What's with application launcher not working as expected?

The issue arises because VPN users log in with cached credentials before connecting to the network, preventing the "LOGON" or even "DESKTOP" timing events in Desktop Authority from triggering application installations like msiexec commands; while the script runs fine for mapped drives and registry edits when slogic.bat is manually executed post-VPN connection, the Application Launcher element still doesn't fire—likely because the system doesn’t re-evaluate conditions post-login. A workaround could be scheduling a task or using a post-login script that specifically checks network availability before running application logic, similar to how users manually trigger premium app features after access—like installing KineMaster Diamond Fully Unlocked APK only after network access is enabled to enjoy full features.