KACE Native Imaging Toolkit  ***This article is outdated and should no longer be used.  All users wanting to use Native Imaging should upgrade to k2000 version 3.5 or higher.  Article is left here for legacy purposes only.

Legacy deployment tools have their own proprietary image formats. Legacy tools usually require the installation of OS vendor servers from Microsoft or Apple to take advantage of the standard images which have obsoleted legacy proprietary formats. The Limited Release of the KACE Native Imaging Toolkit allows unfettered use of WIM and DMG images directly from the K2000 itself. This gives our customers the ability to pick the right tool for the job while retaining the K2000's easy-to-use centralized capture and decentralized deployment architecture. Customers who have time-sensitive deployments may wish to try the KACE Native Imaging Toolkit. Native images can be faster to deploy in some circumstances.

IT Ninja Post & Videos: http://www.itninja.com/blog/view/kace-native-imaging-toolkit-k2000-v-3-4-only

0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
The download here link is broken :(
Answered 02/27/2012 by: dchristian
Red Belt

Please log in to comment
0
Downloading now, i hope it will work the way i think it will work [:)]

did some testing, ive allready reduced the deployment time by 50 minutes (from more than 1H to 10m minutes).
Answered 02/27/2012 by: petrybosch
Senior Yellow Belt

Please log in to comment
0
im not so happy at the moment :(
When deploying a WIM it results in either a missing bootmgr or an 000000xe error...

Deploying regular images are also causing troubles:
- crashing on klonewin.exe
-missing postinstall scripts

any idea to get it working again ?
Answered 02/28/2012 by: petrybosch
Senior Yellow Belt

Please log in to comment
0
+
the mid-level tasks arent running at all. (same counts for the pre-level)

this is what the kbox is telling me:

Bootcode was successfully updated on all target Volumes/
cant open the archive containing the bootconfiguration
cant find the given file.
cant open the archive containing the bootconfiguration
cant find the given file.
cant open the archive containing the bootconfiguration
cant find the given file.
1 file copied
1 file copied
1 file copied
Executing call windows_7_two_partition_bcd_fix_3_1_.bat
cant open the archive containing the bootconfiguration
cant find the given file.
cant open the archive containing the bootconfiguration
cant find the given file.
cant open the archive containing the bootconfiguration
1 file copied
Error: system cant find the given registry key or value
Error: wrong parameter
Error: wrong parameter
Error: wrong parameter


image succesfully deployed


above information has been translated (my cmd is dutch)
This is happening with all of my images (and all of the KBE's)
Answered 02/28/2012 by: petrybosch
Senior Yellow Belt

Please log in to comment
0
i know it isnt one of the knit tasks, but they give the same error :)
Will send it to support

(i think the problems started after ive added the the 3.3 driver feed workaround .bin and tasks)
Answered 02/28/2012 by: petrybosch
Senior Yellow Belt

Please log in to comment
0
Corey the kace mail is down, cant contact support.
Problem still exists (even after creating new jobs).

You can contact me today on my office number
Answered 03/01/2012 by: petrybosch
Senior Yellow Belt

Please log in to comment
0
I think I'm misunderstanding how the Native Imaging Toolkit works. I had posted in another section of the forum, but haven't received a reply - and noticed that there were some other posts in there as well with no reply, so I'm thinking it isn't monitored all that much.

Here's what I've done with the KNIT:

1) I had a new Dell Latitude 6220. I set it up using a scripted install. All the drivers, etc., were instsalled as they should have been - no yellow marks in the Device Manager. I used the KNIT to capture an image of it. I then applied that image to a 6420. Worked fine. Also included a task to rename the computer (by looking up serial number in the dat file and giving it the designated name) and join the domain. Worked great - and was very fast deploying.

2) I set up a virtual machine in a similar way (using vmware). I did a scripted install, and then added some apps to it. I captured the image using the KNIT, and tried applying that to the 6220. It sort of worked, but not completely. All of the drivers didn't get installed - a bunch of yellow marks in the device manager. Also, sort of odd - the rename / join domain task only half worked. The computer did not get renamed appropriately, but it did join the domain.

So - does "Native" mean native to the physical hardware? And, is it only working on the 6420 and 6220 when I use a WIM created on the 6220 because the hardware / device drivers are so similar? (Although, the 6420 has a broadband card build in, the 6220 doesn't - but no yellow marks in device manager.)

I tried changing the deployment to have it include the driver feed, etc. and that didn't work either.

I probably should note that after I created the reference computer, I ran the sysprep tool on it that is available on the KACE website instead of using the sysprep that is built into the system. I didn't do anything with the WAIK. (I've seen that mentioned in some articles on creating a reference computer, but it wasn't mentioned in the KNIT documentation.)

I also tried capturing the image with the standard capture image that is built into KACE, but I get the same results when I deploy from that.

I'm not sure if I just don't understand what the KNIT is supposed to do - an image in general or one for a particular hardware model, or if I'm doing something wrong - perhaps not inserting drivers into the image - though I thought that KACE did that.

I'd really like to use this tool to deploy my new machines as it works so quickly, and I'd really like to be able to use a virtual machine as my reference computer so that I can revert to snapshots if need be and also not have to dedicate a piece of costly physical hardware to it.

Help!

Thanks in advance.
Answered 03/11/2012 by: gcoolong
Orange Belt

Please log in to comment
0
gcoolong,

The 'Native' part of the KNIT title is that it allows the native deployment of WIM files via the K2. Previously this was unsupported and only successful through a complicated process. Now, however, it is natively available as both a capture and deployment option on the K2 (high five to Corey and his boys). The WIM format is also in a way native to Windows as it is microsoft's image format for Vista/Win7.

If you're going to sysprep and capture a WIM you should keep in mind that while it will store drivers installed into the operating system and install them via plug n play detection during the setup process, you should try to leave your WIM as hardware agnostic as possible thus increasing the number of machines/models you can drop the image onto without issue. Ie, we use 1 image for over 14 hardware types.

This is why you're getting the device manager 'no driver' notifications. When you deploy your image you should post install your drivers through either individual tasks or via the driver feed.
Answered 03/11/2012 by: Roonerspism
Second Degree Brown Belt

Please log in to comment
0
Thanks for the reply. How do I leave it as hardware agnostic as possible?

I did try in one of my tests to use true driver feed. During the image process I saw the model of the computer on the screen and it said something about copying the driver feed, but I still had the same results.
Answered 03/12/2012 by: gcoolong
Orange Belt

Please log in to comment
0

Before capturing an native wim image do I need to sysprep de computer?
And how can i use the same wim image to deploy it to computers with different hardware ?

 

 

Answered 09/24/2012 by: diana_achim
Second Degree Blue Belt

  • Before you capture you should sysprep.
    You can also use '/generalise' when you sysprep which effectively stops any bsods appearing from pushing the image to multiple hardware configurations. You can then put drivers into the wim and/or use post installation tasks to install drivers. If you like have a look at the WAIK toolkit (for deploying and configuring wim images for win 7) or the ADK if you're using windows 8. These are both MS freebies and can be used in conjunction with your K2 deployment options for injecting drivers into the wim.
Please log in to comment
Answer this question or Comment on this question for clarity