There are many blogposts on how to configure Autologon for use when deploying kiosk devices for example. I needed to solve that in a kiosk scenario, more kiosk blogposts will be posted later. What are the challenges with Autologon then? To start with the OOBE phase clears out all Autologon registry values so they need to be configured after OSD is complete. Another challenge is that the username and password is saved in clear test in the registry.
Run a PowerShell script during OSD that does the following:
-Writes the username to a registry value so we can pick up later (in another blog post) -Copies Autologon.exe to C:\Windows\Temp -Creates an Autologon.cmd file in C:\Windows\Temp which we can run as a scheduled task. -Autologon.cmd includes username/password for the kiosk user with permissions set to System -Creates a schedule task that runs Autologon.cmd -Autologon.cmd runs Autologon.cmd then deletes Autologon.cmd and AutoLogon.exe and reboots.
I use Collection variables to set username and password to be used during OS deployment shown below.
The group in my Task Sequence looks like this where I have a conditon on the group that the Task Sequence variable “KioskDomain” must be present for it to execute.
The configure Autologon step looks like this and executes the PowerShell script from the package we created earlier. Where I pass the username / password as variables to the script. A follow up post on this will explain how I will use that in a Run script as well.
The computer will restart once after the OSD completes and then the schedule task will start and execute the script and the machine will reboot and logon automatically.
Then we have successfully configured autologon during OSD without the password in clear text in the registry. Next post will cover the script I use to configure Windows 10 to run KioskMode with Multiple apps and how to update it as well, stay tuned!
Privacy & Cookies Policy
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.