Tuesday, February 26, 2013 10:10 PM
I am trying to install a test image with IE10 slipstreamed in and getting an error "Windows could not parse or process unattend answer file [C:\windows\Panther\unattend.xml] for pass [specialize]. A component or setting specified in the answer file does not exist." I used an original Win7 Ent SP1 image + IE10 and then imported full source as if from original DVD / ISO. Then created a new sequence and problem still occurs.
I think it is being caused by:
<component name="Microsoft-Windows-IE-InternetExplorer" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
Which I am not sure is a setting I set in MDT setup or a default setting? This setting has been removed from IE10.
Tuesday, February 26, 2013 10:40 PMFor clarification, please define "slipstreamed".
Jason | http://blog.configmgrftw.com
Tuesday, February 26, 2013 11:34 PM
Did you follow this?
Im guessing this is what was meant by slipstreaming..
Taken from the above link...
Preinstalling Internet Explorer 10 on Windows 7 SP1 or Windows Server 2008 SP1
You can preinstall Internet Explorer 10 on Windows 7 SP1 or Windows Server 2008 R2 with SP1, by slipstreaming Internet Explorer 10 into the operating system image. At this time, Microsoft only supports the English (en-us) version.
Twitter: @iddonline.....Any advice given in these forums should be tested in a non production environment before implementing.
Wednesday, February 27, 2013 2:01 AM
Why slipstream it? Just run an silent install as an application during capture?
If not, you can always edit the Unattend.xml using WSIM and remove that key from the Unattend. If I remember WISM will warn your that that key is deprecated, but it usually wont error.
Wednesday, February 27, 2013 12:30 PMYes I followed the above instructions (almost identical to IE9 process). I slipstream since I know it is going to be in all my future builds so I spend the time once building it into image rather than causing every deployment to take longer. I try to optimize the speed of deployment as much as possible so anything I can do ahead of time is a plus. I did edit the unattend.xml and removed it but I was trying to figure out if I was going to have to do that everytime I create a new task sequence or if it was a default setting I could change in deployment config. Having this in unattend.xml will cause an infinite reboot during deployment and will not allow setup to complete properly.
Wednesday, February 27, 2013 8:49 PM
Do you have much in the unattend? We have a pretty complicated deployment here and I don't have anything in the unattend at all, all done through MDT itself. Maybe the setting that you require to change in the unattend you can move out and just leave it as the default.
Come to think of it, you can edit the default unattend (that is used as a template). You can find the template in your local workstation under C:\Program Files\Microsoft Deployment Toolkit\Templates , remove that key and you will only ever have to do it once!
On a side note, I understand your point regarding the slipstream, I'm also working towards streamlining as much as possible.... for gods sake lets just get SP2 ha haEDIT :: Just a reminder though, if you change the unattend template on your workstation, it is ONLY for your workstation. Any other techs working on it will not have it unless you copy it over.
- Edited by mhouston100 Wednesday, February 27, 2013 8:50 PM
Wednesday, March 06, 2013 4:02 PM
I get this as well. I updated my base image with Internet Explorer 10, syspreped it as usual and copied it up to our deployment share. Deploying gets as far as you before failing.
My unattend has very little in it & doesn't have any IE stuff in it at all.
This process always worked previously with IE9.
Thursday, March 07, 2013 10:23 AM
ok, this was pretty easy to fix actually.
Right click your task sequence > OSinfo > edit unattend.xml.
Wait 5 hours for it to process (zzzzz)
Then in WSIM find Microsoft-Windows-IE-InternetExplorer
Look for IEWelcomeMsg > right click and disable "write image value" Save the unattend.
You should be able to deploy then.
- Proposed As Answer by DrCheese128 Thursday, March 07, 2013 10:23 AM
Thursday, March 07, 2013 11:26 AM
you can go to the control folder in your DS and look for the folder with your task sequence id and open the Unattend.xml from there with wsim it will save you time.
might be that you need to point wsim to the right catalog file then though.
- Edited by Stefan Sonneveld Thursday, March 07, 2013 2:02 PM
Thursday, March 07, 2013 1:35 PMThanks, didn't realise that. Will save lots of time!
Thursday, March 14, 2013 9:55 PM
I'm having the same issue.
I'm using MDT 2012 and the "IEwelcomeMsg" is already set to false with the "write Image Value" checked. When I Right Click the "IEwelcomeMsg" I do not get a disable option. I only see revert change or wrtie image value.
So in order for me to get a test deployment to work is to delete the whole IE string from the specialized phase. Only now I've lost my settings.
Thursday, March 14, 2013 9:57 PM
Uncheck the "Write image Value" bit, then it won't enter that into the .xml & deploy fine.
Thursday, March 14, 2013 10:12 PM
Ok will try it.
Friday, March 15, 2013 2:03 AM
After Running numerous tests I can confirm that everything is working just fine.
Thanks for the advice DrCheese, not so stressed out now =)
Funny how one change via Windows Update can screw up your deployments.
Friday, May 03, 2013 6:58 PM
Thank you for this fix, it pays to google the problem and up pop this thread.
This is correct answer.
Please bear in mind, that my answer is based on the details given in your post. The more I get the better the answer, Slan go foill, Paul
Friday, May 03, 2013 7:21 PM
It drives me nuts when I google, find someone with the same problem but no answer!
I make a point to go back to threads if/when I find a solution and post it to avoid someone else having the same angst as me :P