gotenks98

I don't know. Evidently you are doing various experiments but what you need to post is a "sinchronized" set of two files (the autounattend.xml and the .cmd) and express your perplexities/doubts/resulting issues/whatever referred to that exact set (and not to the ones you have on your machine and that you have in the meantime changed n times). Remember that every time someone trying to help you has to guess something (besides the unfair additional effort he has to bear) it is more likely that you will be sent on a wild goose chase instead of the direction where the solution is. jaclaz Sorry I meant to post a reply about this sooner but my system crashed before I could post it earlier. For the script I had to put it as cmd /c start /b /wait then the command. What was happening is that it was opening a another cmd window which the system thinks the other command has terminated and goes on to the next step. If I put a /b there it does not. I am getting very close to finishing this now. I just need to figure out the xml part that configures the recovery to use the unattend file. I just need to know the syntax of the WinREConfig.xml file. I do have another question but its MDT related. Does any know if MDT can deploy multiple partitions from an image file? Like say my sys prep wim file and my image of the recovery partition to a specific partition?

2. WinRE uses Setup.exe to apply the recovery image. Indeed it doesn't seem to care about the answer file used if one was applied with sysprep prior to capturing the image. Take a look here: http://www.msfn.org/board/topic/142990-installing-windows-7-from-recovery-partition/?p=918385 3. Reagentc commands are written to where your BCD is located. 4. You use Diskpart to set the partition ID after you run the Reagentc commands. Yes this is exactly what I am looking for on my issues. So if I open the Winre.wim and put in my xml file in the proper place will it use that instead? I am a little confused about this factoryrecoverytool Is this something you created or is it just named that? Also if say I am doing my initial imaging to a machine using normal windows setup from a usb drive how or where would I script to in the xml file to set the reagentc commands?

Sorry about that with the cmd file. I also have tried it both ways with the /s /q before and after the path. What I found is that I spelled autounattend wrong on one instance of this script. However now I am noticing that it wants to delete the directories before all the other lines of the script are finished. The delete directory command is at the end of the script. I have even tried moving the delete command to the autounattend file instead of being done at the setup complete. Is there some catch to making these commands go in and order and not execute to the previous one is finished. I thought that was the whole point of the firstlogoncommands synchronous. Maybe I am doing something wrong with the start /wait commands?

I have attached my autounattend.xml and my setupcomplete command. Originally I had the autounattend.xml file to call the setupcomplete.cmd but I still got the same issue of the deleting directory still saying that the directories are empty. Also I still need to know where the files that reagenct edits gets stored so I know what to do to ensure my recovery image works. Maybe I need another script that sets this during windows setup? autounattend.xml setupcomplete.cmd

I have been struggling for the past 3 weeks trying to come up with a recovery solution for our loaner program so I dont have to reimage machines so often. What I wanted to do is capture an image, sysprep it, and have a bunch of scripts that run to install apps and install drivers using dpinst. When I capture the wim file I want to use it as the recovery image by setting it with reagent.exe . I want to then capture an image of the image (wim file within wim file) so that during windows setup when I do the initial image of the machine it does an apply of the first OOBE captured wim on the c: drive and apply of the recovery partition which is the r: drive which will be hidden from the user. I have ran into a few issues with this. Problem #1 my script to delete the directory that has the following issue, it keeps saying that there are empty folders which can not be deleted. These are folders that contained drivers that were used in the dpinst step Problem #2 after the first initial boot up and factory reset after log in the factory reset no longer uses my answer file that was used in sysprep. I am not sure whats going on here so I even tried putting the autounattend.xml in the root of the c: and it still gets ignored when the factory reset is done. Problem #3 I can not figure out where the reagentc.exe file writes to. If I am going to make a image with dism I need a way to make it so upon applying both index images I dont have to do the setreimage and setosimage commands again. Problem #4 I am not sure how I can set the id value of the disk to 27 and still make it so that the reagentc.exe finds the winre and install.wim files. My thoughts are that once I set it to hidden with diskpart it wont find the recovery options. Small Edit Problem #5 In the past I used to use firstlogoncommands and I would get this nice little check list in the upper left corner that says what has installed or succeeded. However since MS changed from the WAIK to the ADK I have not been able to get this to work again. Instead of installing applications one at a time, It just fires off all the executables at once instead of waiting for the first one to finish. I have had to switch to doing this via the setupcomplete.cmd batch file which is called in the autounattend.xml under firstlogoncommands. I just wish there was a way to change this back and have it to still work. Any ideas on how to solve these issues?

You just need to put it in the sources folder. The other media discs only need a sources folder for the other images.

Anyone figure out how to do the audit mode install from dvd/usb from windows 8? I been struggling with this for a few months now and nothing I have found online works.

I have a similar version of this unattended file and it works great on windows 7. Its pretty much a copy paste of the same thing but its in a windows 8 answer file. I went this route instead of the setupcomplete or using a cmd file because it makes a nice little check list of what apps installed. If you notice sometimes on new systems at the first log in there is a box that shows what installing or whats configuring and it goes down the list. I will check the administrator thing and set it to enabled and report back to see if anything is different.

I am trying to do a scrpted install of windows 8 via the audit mode using an autounattend.xml file. I am having 2 issues. First is during the first reboot after its done extracting the image to the HDD it hangs on the first reboot. It will not reboot and I have to power off the machine. Second issue is it does not install any of the applications I want to install in audit mode. It takes a really long time to even do the audit mode log on. It stays on loggin in administrator with the little swirlly thing. After some time it errors with a diaglog box with slash commands for a using the wusa.exe to install *.msu files. I was wondering if I need to move the quotes in the xml file due to the spaces in the folder name. Here are my xml files. Let me know where I am going wrong on this. autounattend.xml unattend2.xml

Your listing of updates will come in handy. I think I have almost as many if separating them out like that. What I will do is put all the critical updates separate and save the images in sections, like 30 updates at a time.

This is what I am trying to do but I keep getting failures on the updates when it gets like 30+ updates in. It keeps saying the image is no longer serviceable. I have to basically start over if I get this.

I figured it out. The issue is 2 things. One machine integrated from gave me a different error than my windows 8 machine. If I do it from the windows 8 machine it actually gave me an error I could look into using the log files. It ended up being one of the settings in the unattend.xml file that's depreciated. The problem is I never changed that setting it comes default in the answer file. So I had to delete the internet explorer section of the unattended file and re-add it after I updated the catalog file to show IE10. Once I did this it worked using MDT 2012. This problem could have been easier to figure out had I started the integration from the Windows 8 machine. My thoughts are that there is a bug in the Windows ADK that if you do integration from windows 7 it does it differently than windows 8. I got all kinds of weird errors doing this differently on Windows 7.

Question for those who got this working what did you do for testing? Like did you use a VM or real machine. I am currently using virtualbox in testing this and its still not working. I have verified the image I have is good, I redownloaded the msu and exe from microsoft's site directly. I integrated using the Windows ADK using the exact same dism code. So this makes me think something else is causing this and not what I am doing. I am going to try this with VM ware next to see if it works. Nevermind scratch this, still does not work in VM ware.

To be honest microsoft has made a huge mess with this especially on vista. Its had so many post sp2 updates and more than half of the stuff is not integrateable now. What I just end up doing to get all the updates is just do a full install and manually update everything then capture the image. The reason being is there is just too much trial and error as to what will and wont integrate with this now. It just takes way too long doing it the other way only to have more than half the crap not even integrate. And dont get me started on the whole .net framework thing, its a nightmare.

This kind of defeats the purpose of what I am trying to do. I am hoping to deploy it so that when the later updates come I can just add them to the folder just like I did with IE9 and MDT would just work. It is not working at all for ie10

This whole thing has been a pain. I have tried suggestions in this thread as well as the other thread. It always errors out with windows could not configure one or more components. This is with just integrating it and installing normally and also integrating it and deploying with MDT. It just does not work. If I try to just deploy all of it the pre-reqs will install but no IE 10 but it does not error out. I tried using the pre-reqs in the document that's extracted and the pre-reqs listed online.

What other 3 updates? I did it whats listed in the first post, I even tried what was required thats in the text file that gets extracted when you extract IE 10. I even tried just integrating it and not using MDT to push out the patches and I get an error of "windows could not configure one or more system components" and the install fails. I even used the integrity check switch to ensure there were no errors.

That's because IE10 needs 4 updates to be installed/integrated before IE10 can be installed/ntegrated, you will find those updates in my first post. Still does not work. Still shows IE 8 when I try to deploy with the cabs in MDT 2012. The 4 cab files do get installed, just not IE 10. If there was a way to get them to install in a certain order it might work.

Thanks, I will give this a try when I return to work. This whole thing has been a pain trying to get it to work.

Anyone get this to work with MDT using the cabs? I am trying to deploy this like the other updates but it never installs it.

I just wanted to know has anyone successfully deployed windows 7 with IE 10 using MDT 2012 just using the cabs or msu files, not doing it post install. For IE 9 I can do this pretty easily but I just cant quite figure out why it does not want to install during the apply patches part of my task sequence.

I just wanted to know has anyone done any deployment testing where you timed your deployment speed in certain aspects. I am trying to test whether slipstreaming the patches into an image then deploying the image is going to be faster than just letting the install pull the patches from the server. I do know that with a slipstream there is a point during the install where the computer has to still process the patches. So maybe it will still take just as long if not longer to do that vs just letting mdt pull the needed patches.

I pulled it in straight from the ISO from MSDN. Full source files and all. No customizations were made aside from changing the answer file. I tried it with both x64 and x86 boot.wim. I even tried it with the default answer file that gets generated. Still nothing.

I can create task sequences for Windows 7 and Windows 8 just fine but for some reason the vista task sequence never show up when I boot from the image. I do not have it set to hide anything and have created the task sequence the exact same way as windows 7 and 8. Is there some new restriction that keeps vista from working with this now? I just want to note that my boot media for the MDT 2012 is using the boot.wim from windows 8.

One is an executable type update and the other is just online only because its an update to the service stack, kind of how SP1 was to Windows 7. I really wish microsoft would post something to let us know what updates are integrateable or not. I spent 2 days trying to figure this out.