Setup autologon after OSD
We have several laptops that are given out as "loaners" and are not joined to our domain. As such, during the OSD process, we create a local user on the computer, and then would like to set this up to autologon. We had this working when just using MDT by using the HTA that waits for the MDT processes to exit, then sets the appropriate registry keys. I am wondering how this would translate to SCCM. It's my understanding that I would not be able to have anything pop up (like the HTA) due to the way the SCCM imaging process works (not logging into the desktop, but doing it all before the login screen even). To add to that, I'm not sure which processes I would even be watching for to know when the OSD session completes. Does anyone have any experience with this, or could point me in the right direction? I can't be the first person in the world wanting to do this!
November 10th, 2010 11:23am

how about the registry method described here My step by step SCCM Guides I'm on Twitter > ncbrady
Free Windows Admin Tool Kit Click here and download it now
November 10th, 2010 4:35pm

I tried that just today as well, I put that task as the final task in my sequence. The registry entries get imported, but it never logged in automatically. I logged in manually myself, and none of the registry keys were there any longer (except DisableCAD, which had been changed from 1 to 0). My assumption is that SCCM is somehow cleaning out these AutoLogon registry keys as part of it's cleanup. This assumption is also played out by a little testing I did, as the last steps of my task sequence, I did the following: - using a REG command line, dump the Winlogon key (no keys there yet, as expected) - using a VBS, create the autologon registry keys - using a REG command line, dump the Winlogon key (my registry keys are still there) - reboot the computer - using a REG command line, dump the Winlogon key (my registry keys are still there) Using those steps, the computer as well never automatically logs in. When I manually logon and check the registry, the keys are not there.
November 10th, 2010 5:59pm

It's due to SCCM running the VBS in a 32-bit process. Microsoft is redirecting certain registry entries based on if it's 32-bit or 64-bit, much like the Program Files redirection. However, the auto-logon registry keys are *not* supposed to be redirected, so something is going seriously wrong. However, due to a solution from a member on another forum, I now have a working work-around. Read more here: http://www.windows-noob.com/forums/index.php?/topic/2804-setting-up-autologin-at-the-end-of-sccm-osd Just posting this here in case anyone else is looking for a solution.
Free Windows Admin Tool Kit Click here and download it now
November 24th, 2010 1:33pm

Hello Sabkor, do you have a full working .vbs for x86 windows 7 machines? Thx!
August 24th, 2012 5:16am

Somebody who has a full script for x86-machines?
Free Windows Admin Tool Kit Click here and download it now
August 25th, 2012 3:45am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics