Cuken Posted March 28, 2013 Report post Posted March 28, 2013 Hello, We are currently piloting SCCM 2012 to replace our Altiris solution for our Company. We're working through several things and are getting stuck on seemingly simple tasks. Currently we are trying to get an autologin script to work for some of our customer facing machines. In altiris, we can deploy the vbs script and it works just fine. We've created a package with the same vbs script using the command line of autologn.vbs as the argument. The issue we're seeing is that many of the registry keys are getting set correctly, but the key AutoAdminLogin is never setting to anything other than 0. If we run the script manually on the machine it sets the values correctly and works. I've tried including this in the Task Sequence during imaging, as a package outside of the image process, and finally by making the package available and running it while logged in as an admin user from the SCCM client on the desired machine. None of these are allowing the key to set properly. Is there any insight into why this is happening? I've searched extensively on multiple forums and the closest solution I've found is a 64bit registry problem. We are only using 32bit machines. Any help would be greatly appreciated. Thanks, Cuken Quote Share this post Link to post Share on other sites More sharing options...
Rocket Man Posted March 28, 2013 Report post Posted March 28, 2013 Have you tried putting cscript.exe "autologin.vbs" as the command line parameter? Also you could export the desired registry settings from a machine that has the correct settings and deploy the exported registry key instead of using a vbscript(not unless of course the script does other tasks apart from editing the registry) Quote Share this post Link to post Share on other sites More sharing options...
Cuken Posted March 28, 2013 Report post Posted March 28, 2013 I actually just tried cscript.exe, still not working. I'm attempting to do a simple import via command prompt right now. I'll check back, thanks for the quick response! Quote Share this post Link to post Share on other sites More sharing options...
Cuken Posted March 28, 2013 Report post Posted March 28, 2013 Still no luck! The amount of ways to import a registry is staggering, and its still not working I just tried creating a task sequence referencing the package and that still did not work.Its setting all registry values but one, I'm not sure why it keeps failing on just that one key. Any other ideas? EDIT: Is it possible it has something to do with how we syspreped our image? Something in the unattend.xml? Quote Share this post Link to post Share on other sites More sharing options...
