K2000 Preinstallation tasks fail on USB sticks only. PXE works fine.
Hi all,
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.
0 Comments
[ + ] Show comments
Answers (2)
Answer Summary:
Please log in to answer
Posted by:
TheAustinDave
7 years ago
Hi,
There are a couple of things I can think of, one of which is it sounds like you are just booting the system into the KBE with the USB Key? If so that just changes where the files are loaded from into the RamDisk created on the target system (tftp via network vs loaded from USB). Once its loaded the KBE and at the main KACE menu remove the USB key and select the deployment from the appliance.
Speeding up the deployment, if it is a WIM image can be changed to have it download and apply the image by using the KSWIM process. http://www.itninja.com/blog/view/kace-streaming-wim-toolkit-kswim
The other item that comes to mind is that the appliance could be updated as the issue you describe I believe is updated in the later release. The only caution on updating the appliance is that if there are Remote Sites created these will need to be re-created and data either re-sync to them or migrated from the 3.7 version to the 4.0 version. The reason is the RSA appliances are 32bit for the 3.7 version but are updated to be 64 bit for the 4.0+ versions.
TheAustinDave
Comments:
-
Unfortunately, I will not be able to update the k2. I had to fight tooth and nail to get access to it in the first place since the last guy left. The engineering manager is not very trusting.... I will look into the KSWIM feature. Thank you very much! - Irvine5000 7 years ago
-
To Clarify, I guess part of that un-trusting nature is due to the kace engineer leaving, He did EVERYTHING when it came to k1000/k2000. The engineering manager hasn't touched kace in years and years, and since it is such a vital piece of our infrastructure, being our imaging appliance, he does not want any major changes done to it. I can understand this viewpoint, but I personally am the type of person to update things. But I have no authority. - Irvine5000 7 years ago
Posted by:
Irvine5000
7 years ago
Top 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.