Config Mangler

Found the source. The date and time were wrong in the BIOS i.e. set to 2010. As soon as I set it to today the task sequence started. I also had a Lenovo X200 with the same problem, it was 4 days out in the BIOS, again changed it to today and it worked straight away. That was sheer luck that I noticed a log file had an old date on it. So to clarify the Toshiba R700 and Tecra A11 need Intel's own 82577LM v.11.2.19.0 driver added to SCCM 2012 The X200 did not need a driver added

Well I got a little further. I added this set of WinPE 3.0 drivers from Dell to my boot images and the Toshiba R700 will now build http://en.community.dell.com/techcenter/enterprise-client/w/wiki/2069.aspx It is still inconsistent though. The Toshiba Tecra A11 has the EXACT same NIC with the same Hardware ID's as the R700 but will not build. The Lenovo X200 will still not build even though the 82567LM is now listed in PE.

Still having problems with this. Let's take the Lenovo X200. The driver in Windows 7 is the Intel 82567LM. If I import the driver into SCCM for the PE image it shows that an Intel 82567-2LM was imported. If you search inside the .INF file the 82567 and 82567-2 are both listed. Yet when I boot to install the image it is still failing. I have tried removing all vendor NIC drivers from SCCM and using only the set from Intel to no avail. Same problem with Toshiba R700 and Tecra A11 using Intel 82577LM. The driver is not native in Win 7 or in PE. Importing the vendor or Intel drivers to PE does not list the 82577LM driver even though the 82577LM section is present in the driver INF Is this maybe a problem with the SCCM driver database matching the drivers? Anything else I can try?

Well, the error in the Microsoft-Windows-Shell-Setup section was caused by the <ProductKey></ProductKey> line. When I remove this one line I get prompted to accept the EULA after the build which is not ideal. If I remove the whole Microsoft-Windows-Shell-Setup component it does not prompt me. Sub components of this component process ok. I will probably leave this section out and script the parts it omits. The main problem I have with this is that the SIM validates the XML file and it passes. If you run sysprep with the XML file you can see it specifically checking the specialization section and that passes too. We were getting these sort of errors 10 years ago with Sysprep and unattend.txt. Nothing has changed. The 1024x768 resolution was at the bottom of unattend.xml so that's my mistake.

Yes deploying x86 - I don't know if this is relevant, but to generate the unattend.xml I have to run WSIM on a 32-bit server and point it at the WIM on the 64-bit SCCM 2012 RC1 server. This "feature" existed in MDT 2010 too. Basically you can't catalogue the 32-bit WIM on 64-bit server.

I was getting an error with unattend.xml - "Windows could not parse or process unattend answer file for pass [specialize]. section Microsoft-Windows-Shell-Setup. Can anyone see anything wrong with this section? It was validated in WSIM (for what that's worth) <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.micro...nfig/2002/State"> <ComputerName></ComputerName> <ProductKey></ProductKey> <RegisteredOrganization>My Organisation</RegisteredOrganization> <RegisteredOwner>User</RegisteredOwner> <TimeZone></TimeZone> <DoNotCleanTaskBar>true</DoNotCleanTaskBar> </component> Once I removed this section it carried on. It changed the regional settings to UK-GB which was great but it did not set the Organization or User name. It also set the resolution in Windows to 1024x768 which is wrong as this is only listed in the WinPE pass. I've attached the full unattend.xml Thanks in advance! unattend.xml

I have three models of laptop which PXE boot, load PE to a point, then reboot themselves just after the "Preparing Network Connections" screen is shown. I pulled in the latest NIC drivers for these models and updated the boot image, but that didn't help. Also turned the HDD drivers from AHCI to compatibility mode in case it was that. I get just enough time before it reboots to get a command prompt and see it get an address and I can ping the DC / DNS server. Any ideas what to look at or where it might be logged? Added - I have 11 other models of laptop and desktop building ok from the same environment.