K2000 problem processing unattend.txt
I have a failed kimage deployment that is failing during post deploy setup. Setup is unable to parse or process the unattend.txt for specialize. My question is can I fix the unattend file and save the image stored on the K2000 or must I start again?
I have error logs that show unattend action failed with exit code 4 and execution of unattend GCs failed 0x8030006. Plus other logs if needed
-
I don't believe the problem is with the answer file itself but in that I deleted a domain profile before adding settings as the default admin. I am trying now to fix the registry in the image files. Not sure how to do that quite yet. Your advise on backing up and creating a restore point prior to each ssyprep is great however and I will be sure to do that in the future. Thanks - mmalko 10 years ago
Answers (3)
Take a look at this link. http://support.microsoft.com/kb/2530664
Comments:
-
This was indeed my issue. I had deleted a domain profile and reconfigured the image as a local admin. After my failure, I went back and pulled the registry hive from the image files in the K-image, deleted that profile from the profile list so that I had just the four required and pushed the hive back to the image. After that, the image deployed just fine.
Thanks to all. - mmalko 10 years ago
start over and find bug in answer file.
Anytime I redo the answer file I sysprep, capture and reboot that machine first to see if it comes out of post before creating deployment.
I do not use virtual machines so I use the "create a system image" choice under control panel-backup and restore to make a copy prior to syspreping that I restore and update or fix bugs continually. Any update I make a new copy. You boot to a windows disk and restore the system with that image. Also that way all off my deployments have only been sysprep'd once.
I would first duplicate your image as a backup. Then click on Browse Files.
Browse to \windows\panther\unattend.xml and download the file.
Make the modifications you desire and then replace the file. Close the image browser window and commit the changes.
You can repeat the process until the issue is resolved.
However, I'm not convinced this issue is related to a misconfigured unattend file.
Corey
Lead L3 Enterprise Solutions Consultant, K2000
If my response was helpful, please rate it!
Comments:
-
Indeed, it was not the unattend. See above. Thanks - mmalko 10 years ago
