I'm deplying a Windows 7 x64 WIM sysprepped image now, and I'm getting stuck on the "set engine run key" task, even before any post install tasks take place.

I read this article:

https://www.kace.com/support/resources/kb/solutiondetail?sol=SOL118934

However, it's the same image I've been using for the past year for our x64 machines. It has the NIC drivers already installed, and the driver feed already checked. 

Any ideas?

9 Comments   [ + ] Show Comments

Comments

  • Did we get a fix for this. I know the Nic drivers are installed because I can connect with VNC until it gets to that point, than I can't.
  • Nope. I'm having to re-create my images. Support can't figure it out either. If I would've known 3.6 would screw up every single image I have, I would've never have upgraded. Bunch of post-install tasks won't even work.
  • Yikes, I'm having the same issue and I really don't want to re-create my images. In your new images are you doing anything differently? Is there something you have to do different in your sysprep config? Do you install your network drivers in your image or let the driver feed take care of it?
  • Nope - same exact WIM image as before - just have to re-sysprep, re-capture, drag over all post install tasks again, and then duplicate for all 20+ images that use this WIM. It's a pain in the ass, but the only option at this time since support can't seem to figure out the issue either. The knowledge base article says its the NIC driver, but the NIC driver is installed on the machine way before I even captured the initial image - so it's not that. There must be a compatibility issue somewhere.

    I'm running an Optiplex 990 Windows 7 x64 - for your reference.
  • Great. so no fix for this issue. I have recreated the images several times. I get no where.
  • I had to re-create a base image from scratch and it worked. Not sure what to tell you - other than I hope you don't need to image anything any time soon. I've learned my lesson with KACE updates. 5.5 completely borked a lot of my Smart Labels, and the only thing I've been told for the past few months is that I need to wait until 6.0. Now with the K2 3.6 update, I'm unable to image. I'm in a K-12 environment with over 5,000 machines and have 20 locations setup with RSA's. I get a headache every time I think of updating the RSA's now, let alone get my main K2 working. Unfortunately, KACE isn't the only thing that I run in my position - I have to do helpdesk tickets for our schools as well, so finding the time to fix end user problems and spending every single day doing test images is getting tiresome.

    Good luck. Once tech support resolves my issues with 3.6 right now, I'm not upgrading again.
  • I also have this issue on machines that built perfectly fine before 3.6. I've found that the build process will continue if you logon to the PC but this is fairly ridiculous. Drivers for the NIC are installed. I really don't know how to overcome this?

    Another one of my post install tasks that worked prior to 3.6 also no longer works but that's another story.
    • Even if I logged into the machine, post installs wouldn't continue. No post install tasks worked since it was stuck on the set engine run key error.

      I'm also having issues with a few of my post install tasks not working correctly. It looks like it may have corrupted the files, so I'm still testing this with Tier 3 support.
  • Previous comments say they have re-imaged but I'm not willing to do that. A lot of work goes into my Windows install before it is captured. We have paid KACE for support, perhaps they should pay us for the many hours this will apparently take to fix.
  • I had been experiencing the same issue after the upgrade from 3.5 to 3.6.

    After logging a ticket with Dell and doing everything that they asked, deleting and re-adding nic drivers, checking for and IP addresses on start up, attempting to run various post-install tasks etc, I still could not get it to go past the Set Engine Run Key task.

    Stumbling across this the below article this morning, it states way down the bottom that the run once converter is no longer needed in 3.6 because of the new task scheduler. I still had the "run one converter" executing at the Mid-level task from when I upgraded from 3.5. Didn't even know it needed to be removed! I have since deleted it and it now works like a charm! Hopefully Dell can update their knowledge base to reflect this.

    http://web01.itninja.com/blog/view/k2000-best-practices

    Hope this helps others in the future.

    Cheers.

    Russ
Please log in to comment

Community Chosen Answer

2

I had been experiencing the same issue after the upgrade from 3.5 to 3.6.

After logging a ticket with Dell and doing everything that they asked, deleting and re-adding nic drivers, checking for and IP addresses on start up, attempting to run various post-install tasks etc, I still could not get it to go past the Set Engine Run Key task.

Stumbling across this the below article this morning, it states way down the bottom that the run once converter is no longer needed in 3.6 because of the new task scheduler. I still had the "run one converter" executing at the Mid-level task from when I upgraded from 3.5. Didn't even know it needed to be removed! I have since deleted it and it now works like a charm! Hopefully Dell can update their knowledge base to reflect this.

http://web01.itninja.com/blog/view/k2000-best-practices

Hope this helps others in the future.

Cheers.

Russ

Answered 04/01/2014 by: table_top_russ
White Belt

  • The images I've been testing has had these removed. This could be a possible solution for some, but not for all. Didn't fix anything in my instance. Looks like 3.6 really screwed up a lot of people's images. Makes my push to go SCCM even easier for the boss to consider.
    • have look here: http://www.itninja.com/question/k2000-3-6-has-an-issue-set-engine-run-key-stage-stalls-build-question-statement
  • This fixed my issue with my scripted installation. Thank you so much for saving me from a huge headache.
    I haven't tried deploying an image I created with 3.5 yet.
Please log in to comment

Answers

0

That is the first Windows PO task, automatically set by the K2.  Maybe put a pause type task as your first PO so that you can pull up a command prompt and see if you have an IP address, or check device manager to make sure the NIC is installed at that point.

For the task, create a Windows Batch Task, enter in:

start cmd.exe
pause

That will open a new command  prompt window and pause for you.  You could also just type 'Exit 1' which will give you the error page and the ability to open a command prompt.

 

Corey
Lead T3 Enterprise Solutions Consultant, K2000

Answered 02/26/2014 by: cserrins
Red Belt

  • It images fine, then reboots and goes directly into Windows (after sysprep). Progress on the WebUI shows it being stuck there. I have a valid IP, and the NIC shows being installed without a problem.
    • but does it have an IP and installed NIC driver immediately? Sometimes it gets installed later in the process.
      • Yes, I believe the NIC drivers were installed prior to capturing the WIM. It's never been an issue prior to 3.6, as we've deployed almost 2,000 machines with this image.
      • Should I open a ticket for this? We have some machines that aren't functional in our schools and need to be reimaged, but we're unable to now.

        (disabled driver feed to see if that was related somehow - still gets stuck at that point. NIC driver is installed, and working fine. Only thing that happens between imaging and Windows is the sysprep setup of drivers/devices).
Please log in to comment
Answer this question or Comment on this question for clarity