We have a unique situation in our organisation where we've been forced to customize our Windows 7 image for deployment from our global partners starting as a ghost image.

They've all gone Altiris as their deployment tool which has the added benefit of being able to use wim images, however as we are a smaller business we've elected to use KACE for budget reasons.

With that said is their a best way to utilize K2000 in this environment?

In my test so far, I've just captured the image straight from the Ghost supplied by global and uploaded it right into k2000. With all our local customization being run as post install task. In doing so I've had to create post install task for drivers and what not which has become a bit messy and time consuming. We're also running dell desktops and laptops throughout the business but have not been able to leverage off the driver feed supplied in k2000 as we can not create a scripted install since we must use the global image supplied as our base point.
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
We have been able to deploy custom images via scripted install by capturing the image as a .wim using imagex and then replacing the default install.wim from OEM media with our custom one. This allows you install your customizations and deploy it as a scripted install becasue you've uploaded "OEM" media which really has your custom wim inside of it.

This would help alot with your driver issues as well because then you could simply upload the necessary drives to the KBOX driver store and they would install during the scripted install.

This method also vastly improves imaging time since you're not running all of your applications as post install tasks. Having most of the software already installed and deployed as flat files rather than installing them one by one as post installs really helps speed up the image process.
Answered 06/07/2011 by: matiasm
Orange Senior Belt

Please log in to comment
0
ORIGINAL: matiasm

We have been able to deploy custom images via scripted install by capturing the image as a .wim using imagex and then replacing the default install.wim from OEM media with our custom one. This allows you install your customizations and deploy it as a scripted install becasue you've uploaded "OEM" media which really has your custom wim inside of it.

This would help alot with your driver issues as well because then you could simply upload the necessary drives to the KBOX driver store and they would install during the scripted install.

This method also vastly improves imaging time since you're not running all of your applications as post install tasks. Having most of the software already installed and deployed as flat files rather than installing them one by one as post installs really helps speed up the image process.


It also limits the flexibility and customization that the K2000 was designed to offer. To each their own, but I prefer to let applications and drivers install as post-installation tasks instead of having 20 images taking up space on my K2.

I've tested both ways and there is about an additional 15 minutes doing the post install tasks with the size that our images would be with all of the applications we use. The larger the image, the longer it takes to deploy.
Answered 06/08/2011 by: dyehardfan
Second Degree Blue Belt

Please log in to comment
0
Cool idea Matiasm,

Can I ask how did you install your applications? Did you use MDT at all? Did you just bring up an instance of the OS, install the applications and sysprep it?
Answered 06/09/2011 by: AndrewPa
Orange Belt

Please log in to comment
Answer this question or Comment on this question for clarity

Share