Creating a new VM from a template fails on step 1.6.5 with error "windows could not parse...unattend answer file"

Creating a new VM from a template fails on step 1.6.5 with error "windows could not parse...unattend answer file"

  • Comments 1
  • Likes

fixHere’s an issue that might bite you if you’re not mindful of it.  I ran across this a few days ago so I thought it would be worth mentioning here just in case:

========

Issue: When attempting to create a new virtual machine from a template in System Center Virtual Machine Manager 2008, the process may fail during step 1.6.5 with the following error that shows up on
the new VM after a reboot:

Windows could not parse or process the unattend answer file for pass. The settings specified in the answer files cannot be applied. The error was detected while processing settings for component [microsoft-windows-shell-setup]"

No errors show up in the SCVMM console for that job unless you cancel the job. Then you will see a generic 12700 error.

Also of note is that the VM will reboot repeatedly unless the job is cancelled.

Cause: In this case, the Administrator password had not been set to blank and the password complexity policy had not been disabled.

Resolution: For SysPrep to succeed, the admin password must be blanked out on the Source VM that was used to create the template.  Unfortunately there’s no way to fix this after the fact but to prevent it from happening in the future be sure to clone the VHD (always a good practice!) and then make sure you follow the steps in the following article:

Creating a Windows Server 2008 Template in SCVMM 2008

Michelle Foley | Senior Support Escalation Engineer

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • do you have an update for this for SCVMM 2008 R2? I have an issue where the VM creation is hanging at step 1.8 71% (95% overall) and the same VHD works on a different SCVMM instance so I doubt its the password issue stated above, but I am getting what appears to be the same error message when I connect to the VM.