We upgraded our kbox 2000 to 3.4, and I can not find any instructions on how to correctly recreate the two paritions windows 7 creates.

there is the 100MB system partiton and the rest of the disc on the second partition (where windows is installed)

When I run the KBE it seems to be assigning C: and D: drive letters to the partitions, even though the system partiton should not have a drive letter, and so when I capture images KACE wants to restore to the wrong partition.

The knowledge base article I can find says it's for 3.3 and below, so I'm not sure which parts to use and not to use.

Anyone have an exact list of steps to capture and create a deployment for Win 7 on the 3.4 system?



0 Comments   [ + ] Show Comments


Please log in to comment

Community Chosen Answer


Best practice has been to only have a single partition when creating an image. Having more then one partition tends to throw things off and cause problems.

Answered 09/07/2012 by: Ben M
Ninth Degree Black Belt

  • Windows creates a system partition that is not visible to the user. As mentioned, it's ~100mb and shows when you look at Disk Management, but doesn't show in Windows Explorer. Basically, it's not mounted.
    However, the K2K shows two partitions (C:\ and D:\) when imaging the system.
    Capturing both 'partitions' and attempting to deploy them to another system fails as there is no D:\ partition to deploy to.
Please log in to comment



Support recommends deploying a single partition scripted install and then building your golden master from that machine.

Lead L3 Enterprise Solutions Engineer, K2000
If my response was helpful, please rate it!

Answered 09/20/2012 by: cserrins
Red Belt

  • In my case, the system was built using a OEM Win7Pro disk. Single partition. Only the System Reserved 100mb partition is created by Windows. Cannot be removed.
    Cannot capture what the K2K thinks is D:\ and deploy that to C:\ on a new system.
  • http://www.terabyteunlimited.com/kb/article.php?id=409
    I found this article that removes the System Partition if you forget to do it at the creation of the image like I did :-)
Please log in to comment

Hi, Bretts.

I have a 3.4 version and I had to do all steps shown on that article that you've mentioned and it worked fine.



Answered 10/03/2012 by: phabran
White Belt

  • Or you can remove it this way afterwards: it caued me no issues.
Please log in to comment
Answer this question or Comment on this question for clarity
Five Easy Steps to Smarter Systems Imaging
With traditional methods for systems imaging, each image captures a particular hardware and software configuration at a specific moment in time—static, unchanging, unmanageable.