I created a simple batch file on the local desktop, echo hello pause, and that doesnt work to prove to the palo rep is not the complexity that is causing it.
Not OP, but it shouldn’t be complicated to make it work. The tricky parts can be making sure that the command path is correct and if it contains spaces, to use quotation marks, and to run it under the correct context.
Here’s our registry entries for both pre-connect and post-connect. We use pre-connect to map drives, so this is run in the user context - the script itself starts with a ping command that waits until a connection to our file server is established. That’s because the post-connect does other things that absolutely need admin privileges and the connection to already be established. So both scripts need an active GP connection, but one of them is forced to use that ping workaround.
The entries look “normal” in the registry, no double backslashes or anything. Basically like this:
“C:\Program Files\Palo Alto Networks\post_vpn_connect.bat”