FireGeier

Hello zedox! There is something else missing in your Autounattend.xml. You need to change this: <RunSynchronousCommand wcm:action="add"> <Order>120</Order> <Path>%WINDIR%\system32\sysprep\sysprep.exe /quiet /oobe /reboot</Path> <Description>Restarting</Description> </RunSynchronousCommand> to this here: <RunSynchronousCommand wcm:action="add"> <Order>120</Order> <Path>%WINDIR%\system32\sysprep\sysprep.exe /generalize /quiet /oobe /reboot</Path> <Description>Restarting</Description> </RunSynchronousCommand> Without generalize CopyProfile will NOT work. Regards, Martin

Hello smileface! The second one is the subimage that boots to Vista setup, BUT my injection method is for install.wim only. If you want to integrate drivers into PE image, than you have to use peimg command line tool. So try out Mercury_22 batch, cause it's using peimg command for integration. Regards, Martin

Hello LeveL! use cmd /c in front of your command and it will work again: <FirstLogonCommands> <SynchronousCommand wcm:action="add"> <CommandLine>cmd /c REGEDIT /S %WINDIR%\system32\tweak.reg</CommandLine> <Description>RegEntries</Description> <Order>1</Order> </SynchronousCommand> </FirstLogonCommands> Regards, Martin

Hello zedox! Sorry, but did not knwo that - I've thought the command lines would not be executed at all. I've looked over your Autounattend.xml again and I miss the <CopyProfile> tag in specialize pass. Should look like this: <CopyProfile>true</CopyProfile> Look here inside guide for more information or you can have a look at ruudboeks Autounattend.xml file (specialize section). Regards, Martin

Hello zedox! You don't do it like described in guide exactly. You're using spaces in file and directory names, which always is a good way to run in problems. Please rename your directories and files and it will work or play around, where to put the quetes. That can differ from command line to command line! Regards, Martin

Hello ruudboek! Your error is cause by a double slash, look at the following parts inside your Autounattend.xml: <RunSynchronousCommand wcm:action="add"> <Path>cmd /c "FOR %i IN (C D E F G H I J K L N M O P Q R S T U V W X Y Z) DO IF EXIST %i:\AppsRoot.txt SETX AppsRoot %i:\ -m"</Path> <Order>1</Order> </RunSynchronousCommand> and: <RunSynchronousCommand wcm:action="add"> <Order>1</Order> <Path>cmd /c regedit /s %appsroot%\install\default.reg</Path> </RunSynchronousCommand> Your %Appsroot% variable will looke like this for example: D:\ That means your calling command looks like this for the moment for example - this is the way setup will read it: cmd /c regedit /s D:\\install\default.reg The two slashes will setup let fail! That means you have to remove the slash here, like this: cmd /c "FOR %i IN (C D E F G H I J K L N M O P Q R S T U V W X Y Z) DO IF EXIST %i:\AppsRoot.txt SETX AppsRoot %i: -m" Regards, Martin

Hello arablizzard2413! Yes, you're right that should be an easier solution and it should work. I'm not the "king" of batch programers, so it could be that there is further code which could be more simplified. Thanks for your input! Will try out and change, if it's working fine finaly. Regards, Martin

Hello smileface! First of all the driver installation from media (DVD, Stick etc.) will not work for bootcritical drivers like your SATA driver. But the injection method supposed to do that. So what kind of driver you want to install exactly? Could you please post you inject log file. And do you have injected the driver to the right image? Regards, Martin

Hello ruudboek & zedox! Could you please post your Autounattend.xml. And what kind of DVD you're using is it an OEM DVD? Regards, Martin

Hello deca! AFAIK there is no other way to leave audit mode, than using the sysprep command as Synchronous Command. That's the "official" way described in WAIK help. Or are you talking about something else? Regards, Martin

Well the workaround described on TechNet is a bit contradictorily. On the one hand it says to execute the reg add command after sysprep, which does mean after audit mode, cause you have to use sysprep to leave audit mode. On the other hand it says you could run the command in audit pass, too. I don't know how to leave audit mode, than. I'm still havin probelms with network location setting, too. Regards, Martin

Hello arabianhorse! Thank you very much for your feedback! I will try to reproduce your error and do some further experimentation with it. I guess that the PublicKeyToken value changes after an update integration has finished and this will cause the error message. Regards, Martin

Hello Deca! Do you use the main administrator account to apply the tweaks? Regards, Martin

Hello arabianhorse, could you please tell a little bit more detailed how you were integrating the updates. And where you got this report from (location). I could imagine that you may have to rebuild the catalog in WSIM by opening the modified install.wim. Than - based on this modified catalog - rebuild your answerfile and try again. Regards, Martin

Hello smsc! I'll need some time to check this log - it's not the shortest one. I would try to start with a "clean" install.wim and to integrate extras only, without the updates. So you could find out if it's never integrating extras properly for you or only if you're doing it in one step with the updates together. Regards, Martin

Hello woodswalker! Do you use the Vista Batchs? Which OS you're using?

Hello smsc! Do you have checked the logfile of pkgmgr already? What does it tell you? Do you install the updates and extras at the same time? Regards, Martin

Hello woodswalker! Do you have created a Sandbox folder before executing pkgmgr.exe? Regards, Martin

Hello idbirch2! The introduction explains, what BDD 2007 is. If you don't have it installed now, don't install it. It's not necessary to get the updates part to work. But you're right the guide is missing a little step here. If you don't have an Distribution Share folder already, you need to choose Create Distribution Share... from Tools menu in WSIM. And there you can choose any folder. Regards, Martin

Hello smsc! Thanks, for the feedback. I'll try to reproduce that on my system and will add a note, if same problem will come up here. Thanks again! Martin

Hello alexch! Just insert a Synchrounus Command to your Autounattend.xml using WSIM. Simply use UNC path to point to your share. Look here for general information about apps installation. Regards, Martin

Hello MC! Well it's not that easy to find such an error. I would first list all Device IDs on your system and than search for this device IDs inside setupact.log. There is a tool comming with BDD 2007 which is called Microsoft.BDD.PnpEnum.exe listing all device IDs on a system. Regards, Martin

Hello Yurek3! Do you have adapted wpi files to use them with Vista like described here? Note: You're using %AppzRoot%, so you need to change that to %AppzRoot% for WPI, too. Regards, Martin

Hello smsc! You're right. That was a misspelling. Except is right - so WSUSSCAN.cab is NOT needed! Thanks for pointing that out. Have corrected it now! Do you get the error with or wihtout using WSUSSCAN.cab? Regards, Martin

Hello Yurek! Please look here. You'veexactly the same problem like AMIT have had. Regards, Martin