maxXPsoft

Some things that bother me but I don't know why you say it work on 30 of 40 It seem that you should have used CopyProfile on original image. To copy the Administrator profile I think you need to AutoLogon with Admin or his profile folder don't exist.

1. Make sure you burn any MS iso at 4x max. I had errors with Dell mainly burning faster 2. never in the setuperr.log. Look for error in setupact.log. I don't see anything in the setupact.log. Did you copy this from C:\Windows\Panther? Sometimes the error reflects in C:\Windows\Panther\UnattendGC

you won't get much reduction in size removing images EX: I removed Premium and my iinstall.wim decreased from 2.75 GB to 2.73 and I did cleanup on it also to remove [Files] so uhhhh whats the use

Did you remove or rename the ei.cfg? That will install whatever image it was intended for [EditionID] Professional Without removing the ei.cfg you need to specify image to install in the xml. Look at <ImageInstall> here <Value>Windows 7 ULTIMATE</Value> EDIT: http://technet.microsoft.com/en-us/library/dd744535%28WS.10%29.aspx

It process all driver sub folders in that folder No to WU. Get sp1, inject all WU and then use as base image People have done that with 64 and 32 Go back and read the first link I gave you and look for SP1 original iso, over there it will tell you how to install different images by manipulating the ei.cfg. I simply delete or rename and can install any image then. If you don't specify in xml then it will ask which you want to install

scroll sown to Adding Boot critical and all other drivers

You do quotes "" like this in xml "HKLM\SOFTWARE\Policies\Microsoft\Windows NT"

Thats tricky determining exactly which drive/partition is which when Win will make a install drive E or F depending how many you have and then when it boots it switches boot part to C:. For instance if you have the small 200mb part it will be C yet when OS boots Win becomes C. Hope you understand. I just keep my data partition backed up to external usb (SAFE) before my experiments

Install with the actual key on an xml and don't complete oobesystem. Can just shut it down when eula comes up use an xml If you want to install software then use audit mode and shutdown the PC coming out of that. page__view__findpost__p__892782 I see you have this also http://www.microsoft.com/OEM/en/downloads/Pages/ExpressDeploymentTool.aspx

<DiskConfiguration> <WillShowUI>Always</WillShowUI> </DiskConfiguration> won't hurt a thing if you want it to do that. That is early on

removes it from installed xml found in Panther folder after install <Password>*SENSITIVE*DATA*DELETED*</Password> just delete original xml

think all you need is something like this but am not sure with MDT This contains a Recovery and the small system reserved, just modify and fix for what you need partitions.cmd diskpart select disk 0 clean create partition primary size=15000 format quick fs=ntfs label="Recovery" assign letter="R" set id=27 create partition primary size=300 format quick fs=ntfs label="System" assign letter="S" active create partition primary format quick fs=ntfs label="Windows" assign letter="W" exit

sim sometimes will not tell errors just crash on an install BSOD 1 time I fought several days time permitting 100 or more full install and no vm both with vista and 7 debugging Se7en_UA to create it. sometimes things that work in vm will not in an actual install can capture your Panther logs and see error's myselfidem is well versed with it also

that's confirmed

We have been through this many times. Can't install some things if they are User specific till a user logs on. Only other alternate is use Audituser pass and log that user on and install. But you have 3 different clients so would have to do 3 diff images. Someone used a script here somewhere where certain criteria are met then A happens otherwise B happens using Firstlogon I think. Don't remember where that is at. Might have worked off IP address as I was showing you in a post

No only used right at that point, may stay till reboot I tried 2nd cmd file and couldn't even see it so was hung on Choice. I do see exe, msi flashing up I meant autoit script compile to exe. I never wrote one with a choice menu

but you need this first cmd line also as I said setupcomplete run's invisuble, perhaps craete a autoit with Choice variables you wanted

oops forgot I added that key I'll update first <DriverPaths> <PathAndCredentials wcm:action="add" wcm:keyValue="1"> <Path>$WinPEDriver$</Path> </PathAndCredentials> </DriverPaths>

Updated first post with this Adding Boot critical and all other drivers to an OEM installation if you don't want to inject - tested and working in a VM today

Will only work for newer PC with Slic 2.1 bios. OEM typically

OK <Path>%systemdrive%\Drivers</Path> don't work there. It looked on X which is PE loaded into ram 2011-08-07 15:03:56, Info PnPIBS: Finished building list of drivers in the path X:\Drivers. 2011-08-07 15:03:56, Info PnPIBS: WARNING: Could not build list of driver packages at X:\Drivers. heres setupact.log looking for drivers so if folder was named WinPEDriver it would find? 2011-08-07 15:03:56, Info PnPIBS: Checking for pre-configured driver directory C:\$WinPEDriver$. 2011-08-07 15:03:56, Info PnPIBS: Checking for pre-configured driver directory D:\$WinPEDriver$. 2011-08-07 15:03:56, Info PnPIBS: Checking for pre-configured driver directory X:\$WinPEDriver$. That may be only boot critical I am unsure, I'll redo and change folder and see what happens

http://technet.microsoft.com/en-us/library/cc748846%28WS.10%29.aspx EDIT: This explains better http://technet.microsoft.com/en-us/library/dd744282%28WS.10%29.aspx I'll know after I can run a VM

nonPE goes in offline servicing. WinPE is <settings pass="windowsPE"> I am trying this as soon as my .msu finishes Processing 16 of 48 - Adding package D:\Se7en_UA\HFixes\Windows6.1-KB2496898-v3-x64.msu Use instead <Path>%systemdrive%\Drivers</Path> There are some other things I'll have after my VM test

$OEM$\$1\Drivers <settings pass="windowsPE"> <component name="Microsoft-Windows-PnpCustomizationsWinPE" 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"> <DriverPaths> <PathAndCredentials wcm:action="add"> <Path>%systemdrive%\Drivers</Path> </PathAndCredentials> </DriverPaths> </component> </settings> I think that will work but haven't tried it. Using $OEM$ Drivers folder should be there when needed