|T O P I C R E V I E W
||Posted - 05/04/2012 : 4:02:21 PM
I have been dealing with a problem I hope someone can answer.
I wanted to load Win 7 on an old computer I had, so I buit a
WinPE image, and in it I had installed the nic drivers using
/Add-Drivers /Driver:F:\Lan\WinXP\NetOEM.Inf /ForceUnsigned
This worked. I was able to boot to the CD and install Win 7
from a network share.
Now, I decide to use WDS. I install the system and it appears
to work, but as i am booting the WinPE portion of the install,
a message pops up saying I do not have the necessary network
So I modify the image in:
G:\RemoteInstall\Boot\X86\Images\P4SP_Boot.Wim and try again.
(Note: The drivers are for a P4SP-MX Asus motherboard).
I can see the image being copied across to the computer,
but I get the same message, and when I look in
X:\Windows\INF, I do not see the driver I installed.
I am lost for an answer. I can modify the image and
build a CD which works, but I am unable to do the
same in WDS. Just a note, I used a batch file to
modify both images, I just changed the name of the
Thanks for your help.
|5 L A T E S T R E P L I E S (Newest First)
||Posted - 05/18/2012 : 06:09:11 AM
There is plenty of docs on Microsoft TechNet, but again, you should not being using plain vanilla WDS (without MDT integration) for Windows Deployments....
||Posted - 05/15/2012 : 08:26:16 AM
I finally solved my problem. I did not realize that within
my .Wim file, there are two images. One is a boot image the other
is an install image. I was modifying the boot image, and not the
I suppose I thought I understood images fairly well, but this
makes me realize I need to investigate the install process a
little more. Is there a document online that explains in detail
the PXE boot process and how files on the WDS server are used?
I feel I do not understand the process well enough.
Thanks again for your help.
||Posted - 05/11/2012 : 3:55:18 PM
OEM*.inf files will be created in the C:\Windows\Inf folder
||Posted - 05/11/2012 : 11:26:27 AM
Sorry to get back so late. I watched the videos, and
I can see were MDT will help.
I still wonder where the OEM0.Inf file went to after
I added my driver using DISM.
Also, because there was a *.sys file that needed
to reside with the Oem.Inf file, the driver install
wouldn't work anyway.
||Posted - 05/07/2012 : 2:19:23 PM
Don't use WDS for deploying your operating system images. Integrate WDS with MDT 2012 so you get a good deployment solution.
Check these videos for MDT 2010, they are still valid for MDT 2012