K2000 3.6 has an issue - 'Set Engine Run Key' stage stalls build (Question/Statement)
I know I'm not the only one, but I have a big issue since upgrading the 3.6 and that issue is that once the build gets to 'Set Engine Run Key', it hangs there and does not progress the build until I logon. It does seem my experience is slightly different in that I can logon and the build will continue.
Pre-installation tasks run OK (disk is formatted, Get Computer Name etc all run). Mid-level tasks all run OK (Image is applied, drivers install). Post installation tasks DO NOT RUN due to being stuck on 'Set Engine Run Key' which shows as 'In Progress' for all eternity.
Logging onto the PC will continue the build, i.e. all post-installation tasks run and complete and the PC can then be used.
KACE has a an answer for this issue and that is that the network drivers are not installed. However this solution is wrong. I don't think KACE tested anything, they just said "typically this means the PC can't communicate with the K2000 and it's because network drivers aren't installed).
However, I can remotely view event logs, services, and whatever else I want so the network drivers are installed and working fine.
What I do believe is that KACE attempts to logon (but with what account I don't know) but I think it tries too soon or something, the PC doesn't logon and that KACE does not try to logon again. It will then just sit there until you logon and once logon is successful, it will carry on as if nothing happened.
Any guidance on what this might be is highly appreciated, but also this is just to highlight that this is an issue and KACE's answer is not acceptable.
Someone who's team now has to logon to all PC's being built to complete the imaging process.
Community Chosen Answer
I had the same issue and after some troubleshooting I assumed it was related to my image. Note I also tried to apply image without inject unattend.xml just to see if was related to that. Still nothing. So I applied the image letting Windows doing the setup. When I tried to re-run sysprep on it I had the error described here: http://support.microsoft.com/kb/929828 then I realized that something was broken with sysprep procedure. I rebuilt from scratch the image installing fresh Windows and running sysprep again. Now post install tasks work like a charm. I still don't know why the very same image worked with 3.5 but I would give a try. btw, this articles http://www.kace.com/uk/support/resources/kb/solutiondetail?sol=SOL118913 explain how you should change post install tasks to work with 3.6. It has nothing to do with issue described but maybe you need to take a look as well.