What happens during a Image Deployment from Flash Drive?
So I have been testing the USB Flash Drive System Image deployment method for geting an image on a system. I have a 10GB image and it takes a little over an hour to deploy. I am interested in decreasing this time as much as possible. To that end I was hoping somebody could hash out what steps are taken during the USB Image deployment.
Here is what I see:
-Boot to flash drive.
-KBE starts up, sees that there is an image to deploy ("Checking if this is a UFD boot and an image is prepped for deployment")
-KACE\deploy.bat starts. Runs preinstallation tasks.
-KLONED.EXE starts (whats this?) listens on a port, creates hashstore at E:\KACE\hashstore
-KLONED waits for a connection, and then about a minute later receives one from the local machine.
At this point there isn't any more dialog for about 10 minutes. The system just seems to be waiting, or doing something in the background. What is going on at this point?
Here is what I see:
-Boot to flash drive.
-KBE starts up, sees that there is an image to deploy ("Checking if this is a UFD boot and an image is prepped for deployment")
-KACE\deploy.bat starts. Runs preinstallation tasks.
-KLONED.EXE starts (whats this?) listens on a port, creates hashstore at E:\KACE\hashstore
-KLONED waits for a connection, and then about a minute later receives one from the local machine.
At this point there isn't any more dialog for about 10 minutes. The system just seems to be waiting, or doing something in the background. What is going on at this point?
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
muebel
13 years ago
I deployed a system image to system via flash drive, and when the deployment finished it rebooted and then complained that winload.exe was either missing or corrupt. I booted up to KBE and checked the directory and found that winload.exe was there, but it was 0 bytes in size. I found that many many files were 0 bytes in size.
Has anybody seen this sort of behavior? This was an install to a D520. I am trying a D820 now. I have gotten both of these systems to work with a different flash drive, and different system image.
Has anybody seen this sort of behavior? This was an install to a D520. I am trying a D820 now. I have gotten both of these systems to work with a different flash drive, and different system image.
Posted by:
muebel
13 years ago
So I am paying very close attention to the hashstore at each step of the process, and I think my issue might have been using the builtin file extractor that comes with windows 7.
I tried 7zip and it extracted all the files without any unexpected empties.
Am now using install script to load image on flash drive (xcopy)
I tried 7zip and it extracted all the files without any unexpected empties.
Am now using install script to load image on flash drive (xcopy)
Posted by:
muebel
13 years ago
I edited deploy.bat by taking out @echo off and the safeguard "are you sure you want to format?" prompt. (I need to draw skull and crossbones on the UFDs.) I can see the script seems to sit at "kloneconsole.exe -d C: -i <image_id> -h 127.0.0.1 -l E:\KACE\<image_id>.log" for that 10ish minute gap before it starts to actually Deploy the items.
Is there anything that can be done to make whatever kloneconsole.exe is doing go faster?
Is there anything that can be done to make whatever kloneconsole.exe is doing go faster?
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.