About bernardo.hernandez

Yup. The only way to make it work for me is to uninstall everything (certificate and Global Protect client v4.0) and then reinstall the certificate and install Global Protect version 3.1.1 then it connects on the first attempt BUT -and this is where it turns stranger than Stranger Things - it will only successfully connect that one time, if you disconnect and then try to reconnect a second time it won't work and you'll have to uninstall the certificate and reinstall it everytime you want to connect.   Definitely a thing of beauty.   Greetings from the upside down!     ... View more

Thanks for your reply @Raido_Rattameister. Everthing seems OK with the portal. Macs work just fine as well as iOS and Android devices. I get no issues with my PC running Windows 10 but some of my peers can't connect with the same version of Windows. It's a strange one.    So far the only workaround we have is downgrading to version 3.1.1     ... View more

As @vsys_remo mentioned, you should run it on any server or machine that has access to the API of the firewall where you have configured Global Protect. A few considerations before you can run the script:   You are going to need your API key from the firewall. You can get it by replacing the HOSTNAME, USERNAME and PASSWORD fields with your particular information and then copy-paste it in your browser like this: https://HOSTNAME/api/?type=keygen&user=USERNAME&password=PASSWORD If everything goes as planned you should get a response like this:   <response status="success"> <result> <key>gJlQWE56987nBxIqyfa62sZeRtYuIo2BgzEA9UOnlZBhU</key> </result> </response> This will be the value of the $apikey variable on the script.    2.- You might need to change the powershell execution policy on your client machine. In my case it was set to "Restricted" which is the default.    To find out what is your current execution policy run the following command: Get-ExecutionPolicy To change it, run: Set-ExecutionPolicy RemoteSigned -Scope CurrentUser This will change the execution policy for the curent user on the client machine and will allow you to run the script.   Good luck!               ... View more

Sorry, I’m not sure what do you mean. ... View more

Absolutely!   It's the hard knock life for us,  sysadmins!     Thanks again! ... View more

8.0.9 ... View more

Nice!    I can see the user and computer names now.    It doesn't seem to disconnect them tho, but at least I can now know who has multiple sessions and disconnect them manually.     Thanks again!   ... View more

Awesome!    Looking forward to it.    Thank you for sharing and taking the time to walk me thru it all. I appreciate it.   Regards ... View more

Cool!   It does run. Now, I'm not sure what output should I expect.    I get:       ... View more

All right. I'm getting there...    Just one more hiccup   ... View more

Yes.      Something like this:    $firewall = 192.168.0.1 $gpgateway =GP_test   ... View more

Great. I've got my API key.    I had to change the execution policy for the currentuser on my machine so that I could run the script however I get the following errors. One per every one of the first $variables on the script, meaning $apikey, and $firewall.   "The term $variable is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name , or if a path was included, verify that the path is correct and try again."   😞 ... View more

Thanks Remo   I'm having a lot of trouble trying to get my API key. I've tried sending a GET request to the FW per this article https://www.paloaltonetworks.com/documentation/80/pan-os/xml-api/get-started-with-the-pan-os-xml-api/get-your-api-key using powershell, however I've had no luck yet.    Any pointers?       ... View more