We are testing the GlobalProtect Client (version 1.2.2-14) and are experiencing an issue. We use Windows automatic login for some custom deployment tasks, but are experiencing odd behavior and possible bug.
With the AutoAdminLogon, DefaultUsername, and DefaultPassword registry keys set, Windows will automatically log into the specified local account. Also, when creating the image in audit mode to run sysprep later, Windows automatically logs into Administrator on boot. This is the default behavior.
However, once the GlobalProtect client is installed, it seems that these built-in Windows features are ignored. The computer will not automatically log in. If an account was set to automatically log in using the registry keys and then the GlobalProtect client is installed and the computer is restarted, it will not automatically log in, but will have the password filled into the password box when clicking the user account picture that was set via registry keys.
We would like to find a way to fix this so we can include the client on our image. Any suggestions are appreciated.
Hope this document helps:
When GP is installed, we modify the gina dll which is why you are presented with a login. You can run the command listed in the document to restore the auto login.
Thank you for the response. We look forward to testing it tomorrow and your response is especially timely since our deadline is Friday. Are there any other similar issues to look out for on OS X? We have yet to test on OS X because of the issues we were having with Windows.
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!