<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The D-Spot (The Deployment Spot) &#187; WinPE</title>
	<atom:link href="http://www.the-d-spot.org/wordpress/tag/winpe/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.the-d-spot.org/wordpress</link>
	<description>Tickle your Deployment needs.</description>
	<lastBuildDate>Sat, 28 Jan 2012 15:43:53 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
		<item>
		<title>VMWare network drivers for WinPE 3.0</title>
		<link>http://www.the-d-spot.org/wordpress/2010/01/20/vmware-network-drivers-for-winpe-3-0/</link>
		<comments>http://www.the-d-spot.org/wordpress/2010/01/20/vmware-network-drivers-for-winpe-3-0/#comments</comments>
		<pubDate>Wed, 20 Jan 2010 15:35:17 +0000</pubDate>
		<dc:creator>Ben De Vriese</dc:creator>
				<category><![CDATA[MDT 2010]]></category>
		<category><![CDATA[AMD PCNet family]]></category>
		<category><![CDATA[VMWare]]></category>
		<category><![CDATA[WinPE]]></category>

		<guid isPermaLink="false">http://www.the-d-spot.org/wordpress/2010/01/20/vmware-network-drivers-for-winpe-3-0/</guid>
		<description><![CDATA[When capturing a reference image using VMWare Workstation/Server your WinPE image needs the right nic driver to contact the Deployment Share. Here is how to obtain and inject these vmware drivers into your WinPE boot image. First download the drivers from VMWare (link updated Sept 2010). (PCnet Family network adapter, NDIS5 Driver) Import them (I [...]]]></description>
			<content:encoded><![CDATA[<p>When capturing a reference image using VMWare Workstation/Server your WinPE image needs the right nic driver to contact the Deployment Share.</p>
<p>Here is how to obtain and inject these vmware drivers into your WinPE boot image.</p>
<p>First download the drivers from <a title="AMD PCNet family NDIS5 Windows driver version 4.51" href="http://the-d-spot.org/files/V4.51.zip">VMWare </a><em>(link updated Sept 2010</em>). (PCnet Family network adapter, NDIS5 Driver)</p>
<p>Import them (I used \WinXP_SignedDriver\netamd.inf, pcntpci5.cat and PCNTPCI5.sys) into your deployment share:</p>
<p><a href="http://www.the-d-spot.org/wordpress/wp-content/uploads/mdtwinpevmwaredrv.png"><img style="display: inline; border: 0px;" title="MDT 2010 WinPE drivers" src="http://www.the-d-spot.org/wordpress/wp-content/uploads/mdtwinpevmwaredrv_thumb.png" border="0" alt="MDT 2010 WinPE drivers" width="244" height="112" /></a></p>
<p>Make sure drivers are injected into your WinPE images:</p>
<p><a href="http://www.the-d-spot.org/wordpress/wp-content/uploads/mdtinjectdriverswinpe.png"><img style="display: inline; border: 0px;" title="MDT 2010 - Inject drivers into WinPE" src="http://www.the-d-spot.org/wordpress/wp-content/uploads/mdtinjectdriverswinpe_thumb.png" border="0" alt="MDT 2010 - Inject drivers into WinPE" width="244" height="176" /></a></p>
<p>And rebuild the Deployment Share, to regenerate the WinPE boot images.</p>
<p><a href="http://www.the-d-spot.org/wordpress/wp-content/uploads/mdtupdatedeploymentshare.png"><img style="display: inline; border: 0px;" title="MDT 2010 Update Deployment Share" src="http://www.the-d-spot.org/wordpress/wp-content/uploads/mdtupdatedeploymentshare_thumb.png" border="0" alt="MDT 2010 Update Deployment Share" width="244" height="167" /></a></p>
<p>Last step: import the new WinPE boot images into your PXE boot server. (or rewrite your bootcd’s with the WinPE ISO file)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.the-d-spot.org/wordpress/2010/01/20/vmware-network-drivers-for-winpe-3-0/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
	</channel>
</rss>

