<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
	<title type="html"><![CDATA[DriverPacks.net Forum - Network drivers missing in Sysprep Mini-setup]]></title>
	<link rel="self" href="http://forum.driverpacks.net/extern.php?action=feed&amp;tid=4872&amp;type=atom"/>
	<updated>2010-11-02T16:01:17Z</updated>
	<generator>PunBB</generator>
	<id>http://forum.driverpacks.net/viewtopic.php?id=4872</id>
		<entry>
			<title type="html"><![CDATA[Re: Network drivers missing in Sysprep Mini-setup]]></title>
			<link rel="alternate" href="http://forum.driverpacks.net/viewtopic.php?pid=41162#p41162"/>
			<content type="html"><![CDATA[<p>Further testing: I carried out exact same steps as above except this time sysprep&#039;d using sysprep files on local c and bypassed using bartpe and offlinesysprep. The result was the correct drivers loaded during mini steup. Therefore somewhere during offlinesysprep/sysprep in bartpe something goes wrong. If the driverpacks are confirmed as working fine without offlinesysprep then im guessing this its not a driverpack issue.</p><p>I am now testing the following. Devpath.exe, D on C etc, Sysprep on local c and reseal. Then reboot into bartpe and use all offlinesysprep functions required (mass storage and hal etc) but dont use sysprep afterwards. Then reboot. Will posts results</p>]]></content>
			<author>
				<name><![CDATA[Yakuzi]]></name>
				<uri>http://forum.driverpacks.net/profile.php?id=14269</uri>
			</author>
			<updated>2010-11-02T16:01:17Z</updated>
			<id>http://forum.driverpacks.net/viewtopic.php?pid=41162#p41162</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: Network drivers missing in Sysprep Mini-setup]]></title>
			<link rel="alternate" href="http://forum.driverpacks.net/viewtopic.php?pid=41144#p41144"/>
			<content type="html"><![CDATA[<p>Hi Guys</p><p>I have found a resolution to my problem although im still not 100% as to what the issue is. Ive basically used an older version of driver packs 10.5 or 7 depending on the pack and still using SAD 1 and devpath in conjunction with offlinesysprep. The drivers (most importantly LAN) install correctly during minisetup. I understand that device drivers sometimes do not install correctly if chipset drivers fail in mini setup so im not sure how to find out weather its a chipset failure or LAN or maybe something else. Im going to test using working driver packs but use the latest LAN pack and see if it still works.</p><p>Will let you know the result</p>]]></content>
			<author>
				<name><![CDATA[Yakuzi]]></name>
				<uri>http://forum.driverpacks.net/profile.php?id=14269</uri>
			</author>
			<updated>2010-11-01T12:10:28Z</updated>
			<id>http://forum.driverpacks.net/viewtopic.php?pid=41144#p41144</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: Network drivers missing in Sysprep Mini-setup]]></title>
			<link rel="alternate" href="http://forum.driverpacks.net/viewtopic.php?pid=41078#p41078"/>
			<content type="html"><![CDATA[<p>I’ve checked that the reg key HKLM\Software\Microsoft\Windows\CurrentVersion,DevicePath&#039; is populated correctly starting with %SystemRoot%\Inf;.........................</p><p>I’m am using latest driver packs and BASE 10.06. I’ve read a few posts mentioning to use 9.1 driver packs. Can anyone else recommend this or am I good to use latest and greatest?</p>]]></content>
			<author>
				<name><![CDATA[Yakuzi]]></name>
				<uri>http://forum.driverpacks.net/profile.php?id=14269</uri>
			</author>
			<updated>2010-10-29T08:51:19Z</updated>
			<id>http://forum.driverpacks.net/viewtopic.php?pid=41078#p41078</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: Network drivers missing in Sysprep Mini-setup]]></title>
			<link rel="alternate" href="http://forum.driverpacks.net/viewtopic.php?pid=41069#p41069"/>
			<content type="html"><![CDATA[<p>In my testing, dp_inst_tool was not even needed. Devpath alone was sufficient for Mini-Setup with UpdateInstalledDrivers=Yes and DriverSigningPolicy=Ignore. It was not necessary to select Detect Non-plug and play hardware. That extra step just took more time and made no difference.</p>]]></content>
			<author>
				<name><![CDATA[techie1]]></name>
				<uri>http://forum.driverpacks.net/profile.php?id=14220</uri>
			</author>
			<updated>2010-10-29T02:37:13Z</updated>
			<id>http://forum.driverpacks.net/viewtopic.php?pid=41069#p41069</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Network drivers missing in Sysprep Mini-setup]]></title>
			<link rel="alternate" href="http://forum.driverpacks.net/viewtopic.php?pid=41058#p41058"/>
			<content type="html"><![CDATA[<p>Hi Guys</p><p>Firstly I would like to mention what a fantastic resource this site is. I&#039;ve been gradually building a hardware independent image using particular posts from Overflow, Somebody, Jack_F and of course Galapo who have helped me massively so thank you very much</p><p>OK so im new to the forums.&nbsp; I have successfully built a universal image using mysysprep and ghost/WDS which I thought was running perfectly on many machines in my domain and assumed I had reached Universal Image heaven. This was using the excellent driver packs from this site. Then last week I came to deploy an image on a SATA configured computer and of course got the lovely BSOD 0x7b. I went down the route of tweaking the BIOS without much luck so got into researching Galapos Offlinesysprep with the view of injecting the MassStorage Drivers</p><p>I already had a working BARTPE CD so decided to add the plugin and formulate a method of integrating the Mass storage to include SATA. After a few weeks of reading all posts I have managed to compile a method which I think might just work. The problem I have come up against I don’t believe is offlinesysprep based but I could be wrong.</p><p>Method</p><p>1. Ready configured windows image to sysprep <br />2. Compile Bartpe CD with offline sysprep plugin and mass storage plugin<br />3. Create SAD folder using BASE and method 1 for cpu and the manuall extract all other driver packs<br />4. Copy D (all extracted drive packs inside) directory to C route of sysprep machine (Inlcuded routeDP_Install_Tool.cmd and Devpath etc)<br />5. Run c:\devpath.exe c:\d<br />6. Add call in gui runonce to run dp_inst_tool (this was carried out before compile of bartpe)<br />7. Now I boot bartpe and run offlinesysprep</p><p>General config<br />- User profile - Admin<br />- Optional select extra drivers - Blank</p><p>Advanced<br />-Inject HWIDs supported out of box<br />-Install standard IE mass storage devices<br />-Install all non IDE drivers (SATA)<br />-Suppress Driver signing warnings</p><p>8. Then for sysprep<br />-Don’t reset grace period<br />- Use Mini Setup<br />- Detect Non-plug and play hardware<br />- reseal</p><p>9. Then after reboot I go through sysprep and normally I would insert the Windows key and add local admin password and the network drivers would install and then I would join to the domain manually. For some reason the network drivers &quot;install&quot; very quickly/too quickly and then sysprep skips domain joining and finalises. As a test I removed the runonce dp_inst_tool and let the computer boot into windows after not joining to domain and noticed I had no IP address (network driver issues!)</p><p>10. Once this process finishes computer reboots and dp_inst_tool runs fine installing all drivers</p><p>My question is once I have run c:\devpath.exe c:\d, should this not be sufficient for mini setup to grab all necessary drivers? Do I need select Detect Non-plug and play hardware in sysprep or is the line in my inf file below “InstallDefaultComponents=Yes” also sufficient. </p><p>here is a copy of my sysprep.inf file:</p><p>;SetupMgrTag<br />[Unattended]<br />&nbsp; &nbsp; InstallFilesPath=C:\sysprep\i386<br />&nbsp; &nbsp; UpdateInstalledDrivers=Yes<br />&nbsp; &nbsp; DriverSigningPolicy=Ignore</p><p>[GuiUnattended]<br />&nbsp; &nbsp; EncryptedAdminPassword=NO<br />&nbsp; &nbsp; OEMSkipRegional=1<br />&nbsp; &nbsp; TimeZone=85</p><p>[UserData]<br />&nbsp; &nbsp; FullName=&quot;Seventeen Group Staff&quot;<br />&nbsp; &nbsp; OrgName=&quot;Seventeen Group Limited&quot;</p><p>[TapiLocation]<br />&nbsp; &nbsp; CountryCode=44</p><p>[RegionalSettings]<br />&nbsp; &nbsp; LanguageGroup=1<br />&nbsp; &nbsp; SystemLocale=00000809<br />&nbsp; &nbsp; UserLocale=00000809<br />&nbsp; &nbsp; InputLocale=0809:00000809</p><p>[SetupMgr]<br />&nbsp; &nbsp; DistFolder=C:\sysprep\i386<br />&nbsp; &nbsp; DistShare=windist</p><p>[GuiRunOnce]<br />&nbsp; &nbsp; Command0=&quot;c:\DP_Install_Tool.cmd&quot;<br />&nbsp; &nbsp; Command0=&quot;\\10.1.20.3\klshare\Packages\NetAgent 8.0.2090\lsexec.exe&quot;<br />&nbsp; &nbsp; </p><p>[Identification]<br />&nbsp; &nbsp; JoinDomain=atlgroup</p><p>[Networking]<br />&nbsp; &nbsp; InstallDefaultComponents=Yes</p><p>Everything else seems to be working well so im hoping this is a simple fix<br />On a side note im a using latest driver packs, XP SP3 (all updates) the recommended version of sysprep in Galapos help file and the latest version of sysprep.</p><p>If anyone could point me in the right direction I would be massively appreciative and I hope I articulated this well enough</p>]]></content>
			<author>
				<name><![CDATA[Yakuzi]]></name>
				<uri>http://forum.driverpacks.net/profile.php?id=14269</uri>
			</author>
			<updated>2010-10-28T16:42:05Z</updated>
			<id>http://forum.driverpacks.net/viewtopic.php?pid=41058#p41058</id>
		</entry>
</feed>
