If all goes well, the Global Protect icon should have been removed and the WHfB PIN should be the default login method. Now we have to wait for a device to pick up the new policy. We have created a configuration profile, using the steps above. Assign this policy to your desired AzureAD device group.After some digging in the registry, I came across this GUID: But first I had to uncover the credential GUID of the Global Protect VPN client. :)Īfter some googling, I came across this blogpost from Peter van der Woude, with the explanation of how you can use the Exclude credential providers setting in the Settings Catalog in Intune. So this was annoying for the pilot users and myself, among others. In other words, entering your WHfB PIN (numeric or alphanumeric) could only be done if you had clicked on the "PIN" icon. So I clicked on "login options" and saw the Global Protect icon as default. Uh? I didn't have a problem with that, did I? Not even while logging in after Autopilot's userphase? 🤔
#Globalprotect vpn client password#
after a reboot of a test machine, my password was no longer accepted. So the package is created, uploaded to Intune and is installed during the Autopilot process. There is no clear agreement yet whether or not a VPN client should be installed, but until then, we need a VPN client. And that goes through the Palo Alto Global Protect VPN client. it's not that modern, because they still want all the traffic to go to the Internet through their network. With a client I am working on their modern workplace.
0 kommentar(er)
