Rename and Join domain in K2000 3.6 without manual logon
Hey guys, I've been running the script I found on the support site for years that would auto logon after imaging, run a WSName, reboot and auto logon again to join my domain. I had set the auto logon in sysprep. Now on 3.6 my guys need to logon to the computer and it will kick off the script, then reboot and they have to log back on to finish the job.
Is there a better way to accomplish this in 3.6? The new task engine looks like I may be able to do it a better way, if someone out there has a little direction I would greatly appreciate it!
1 Comment
[ + ] Show comment
-
When we updated to 3.6 there was an extra reboot in the process and it would require a log-in before the post tasks kicked off. Adding 1 more auto logon to the unattend.xml file in all of our images resolved the problem for us. Shouldn't need to turn it off if you find the correct # of log-ins for your images/environment. - SDNBTP 10 years ago
Answers (1)
Please log in to answer
Posted by:
nheyne
10 years ago
This might be related: http://www.itninja.com/question/windows-8-1-and-k2000-scripted-install-cannot-rename-system-with-service-tag
Sounds like this might be a common issue.
Comments:
-
I checked that one out, mine is working but I have to login 2x manually. We have 6000+ machines and image a lot, I want the guys in the field to start an image and basically walk away knowing it will be done in one shot (most the time). I'm thinking in the new task engine I need to do a task for each process and have it reboot by clicking the reboot check instead of my bat w/ the old style scripts. - ddevore 10 years ago
