The IEWelcomeMsg was at fault. MDT was putting that line in all my unattend. I manually went in and deleted the following line:. Thanks for this guide. Originally I prepared a master image win7 32bit and ran sysprep, generalize, shutdown options before creating ghost image.
I followed your steps to go command prompt and changed the registry and managed to load windows successfully. Appreciate your guidance. I had this problem only in a VM and I was able to track it down to the ComputerName in my customsettings. On a physical machine that was fine, but in VMware Workstation it came with a huge "VMware " format which was too long I have also learned to compare my customsettings.
Where you have the PC name in unattend. Hope this helps someone. The hostname defined in specialized section of the unattend file was too long. Make sure your hostname is under 15 chars. One type of workstation is not working. Failing with the above error. Yeah CM doesn't like that. I , i know this is an old thread but this part also fixed my issue on MDT , i had capture my image with MDT and had the same parse error, i removed that line from my unattend. This line does work though with a bare image imported from a Windows 7 cd, my original image i used that same image to patch with windows update and capture, not sure why it failed with the WIM afterwards.
You're getting this error upon validation because that setting is only used if the "DisableFirstRunWizard" or "DisableWelcomePage" settings are toggled to true. If either one of those items are enabled, it "depreciates" or invalidates the IEWelcomeMessage setting Right click it and uncheck "Write Image Value".
What this does is tells WSIM not to write in that specific option or value when saving the image. I also do not see it being a name issue either, since we have the OSDComputerName variable enabled and the name I gave this VM is only 11 characters long. Office Office Exchange Server. Not an IT pro? Windows Client. Sign in. United States English. Ask a question.
Quick access. It was clear from the file that it would not allow any windows system upgrade or change. I simply deleted this unattend. This time it worked. It took me at least two weeks to get it done. Hope you can use my finding. Details required : characters remaining Cancel Submit 8 people found this reply helpful.
Any suggestions? This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread. I have the same question Report abuse. Details required :. Cancel Submit. Srimadhwa B. Hi Tom, Thank you for posting your question in the Microsoft Community.
Sorry to know that you are facing this issue. How satisfied are you with this reply? Thanks for your feedback, it helps us improve the site. In reply to Srimadhwa B's post on August 9, I don't know if that is helpful. Jackson Reece. In reply to TomKeeney's post on August 17, At the last screen, remove the check from Reboot when finished.
Plug into the computer the USB drive from the first step that contains the unattend. At the main Recovery Disk screen, click analyze, then click open a command prompt. Type dir and press enter to verify this file did indeed copy. Reboot the computer. The restored operating system should boot correctly after a lengthy hardware detection process and one or more reboots. Once in the operating system, X out of the System Preparation Tool that pops up on the screen. DO NOT select any of the options.
Open the Windows registry editor. Delete any value in the CmdLine key. Reboot the computer and log in normally. Attachments unattend. Was this content helpful? Yes No Rating submitted. Please provide additional feedback optional :.
Cancel Submit. You are using Microsoft Internet Explorer! Microsoft no longer supports this browser. As a result, some of the functionality on this website may not work for you.
0コメント