I'm working on setting up a Windows 10 deploy with K2000. I have a scripted installation, with a Kace-created unattend.xml (created with the guide in K2000) and a clean Windows 10 Enterprise as source media.

Everything seemingly works fine until the post installation tasks are supposed to be installed.

After Kace is done copying drivers it reboots into Windows. (I'm guessing this is either at the Update Configuration For OS Tasks step or Set Engine Run Key step) However, the task engine doesn't launch and no post installation task is run.

I have also tested sysprepping an image and capturing it with K2000. I get the same result here, it installs Windows fine, but skips the PO-tasks.

I'm clueless as what the next step would be.

EDIT: I solved the problem, see my comment below for full answer. Changing the name of the admin account back to admin and disabling automatic Windows updates solved it for me.
4 Comments   [ + ] Show Comments


  • After the device fails to run the post installation tasks can you verify that the network works correctly on that device? (it assigned, able to browse back to the K2000....etc etc)
    Kind regards,
    Marco - StockTrader
    • After it reboots into Windows from KBE, it's been assigned an IP, it's able to ping K2000 and it can browse to the K2000 network share.
      • Ok. What version ok K2000 are you using? 3.7.120151 ?
        Is this happening for every Windows 10 Scripted install / Image deployment?
        If you create a new one from scratch do you have the same issue?
        Marco - StockTrader
      • Can't reply to your comment, so I'm replying here instead.

        I already tried creating several new ones, which didn't work. I also created two more after I read your comment, but to no avail.

        However, I managed to solve the problem in another way! I named the admin account admin and left the Turn on automatic Windows Update box unticked. Now the task engine runs fine!
  • We also ran into this problem. On our system kace is looking for the system drivers in a windows 8 driver folder not a windows 10 driver folder. Once we created the windows 8 driver folder our images work.
    • Thanks for the suggestion, but I monitored the installation several times, and the Win 10 drivers were always installed. (All 92 of them for this particular machine)
  • Is the computer set to auto login as an administrator? The KACE engine runs in the user context so you need to set an auto login for it to run the post-install tasks.
    • Auto login as admin was set up, however, renaming the admin account back to "admin" actually solved the problem, as I noted in my commet above.
  • I found that I couldn't Join the Domain in the Unattended.xml file and still have my PostInstall Tasks run. So I used the Kace VBS script to join the domain as a task after all of the software was installed.
    • What autologon count did you set in your unattend.xml?
      • I use 3 in Windows 10 and 2 for other OSes
    • Hmm, OK. If you're still interested in troubleshooting why the machine isn't joining the domain with the settings specified in unattend.xml, have a look at the log files in C:\Windows\Panther and C:\Windows\Panther\UnattendGC. (Specifically setupact and setuperr)
      • The machine join's just fine using that method. However, my Post install tasks do not run correctly when joining AD in that way. The Scripted AD join is working fine as the last post install task.

        I do not have a problem, I was just sharing my workaround on this issue to help someone else.
    • Got it! If it ain't broke... :)
Please log in to comment

There are no answers at this time


Answer this question or Comment on this question for clarity