/build/static/layout/Breadcrumb_cap_w.png
12/12/2018 617 views

Hi All,


I am having an error similar to what is written in > https://support.quest.com/kace-systems-deployment-appliance/kb/122254/invalid-root-in-registry-key-hklm-temp_system-setup-systemsetupinprogress-when-deploying-an-image . 

The unfortunate part in the article of https://support.quest.com/kb/121893/how-to-see-if-an-image-being-deployed-was-properly-sysprepped , I am using a Windows captured and not a K-Image.  How do I go about in checking this out ?


I am getting the error only on Win 10 v1803/09  but not problems in deploying a v1709.

2 Comments   [ + ] Show comments

Comments

  • This content is currently hidden from public view.
    Reason: Removed by member request For more information, visit our FAQ's.
  • What version of the k2 are you using. still 3.6 ??
    • it is 4.1.1148
  • Ensure your WinPE KBE was created from 1803 media.
    • as mentioned in my initial posting, even with 1803 I get the same error.

      Also note that i am not using K-Image

All Answers

1

This error happens when you captured the Image with an older KBE that had a lower ADK build, OR when an Image was not properly sysprepped:

error.jpg

Make sure your KBE was built with the ADK 1803 installed in your device where you build Kace Boot Environments .



Also make sure your 1803 image was captured with an 1803 KBE and not an 1709 KBE. If you captured the 1803 Image, with an older 1709 based KBE, it will cause issues.

That error is normally present when the KACE Engine has problems reading your captured Image Registry, Maybe an AntiVirus was added to the Image?, remember AVs must be post install tasks.


Answered 12/13/2018 by: Channeler
Red Belt

  • i am confused on what you mean about this
    • A KACE Boot Environment has three major components:

      -Drivers (network and storage, these are the basic drivers needed to perform imaging, this are known as WindowsPE drivers)

      -Windows Assessment and Deployment tools (ADK)

      -KACE software and scripts

      The Media manager grabs your drivers from \\yourKACEIP\drivers\kbe_windows_x64\

      It grabs your currently installed version of ADK from your Windows OS.

      and it adds KACE scripts and uploads all of them together as a KBE.

      So... the ADKs have many versions, one for each major Windows 10 build, see:

      https://www.systemcenterdudes.com/windows-10-adk-version-history/

      So if you built a KBE with Windows Assessment and Deployment Kits – Windows 10 version 10.1.16299 installed, that is a 1709 ADK. (check that website's table at the end)

      That means your KBE will be capable of dealing with 1709 and OLDER versions of Win10.

      But if you are trying to handle 1803 with a 1709 or 1703 or 1607 based KBE, you will run into strange issues.

      For example, if that KBE was built a year ago, that will not work, a year ago the ADK for 1803 was not available.

      You need to follow this guide to build a new KBE, making sure you have ADK 1803 or 1809 installed in your device:

      https://support.quest.com/kace-systems-deployment-appliance/kb/184391/how-to-create-a-kbe-for-windows-10

      1809 works fine for 1803, since they're all backwards compatible, but make sure your KACE SDA is on version 6.1, 6.0 and older are not compatible with 1809 ADKs.
      • thanks for the information and the explanation. I will check this with the KACE admin here