Pre-VPN Drive Mapping batch script in Registry Key

mwill5392 — Thu, 23 Jan 2020 19:54:57 GMT

So I'm having an issue getting a batch script to run from inside the pre-vpn-connect registry key.

I followed this article exactly with a couple different variations and no matter what I do the batch script is not being triggered.

https://docs.paloaltonetworks.com/globalprotect/7-1/globalprotect-admin/set-up-the-globalprotect-infrastructure/deploy-agent-settings-transparently/deploy-agent-settings-to-windows-endpoints/deploy-scripts-using-the-windows-registry.html#idd19eebe3-48e5-48f1-8c14-72c5b22bfdf3

The batch script runs perfectly outside of the reg key. My gut tells me that the 'command' string Value data UNC path is not being seen correctly. The above mentioned article uses the example %userprofile%\pre_vpn_connect.bat c: test_user

My variation is %userprofile%\Documents\VPN_Mappings\pre_vpn_connect.bat c: test_user (For test_user I've used both the local login and the GlobalProtect user login user names, neither of which seems to work)

I've tried plenty of different variations to include just the file path alone. (%userprofile%\Documents\VPN_Mappings\pre_vpn_connect.bat & also C:\Users\(local user account)\Documents\VPN_Mappings\pre_vpn_connect.bat)

I'm at a loss as to why this reg key is not triggering the batch script on connection to the VPN...

Any help is greatly appreciated, thank you all.

topic Pre-VPN Drive Mapping batch script in Registry Key in Automation/API Discussions

Pre-VPN Drive Mapping batch script in Registry Key