KACE Product Support Question

Trouble creating scripted install

05/24/2012 4715 views

I'm creating my first scripted install and I've run into problems:

We're running version K2100 3.4.54256 on our box.  It was updated last week from version 3.2.31608 to 3.3.36822, then to 3.3.52857 - then to the current version we're running.  I've seen posts regarding a patch for the driver feed, but I'm not sure if we need to install that as well or if that is already included in what we have.

I've also uploaded the KNIT, but I don't think that this will be involved in what I'm currently trying to do other than maybe a couple of the scripts that I used.

I've enabled the Driver Feed - and selected the model machines and OS that we will be using - these driver packages have been installed into the driver share.

My test machine is a Dell Latitude E6410.

What I've done so far ...

I've uploaded the OS to the KBOX 2000 and created the answer file using the wizard. The OS that I'm using is Windows 7 Professional 32-bit.

I've setup the details of the scripted install as follows:

Preinstallation Tasks -

Upload Hardware Inventory, Create 2 Partitions, Format 2 Partitions (these last 2 were obtained from the KNIT)

Postinstallation Tasks -

Windows 7 - Apply C Partition, Windows 7 - Apply D Partition, Win7 Automatic MBR


When I tested this on my E6410, it did complete, but wouldn't boot - got an error "Windows Failed to start ..." It referenced the file \windows\system32\winload.exe with a status of 0xc000000f - and info "The selected entry could not be loaded because the application is missing or corrupt."

Since trying this scripted install, I've found several posts regarding driver feed midlevel tasks - I've even downloaded the "driver feed tasks - 3.4", but I'm confused as to wether I am supposed to use them or not, and if I am supposed to use them where do I set them up.  How do I upload these to the K2000?  If anyone could give me details on this that would be extremely helpful.

As I said ... this is all brand new to me.  We're trying to implement Windows 7 in our environment.  The majority of our machines are Dell, but we do have some Lenovo (those I'll tackle later once I figure this piece out).




0 Comments   [ + ] Show comments


Community Chosen Answer


If doing a Windows 7 Scripted Install, you can't do the partitions the way you indicated, you have to do them in the unattend file if I remember correctly.

Is there a reason you want to partitions?  The small partition is usually there for bitlocker and even if using bitlocker, enabling it in windows will create the partition automatically.

In other words, I would simplify this by doing

create single partition
format c: as ntfs
Install Win7 MBR


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

Answered 05/24/2012 by: cserrins
Red Belt

All Answers

Answered 05/24/2012 by: dugullett
Red Belt

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ