K2000 Preinstallation tasks fail on USB sticks only. PXE works fine.
05/09/2017 1228 views
Can someone help me out with this. A bit of background, The kace engineer left and i was just given the keys and asked to make a windows 10 1703 x64 Enterprise image. We are running K2000 version 3.7.120345 The good news is I got this image working just fine on pxe, but pxe takes far too long as it has to copy the image locally and THEN apply it. We have used usb images in the past. The engineer told me that he had to modify multiple files on the flash drive relating to the UFDPATH or something along those lines, and he does not remember them off the top of his head, otherwise he would tell me. I have never touched kace before last week. So I am quite the beginner.
The error I am getting as soon as the preinstalltion tasks start is "Y:\hta\getkuid.vbs the system cannot find the drive specified" If i proceed, it will wipe my flash drive. I am VERY VERY new to kace so I have no idea what files I would need to modify to fix this.
Also, The former engineer mentioned something about instead of using USB for deployment there is a way to have the k2 via pxe directly apply the image to the computer, instead of copying it locally to the computer first, and THEN deploying\applying it.
I would be happy with either solution as we like usb for super fast imaging with ssds, or the latter so we don't have to maintain and update usb sticks every time an image needs to be updated. We are using WIM system images, and not scripted installations in this environment.
ANY help would be GREATLY appreciated.
Answer Chosen by the Author
Please log in to answer
I just want to update this in case anyone else has this issue. I was able to resolve the USB imaging problem by going into the TASKS.XML file in the kace engine folder, and changing the path on every line in the PRE-install tasks that said %UFDPATH% to E:\ The mid tasks said %systemdrive% which I left alone.
I also had to change EVERY line on the post install tasks from %UFDPATH% to C:\
USB imaging is now working! I hope this helps someone else out.
Answered 05/13/2017 by: Irvine5000