Hi,

Run into a weird issue which has me stumped so to say. Excuse the essay, but having it all I think could help paint a better picture of what I wish to achieve and where it fails. KBOX2000 appliance is running the latest version KBOX 2200 3.2.31608

In our company we use the HP Thin Client T5730. This unit runs XPe SP3, has 1GB of Flash and our corporate standard GP applied.

To initiate and prepare the image for mass deployment (which we have used succesfully in the past unig KACE to rebuild our 200 units in a department) we perform the Thinstate capture onto a USB thumbdrive. This process from my understanding does the HP Sysprep, converts the "HP image" then to a bootable medium onto the pendrive. Once completed, if the unit is powered up, the XPe enters a mini sysprep and voila, re-imaged client. The process however is hampered by the speed of the USB process, meaining it takes about 35 minutes to complete. Then you need to add it to the domain, rename etc etc. KACE here allowed us to rebuild 50 in 10 minutes, simultaneosly with postscript tasks joining and renaming as applicable from MAC address.

Once the Thinstate capture completes, the unit powers off. Now wanting to capture the image, I boot into PXE, Select Capture image. Under drives to capture I select:
C:\ Type: NTFS Size: 0.95GB Free: 0.11GB *** makes sense as this only has 1GB flash drive
Select Force continue on errors and Start.

Capture commences, once completed the log section says it all, the total image size is 1.2GB. The "drive" is only 1GB, and as indicated above the drive capture shows 0.95 GB total size for C:

Where is this mysterious 250MB coming from preventing me from deploying the image to another identical Thin Client. The error reads that there is not enough disk space, duh.

Any pointers or tips would be appreciated, I am exhausted.

Thanks
Steve
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
This is a known issue with deployments that have multiple hard links. Our next release should address this issue.

Please email me privately if you'd like to be the beta list.
Answered 08/05/2010 by: jkatkace
Purple Belt

Please log in to comment
0
ORIGINAL: jkatkace

This is a known issue with deployments that have multiple hard links.  Our next release should address this issue.

Please email me privately if you'd like to be the beta list.



Hi,

Thanks for taking the time to reply. Has this issue krept up in the release we are running now as we did not have this problem with any images for the Thin Clients - we have been using them for 2 years now without any problems in KACE.

Regards.
Steve
Answered 08/06/2010 by: SteveKruger
Senior Yellow Belt

Please log in to comment
0
Hi,

We have now recently upgraded to version 3.3

Are you aware if the issue has been resolved in the latest update?

Thanks
Steve
Answered 01/21/2011 by: SteveKruger
Senior Yellow Belt

Please log in to comment
0
This should be addressed in 3.3; I'd suggest trying a deployment again and advising us of your findings. Sorry I don't have a certain answer, but that is specifically something 3.3 is designed to resolve.
Answered 01/21/2011 by: cblake
Red Belt

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

Share