Error -99 on sysprep'd image!
I'm not having a lot of luck recently...
I've got a sysprep'd image job which distributes a disk image to various clients and it's been working fine on Dell G520, G620 & the 755 hardware. The job delivers a manually sysprep'd image, and the tasks that follow deliver the targeted PnP drivers folder and a revised sysprep.inf
Now enter my HP DC7800. Delivering the disk image fails right at the very end with "Error -99". A look in the KB shows that this error is associated only when a cfg file is required. But this is a sysprep image, so the checkbox to do a post configuration is not checked.
The automation OS is Windows PE2.1, and attempts at using DOS and Linux automation also fail, but with fatal errors at the last second of imaging. The same job works great on the Dells and VMs.
Tried logging this with Altiris Support, but the answer times on the phones are not to great just now. I'll try again with support tomorrow, but hoping someone out there might have a clue on this one?
Kind Regards,
Ian./
P.S. Don't think it's a mass-storage controller issue as the imaging does appear to succeed -the failure is right at the last moment -just when you think its all worked.
I can also script XP onto the DC7800 no problem.
Comments
Ian,
Just a thought...have you tried using a network boot and running rdeploy to manually download the image?
Stu
ITS Partners
LinkedIn
Hi Stu,
Thanks for replying. From the network boot, Rdeploy gives an error that the file path is invalid. The image is split across two files,
sysprep.img -> 2GB
sysprep.002 -> 1.5GB
But imaging reaches the last second before this error is flagged, so the its already read the most of the sysprep.002 file and deployed it.
It looks like I'll have to start a packet trace to see what's really up...
Kind Regards,
Ian./
Ian Atkin, Senior Developer for the ICT Support Team, Oxford University, UK
Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads&
Well the results of the packet trace were not very exciting. No SMB errors, so physical access to the data wasn't the issue.
But I did pick up on something this *is* interesting. The sysprep image has several folders excluded (using image explorer). I've just edited the image to re-include these folders, so that nothing is now excluded and guess what? The image now appears to deploy smoothly.
Interestingly, when imaging through DOS the image deployment crashes, and badly overunning its memory and overwriting the screen with random characters.
So, in short it looks like a bug when using folder excludes....
Kind Regards,
Ian./
Ian Atkin, Senior Developer for the ICT Support Team, Oxford University, UK
Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads&
That is interesting! Thanks for posting your results! If it is a bug, you should be able to open a no-cost incident with support.
Stu
ITS Partners
LinkedIn
I have seen the ugly eror -99 - our image is 2 partioions, the c: was set to 70% and the D: to 30% - I changed it to 50-50 and that fixed it
Hi,
I'm still working on this with Altiris Support. It really seems to be related to the using folder excludes. I excluded c:\windows from an image, and rdeploy failed really quickly. This is great as I could send an entire packet trace of the deployment to Altiris Support.
It's a single partition image, so the fix above won't apply here. I've moved now to using Linux automation -Rdeploy crashes here with an "unspecificed error" :Error 6.
Just need to wade through with support I guess.
Kind Regards,
ian/
Ian Atkin, Senior Developer for the ICT Support Team, Oxford University, UK
Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads&
Would you like to reply?
Login or Register to post your comment.