Deploy Image Fails <from the old forum>
altria May 20th 2009
Hello I am receiving deploy image failed, internal error 5, What does this mean.
Which log files pertain to deployments?
TIA,
Altria
============
DContreras Jun 1st 2009
KACE Employee
Generally, this error is because a change was made to the image. When this happens you need to format C as NTFS the next time you deploy the image to start from a clean slate. The log files in the PETEMP directory will tell you what files could not be deployed.
What version of KBOX are you on?
==============
altria Jun 2nd 2009
Well it seems the NTFS format solved the problem but after deployment completes I am unable to boot the machine. Two different errors, one pertaining to missing HAL.dll file which, when browsing the image I can see the file is there. Second, I get a unknown boot device error, suggesting some partition is not gettting recognized.
Thanks,
Altria
=========
altria Jun 2nd 2009 e
BTW, the version is 2.3.2161
============
DContreras Jun 3rd 2009
KACE Employee
What type of hardware are you capturing from/deploying the image to?
Also, what type of applications are being captured as a part of your image?
Feel free to email me so we can get to the bottom of this.
=============
altria Jun 12th 2009
Actually the deployment has gone through by addressing minor issues:
For those experiencing the problem now or in the future:
1. We had some deepfreeze issues which were resolved by removing the pers0.sys file on image> recaptured
2. We had an OEM partition that kept two partition instead of one, modified boot.ini on image to one and went through successfully
3. Finally, we had some networking issues which was resolved outside the scope of this problem but addressed loading KPE environment.
Thanks,
Altria
Hello I am receiving deploy image failed, internal error 5, What does this mean.
Which log files pertain to deployments?
TIA,
Altria
============
DContreras Jun 1st 2009
KACE Employee
Generally, this error is because a change was made to the image. When this happens you need to format C as NTFS the next time you deploy the image to start from a clean slate. The log files in the PETEMP directory will tell you what files could not be deployed.
What version of KBOX are you on?
==============
altria Jun 2nd 2009
Well it seems the NTFS format solved the problem but after deployment completes I am unable to boot the machine. Two different errors, one pertaining to missing HAL.dll file which, when browsing the image I can see the file is there. Second, I get a unknown boot device error, suggesting some partition is not gettting recognized.
Thanks,
Altria
=========
altria Jun 2nd 2009 e
BTW, the version is 2.3.2161
============
DContreras Jun 3rd 2009
KACE Employee
What type of hardware are you capturing from/deploying the image to?
Also, what type of applications are being captured as a part of your image?
Feel free to email me so we can get to the bottom of this.
=============
altria Jun 12th 2009
Actually the deployment has gone through by addressing minor issues:
For those experiencing the problem now or in the future:
1. We had some deepfreeze issues which were resolved by removing the pers0.sys file on image> recaptured
2. We had an OEM partition that kept two partition instead of one, modified boot.ini on image to one and went through successfully
3. Finally, we had some networking issues which was resolved outside the scope of this problem but addressed loading KPE environment.
Thanks,
Altria
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
arobinso
15 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.