Installing VPN software for remote users
We can use PDQ Deploy for all updates with the exception of the VPN software agent. If we were to push it down when they are on the VPN, it would fail because the VPN can not be running when the installation occurs. I was planning on simply copying the EXE down to their local drive and trying to execute it locally but I'm not seeing how to point it to the local computer instead of a centralized network drive that they won't have access to if they are off the VPN.
-
I had the same issue with updating pulse. You can't update it while it's on VPN. First, I copied the files needed for update to c:\windows\adminarsenal along with a powerrshell scripts that run the update then I added a step to add Task schedule. The task scheduler looks for Even ID on pulse when it logs off. As soon as it logs off. The task scheduler starts a powershell scripts that runs the update, removes the task schedule task and reboots the laptop so the config gets loaded. So the task schedule takes over when it's not on vpn. It worked out like a champ. As long as they don't turn off the computer as soon as they log off vpn :). But you may want to send email to your end user community not to power off. But I am thinking of adding a step to prevent shutdown :) when I need to update vpn client.
Please sign in to leave a comment.
Comments
1 comment