/build/static/layout/Breadcrumb_cap_w.png
07/18/2018 263 views
My Windows 10 deployments sit on the "getting ready" screen for a rather long period of time. The K2 engine appears to be processing tasks as several post install steps have successfully completed once it finally leaves the screen.  This issue appears to be benign as it's not actually holding the deployment itself up but the screen will eventually switch to a message that It's taking longer then expected.

I've been able to reduce the amount of time this screen is visible by having one of the first few post-install tasks initiate a reboot. This doesn't appear to have any adverse effect.

Is the K2 engine called via registry or is it called via setupcomplete.cmd the first time?
1 Comment   [ + ] Show comment

Comments

  • I could be wrong, but during ""Getting Ready" phase, the KACE BOX and the Device have ZERO communication.

    The KACE Appliance is waiting for Windows and your computer, to finish up the initial setup process, after that... the KACE tools to Install Post install tasks (if any), and then cleanup are actually launched with the Desktop (explorer.exe).

    Something inside the Image is doing it, are you deploying to a device with an SSD drive?


    Also make sure the Image was sysprepped and is NOT OEM:
    https://support.quest.com/kb/135252/using-oem-source-media-and-images
    • The KACE 2000 engine is definitely processing tasks during that phase. I know that MDT runs the "In-Place" Upgrades during this phase via setupcomplete.cmd, so I'm wondering if perhaps the K2 is running via setupcomplete.cmd the first time and then via a startup entry on subsequent reboots.

There are no answers at this time