- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
I have Windows 10 Desktop machine which runs in KIOSK mode, it automatically logs in to my dedicated AD KIOSK user through setting the AutoAdminLogon Registry keys.
We are using GlobalProtect for our user identity when inside of the corporate network combined with the GlobalProtect Windows login credential provider to allow SSO authentication.
When the PC signs in using the AutoAdminLogon registry, GlobalProtect can’t capture the login credentials due to Windows using its native credential provider.
I am aware as a work around I could make an identity policy or firewall policy which could be based on IP or AD polling, but I am wanting to try keep things simple and aligned.
Have I overlooked something? Has someone else managed to work a solution to this?
Or should I be using a different method to auto logon these machines which may work better with GlobalProtect?
Software Version 10.2.4-h4
GlobalProtect Agent 6.1.1
Thanks in advance for your time.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!