KNIT was included with 3.5...Yes?
Just making sure.
0 Comments
[ + ] Show comments
Answers (2)
Answer Summary:
The KNIT has been integrated into the K2 per se. There is no longer a need for placeholder images, etc. Rather a radio button will allow you to choose kimage or native image when capturing. *NEVER APPLY THE BIN INCLUDED WITH THE KACE NATIVE IMAGING TOOLKIT (KNIT) TO A K2000 RUNNING 3.5 OR ABOVE*
The KNIT has been integrated into the K2 per se. There is no longer a need for placeholder images, etc. Rather a radio button will allow you to choose kimage or native image when capturing. *NEVER APPLY THE BIN INCLUDED WITH THE KACE NATIVE IMAGING TOOLKIT (KNIT) TO A K2000 RUNNING 3.5 OR ABOVE*
Please log in to answer
Posted by:
mpace
11 years ago
The KNIT has been integrated into the K2 per se. There is no longer a need for placeholder images, etc. Rather a radio button will allow you to choose kimage or native image when capturing.
*NEVER APPLY THE BIN INCLUDED WITH THE KACE NATIVE IMAGING TOOLKIT (KNIT) TO A K2000 RUNNING 3.5 OR ABOVE*
Comments:
-
Great, I assume it is going to sync the wims as well without those pesky extra steps? I am having to get a wim image together in a short amount of time and anytime saved is time spent elsewhere.... - gargone 11 years ago
-
Yep, syncing will be integrated as well. Note that you will have to re-capture existing WIM images with your 3.5 box as there is no way to import them directly. - mpace 11 years ago
-
So we just capture once, then copy the deployment and add our individual hardware specific tasks for each different model? - joe.pyrczak 11 years ago
-
Pretty much, config the machine the way you want it, making sure you have all drivers installed, sysprep it and capture it to the K2. Create your installation with any pre and/or post install tasks. Don't forget to use the driver feed as this will grab the drivers for your specific model from the feed on the K2. (don't forget to sync to RSA if you have one). I have been able to use it on 5 different models with no issues. - gargone 11 years ago
-
So we have to recreate our deployments each time we update the image? Previously, you just updated the one WIM and it was done, any chance of being able to do that? - joe.pyrczak 11 years ago
-
The WIM is integrated with the K2's manifest now so you'll have to drag the tasks into the deployment plan for each image captured. - mpace 11 years ago
-
OK, that means it will duplicate the deployment for each image, so 5GB per deployment and 5 deployments means 25 GB used on the K2000? - joe.pyrczak 11 years ago
-
If you want to keep deploying old revs of the image, then yes. There isn't any reason to keep them on the appliance if you won't be deploying older images. - mpace 11 years ago
-
oh, so duplicating the .WIM captured image deployment to add my model specific tasks will not increase the used space? - joe.pyrczak 11 years ago
-
Sorry, I misunderstood by what you meant by "update the image" in your previous comment. You are correct: duplicating five 5 GB WIM images on the K2000 will take up 25 GB of K2000 storage space. - mpace 11 years ago
-
ok, thanks - joe.pyrczak 11 years ago
