Installing VMware NIC/Mouse/SCSI, ETC drivers into PE 2.0 for BDD

haplopeart

I was looking for an answer to this issue recently, but no where did I find a
completely clear and coherent procedure spelled out step by step. Having now
got it working I offer up the step-by-step process of making it work.

1. You must have the WAIK installed on the machine, lots of writeups are
missing that step, I do(did) have it but some people seem to not know it
needs to be there.

2. Open the WAIK (Microsoft Windows AIK) program group on the start menu and
open a PE command Prompt.

3. type "copype x86 d:\winpe_x86" at the command prompt hit ENTER.
(This could have also been "copype amd64 d:\winpe_amd64"...and d:
should be whatever is correct for your build machine)
4. type "imagex /mountrw d:\winpe_x86\iso\sources\boot.wim 1
d:\winpe_x86\mount" hit ENTER
This step is vital and one alot of people seem to mess up or get confused
by, in many instances I have seen people mount the winpe.wim file from
d:\winpe_x86 or from d:\distribution\operating systems\winpe20-x86 (or
whatever you called the winpe directory when you imported it into the BDD as
an OS). This is incorrect you want to mount and modify the boot.wim this is
the template for winpe.wim.

5. Now you are ready to import drivers, install packages, and generally
modify the pe startup environment.
a. Install drivers with the command:
"peimg /inf=d:\Driverwork\vmdrivers\Drivers\vmxnet\win2k\v mxnet.inf
d:\winpe_x86\mount\Windows" you will need to repeat this procedure for each
driver you are loading modifing the path to point to each .inf correctly. At
Minimum I suggest loading both VMware NIC .inf files, you might want the scsi
and Mouse drivers as well.

b. If you are adding packages to PE now is the time I usually just add them
all. So: "peimg /install=*Package* d:\winpe_x86\mount\Windows"

c. If you are adding other programs and files, copy them into the PE
directory ex. "copy “d:\program files\bdd2007\Tools\x86\imagex.exe�
d:\winpe_x86\mount\windows"

6. Prep the .wim file for use type "peimg /prep d:\winpe_x86mount\Windows"
You will get a question that you will need to answer by typing "yes", if can
be avoided with a /f switch but I like the last chance to bail out.

7. Commit the changes to the .wim type "imagex /unmount /commit
d:\winpe_x86\mount"

8. Now copy the resulting boot.wim file from d:\winpe_x86\iso\sources to
"d:\distribution\operating systems\winpe20-x86" (or whatever you called the
winpe directory when you imported it into the BDD as an OS) delete or move
the winpe.wim file, finally rename boot.wim to winpe.wim

9. If you are also rebuilding the amd64 PE repeat the above procedure for
amd64.

10. Do a full deployment point update for the Lab deployment point, and then
any other deployment points you are using after the lab one is complete

Johan Arwidmark

You can also do this:

1. Add the vmware drivers to Out-of-box drivers using the deployment
workbench

2. Update the Deployment point...

3. Voila, all drivers injected into LiteTouchPE_x86.wim (winpe 2.0)

Regards

Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com


On Wed, 19 Sep 2007 10:12:01 -0700, haplopeart
<haplopeart@discussions.microsoft.com> wrote:

>I was looking for an answer to this issue recently, but no where did I find a
>completely clear and coherent procedure spelled out step by step. Having now
>got it working I offer up the step-by-step process of making it work.
>
>1. You must have the WAIK installed on the machine, lots of writeups are
>missing that step, I do(did) have it but some people seem to not know it
>needs to be there.
>
>2. Open the WAIK (Microsoft Windows AIK) program group on the start menu and
>open a PE command Prompt.
>
>3. type "copype x86 d:\winpe_x86" at the command prompt hit ENTER.
>(This could have also been "copype amd64 d:\winpe_amd64"...and d:
>should be whatever is correct for your build machine)
>4. type "imagex /mountrw d:\winpe_x86\iso\sources\boot.wim 1
>d:\winpe_x86\mount" hit ENTER
>This step is vital and one alot of people seem to mess up or get confused
>by, in many instances I have seen people mount the winpe.wim file from
>d:\winpe_x86 or from d:\distribution\operating systems\winpe20-x86 (or
>whatever you called the winpe directory when you imported it into the BDD as
>an OS). This is incorrect you want to mount and modify the boot.wim this is
>the template for winpe.wim.
>
>5. Now you are ready to import drivers, install packages, and generally
>modify the pe startup environment.
>a. Install drivers with the command:
>"peimg /inf=d:\Driverwork\vmdrivers\Drivers\vmxnet\win2k\v mxnet.inf
>d:\winpe_x86\mount\Windows" you will need to repeat this procedure for each
>driver you are loading modifing the path to point to each .inf correctly. At
>Minimum I suggest loading both VMware NIC .inf files, you might want the scsi
>and Mouse drivers as well.
>
>b. If you are adding packages to PE now is the time I usually just add them
>all. So: "peimg /install=*Package* d:\winpe_x86\mount\Windows"
>
>c. If you are adding other programs and files, copy them into the PE
>directory ex. "copy “d:\program files\bdd2007\Tools\x86\imagex.exe”
>d:\winpe_x86\mount\windows"
>
>6. Prep the .wim file for use type "peimg /prep d:\winpe_x86mount\Windows"
>You will get a question that you will need to answer by typing "yes", if can
>be avoided with a /f switch but I like the last chance to bail out.
>
>7. Commit the changes to the .wim type "imagex /unmount /commit
>d:\winpe_x86\mount"
>
>8. Now copy the resulting boot.wim file from d:\winpe_x86\iso\sources to
>"d:\distribution\operating systems\winpe20-x86" (or whatever you called the
>winpe directory when you imported it into the BDD as an OS) delete or move
>the winpe.wim file, finally rename boot.wim to winpe.wim
>
>9. If you are also rebuilding the amd64 PE repeat the above procedure for
>amd64.
>
>10. Do a full deployment point update for the Lab deployment point, and then
>any other deployment points you are using after the lab one is complete

haplopeart

We (Myself, My Team and the MS Consultants that came on site a few months
ago) have had trouble with the injection of the NIC drivers for VMware into
PE through out of Box drivers which is what lead to the above procedure.

"Johan Arwidmark" wrote:

> You can also do this:
>
> 1. Add the vmware drivers to Out-of-box drivers using the deployment
> workbench
>
> 2. Update the Deployment point...
>
> 3. Voila, all drivers injected into LiteTouchPE_x86.wim (winpe 2.0)
>
> Regards
>
> Johan Arwidmark
> Microsoft MVP - Setup / Deployment
> http://www.deployvista.com
>
>
> On Wed, 19 Sep 2007 10:12:01 -0700, haplopeart
> <haplopeart@discussions.microsoft.com> wrote:
>
> >I was looking for an answer to this issue recently, but no where did I find a
> >completely clear and coherent procedure spelled out step by step. Having now
> >got it working I offer up the step-by-step process of making it work.
> >
> >1. You must have the WAIK installed on the machine, lots of writeups are
> >missing that step, I do(did) have it but some people seem to not know it
> >needs to be there.
> >
> >2. Open the WAIK (Microsoft Windows AIK) program group on the start menu and
> >open a PE command Prompt.
> >
> >3. type "copype x86 d:\winpe_x86" at the command prompt hit ENTER.
> >(This could have also been "copype amd64 d:\winpe_amd64"...and d:
> >should be whatever is correct for your build machine)
> >4. type "imagex /mountrw d:\winpe_x86\iso\sources\boot.wim 1
> >d:\winpe_x86\mount" hit ENTER
> >This step is vital and one alot of people seem to mess up or get confused
> >by, in many instances I have seen people mount the winpe.wim file from
> >d:\winpe_x86 or from d:\distribution\operating systems\winpe20-x86 (or
> >whatever you called the winpe directory when you imported it into the BDD as
> >an OS). This is incorrect you want to mount and modify the boot.wim this is
> >the template for winpe.wim.
> >
> >5. Now you are ready to import drivers, install packages, and generally
> >modify the pe startup environment.
> >a. Install drivers with the command:
> >"peimg /inf=d:\Driverwork\vmdrivers\Drivers\vmxnet\win2k\v mxnet.inf
> >d:\winpe_x86\mount\Windows" you will need to repeat this procedure for each
> >driver you are loading modifing the path to point to each .inf correctly. At
> >Minimum I suggest loading both VMware NIC .inf files, you might want the scsi
> >and Mouse drivers as well.
> >
> >b. If you are adding packages to PE now is the time I usually just add them
> >all. So: "peimg /install=*Package* d:\winpe_x86\mount\Windows"
> >
> >c. If you are adding other programs and files, copy them into the PE
> >directory ex. "copy “d:\program files\bdd2007\Tools\x86\imagex.exe�
> >d:\winpe_x86\mount\windows"
> >
> >6. Prep the .wim file for use type "peimg /prep d:\winpe_x86mount\Windows"
> >You will get a question that you will need to answer by typing "yes", if can
> >be avoided with a /f switch but I like the last chance to bail out.
> >
> >7. Commit the changes to the .wim type "imagex /unmount /commit
> >d:\winpe_x86\mount"
> >
> >8. Now copy the resulting boot.wim file from d:\winpe_x86\iso\sources to
> >"d:\distribution\operating systems\winpe20-x86" (or whatever you called the
> >winpe directory when you imported it into the BDD as an OS) delete or move
> >the winpe.wim file, finally rename boot.wim to winpe.wim
> >
> >9. If you are also rebuilding the amd64 PE repeat the above procedure for
> >amd64.
> >
> >10. Do a full deployment point update for the Lab deployment point, and then
> >any other deployment points you are using after the lab one is complete
>

Johan Arwidmark

I guess I have been lucky with my vmware's then

Point is that deployment workbench actually runs peimg... it just
act's as a frontend...

As a best practice group all winpe drivers into a drivers group and
configure the deployment point properities to only use the winpe
drivers.

The problems in general starts when mixing 32-bit and 64-bit drivers
in the workbench for winpe, then you may need to revert to the manual
method...

Regards

Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com


On Wed, 19 Sep 2007 12:18:03 -0700, haplopeart
<haplopeart@discussions.microsoft.com> wrote:

>We (Myself, My Team and the MS Consultants that came on site a few months
>ago) have had trouble with the injection of the NIC drivers for VMware into
>PE through out of Box drivers which is what lead to the above procedure.
>
>"Johan Arwidmark" wrote:
>
>> You can also do this:
>>
>> 1. Add the vmware drivers to Out-of-box drivers using the deployment
>> workbench
>>
>> 2. Update the Deployment point...
>>
>> 3. Voila, all drivers injected into LiteTouchPE_x86.wim (winpe 2.0)
>>
>> Regards
>>
>> Johan Arwidmark
>> Microsoft MVP - Setup / Deployment
>> http://www.deployvista.com
>>
>>
>> On Wed, 19 Sep 2007 10:12:01 -0700, haplopeart
>> <haplopeart@discussions.microsoft.com> wrote:
>>
>> >I was looking for an answer to this issue recently, but no where did I find a
>> >completely clear and coherent procedure spelled out step by step. Having now
>> >got it working I offer up the step-by-step process of making it work.
>> >
>> >1. You must have the WAIK installed on the machine, lots of writeups are
>> >missing that step, I do(did) have it but some people seem to not know it
>> >needs to be there.
>> >
>> >2. Open the WAIK (Microsoft Windows AIK) program group on the start menu and
>> >open a PE command Prompt.
>> >
>> >3. type "copype x86 d:\winpe_x86" at the command prompt hit ENTER.
>> >(This could have also been "copype amd64 d:\winpe_amd64"...and d:
>> >should be whatever is correct for your build machine)
>> >4. type "imagex /mountrw d:\winpe_x86\iso\sources\boot.wim 1
>> >d:\winpe_x86\mount" hit ENTER
>> >This step is vital and one alot of people seem to mess up or get confused
>> >by, in many instances I have seen people mount the winpe.wim file from
>> >d:\winpe_x86 or from d:\distribution\operating systems\winpe20-x86 (or
>> >whatever you called the winpe directory when you imported it into the BDD as
>> >an OS). This is incorrect you want to mount and modify the boot.wim this is
>> >the template for winpe.wim.
>> >
>> >5. Now you are ready to import drivers, install packages, and generally
>> >modify the pe startup environment.
>> >a. Install drivers with the command:
>> >"peimg /inf=d:\Driverwork\vmdrivers\Drivers\vmxnet\win2k\v mxnet.inf
>> >d:\winpe_x86\mount\Windows" you will need to repeat this procedure for each
>> >driver you are loading modifing the path to point to each .inf correctly. At
>> >Minimum I suggest loading both VMware NIC .inf files, you might want the scsi
>> >and Mouse drivers as well.
>> >
>> >b. If you are adding packages to PE now is the time I usually just add them
>> >all. So: "peimg /install=*Package* d:\winpe_x86\mount\Windows"
>> >
>> >c. If you are adding other programs and files, copy them into the PE
>> >directory ex. "copy “d:\program files\bdd2007\Tools\x86\imagex.exe”
>> >d:\winpe_x86\mount\windows"
>> >
>> >6. Prep the .wim file for use type "peimg /prep d:\winpe_x86mount\Windows"
>> >You will get a question that you will need to answer by typing "yes", if can
>> >be avoided with a /f switch but I like the last chance to bail out.
>> >
>> >7. Commit the changes to the .wim type "imagex /unmount /commit
>> >d:\winpe_x86\mount"
>> >
>> >8. Now copy the resulting boot.wim file from d:\winpe_x86\iso\sources to
>> >"d:\distribution\operating systems\winpe20-x86" (or whatever you called the
>> >winpe directory when you imported it into the BDD as an OS) delete or move
>> >the winpe.wim file, finally rename boot.wim to winpe.wim
>> >
>> >9. If you are also rebuilding the amd64 PE repeat the above procedure for
>> >amd64.
>> >
>> >10. Do a full deployment point update for the Lab deployment point, and then
>> >any other deployment points you are using after the lab one is complete
>>

Jacob

One thing I did notice about the vmware drivers was that when I added all the
vmware drivers to Out-of-Box drivers they didn't work. When I just added the
network driver it worked perfectly. Strange!
--
**********************
Jacob Hodges
http://blog.project84.net



"Johan Arwidmark" wrote:

> I guess I have been lucky with my vmware's then
>
> Point is that deployment workbench actually runs peimg... it just
> act's as a frontend...
>
> As a best practice group all winpe drivers into a drivers group and
> configure the deployment point properities to only use the winpe
> drivers.
>
> The problems in general starts when mixing 32-bit and 64-bit drivers
> in the workbench for winpe, then you may need to revert to the manual
> method...
>
> Regards
>
> Johan Arwidmark
> Microsoft MVP - Setup / Deployment
> http://www.deployvista.com
>
>
> On Wed, 19 Sep 2007 12:18:03 -0700, haplopeart
> <haplopeart@discussions.microsoft.com> wrote:
>
> >We (Myself, My Team and the MS Consultants that came on site a few months
> >ago) have had trouble with the injection of the NIC drivers for VMware into
> >PE through out of Box drivers which is what lead to the above procedure.
> >
> >"Johan Arwidmark" wrote:
> >
> >> You can also do this:
> >>
> >> 1. Add the vmware drivers to Out-of-box drivers using the deployment
> >> workbench
> >>
> >> 2. Update the Deployment point...
> >>
> >> 3. Voila, all drivers injected into LiteTouchPE_x86.wim (winpe 2.0)
> >>
> >> Regards
> >>
> >> Johan Arwidmark
> >> Microsoft MVP - Setup / Deployment
> >> http://www.deployvista.com
> >>
> >>
> >> On Wed, 19 Sep 2007 10:12:01 -0700, haplopeart
> >> <haplopeart@discussions.microsoft.com> wrote:
> >>
> >> >I was looking for an answer to this issue recently, but no where did I find a
> >> >completely clear and coherent procedure spelled out step by step. Having now
> >> >got it working I offer up the step-by-step process of making it work.
> >> >
> >> >1. You must have the WAIK installed on the machine, lots of writeups are
> >> >missing that step, I do(did) have it but some people seem to not know it
> >> >needs to be there.
> >> >
> >> >2. Open the WAIK (Microsoft Windows AIK) program group on the start menu and
> >> >open a PE command Prompt.
> >> >
> >> >3. type "copype x86 d:\winpe_x86" at the command prompt hit ENTER.
> >> >(This could have also been "copype amd64 d:\winpe_amd64"...and d:
> >> >should be whatever is correct for your build machine)
> >> >4. type "imagex /mountrw d:\winpe_x86\iso\sources\boot.wim 1
> >> >d:\winpe_x86\mount" hit ENTER
> >> >This step is vital and one alot of people seem to mess up or get confused
> >> >by, in many instances I have seen people mount the winpe.wim file from
> >> >d:\winpe_x86 or from d:\distribution\operating systems\winpe20-x86 (or
> >> >whatever you called the winpe directory when you imported it into the BDD as
> >> >an OS). This is incorrect you want to mount and modify the boot.wim this is
> >> >the template for winpe.wim.
> >> >
> >> >5. Now you are ready to import drivers, install packages, and generally
> >> >modify the pe startup environment.
> >> >a. Install drivers with the command:
> >> >"peimg /inf=d:\Driverwork\vmdrivers\Drivers\vmxnet\win2k\v mxnet.inf
> >> >d:\winpe_x86\mount\Windows" you will need to repeat this procedure for each
> >> >driver you are loading modifing the path to point to each .inf correctly. At
> >> >Minimum I suggest loading both VMware NIC .inf files, you might want the scsi
> >> >and Mouse drivers as well.
> >> >
> >> >b. If you are adding packages to PE now is the time I usually just add them
> >> >all. So: "peimg /install=*Package* d:\winpe_x86\mount\Windows"
> >> >
> >> >c. If you are adding other programs and files, copy them into the PE
> >> >directory ex. "copy “d:\program files\bdd2007\Tools\x86\imagex.exe�
> >> >d:\winpe_x86\mount\windows"
> >> >
> >> >6. Prep the .wim file for use type "peimg /prep d:\winpe_x86mount\Windows"
> >> >You will get a question that you will need to answer by typing "yes", if can
> >> >be avoided with a /f switch but I like the last chance to bail out.
> >> >
> >> >7. Commit the changes to the .wim type "imagex /unmount /commit
> >> >d:\winpe_x86\mount"
> >> >
> >> >8. Now copy the resulting boot.wim file from d:\winpe_x86\iso\sources to
> >> >"d:\distribution\operating systems\winpe20-x86" (or whatever you called the
> >> >winpe directory when you imported it into the BDD as an OS) delete or move
> >> >the winpe.wim file, finally rename boot.wim to winpe.wim
> >> >
> >> >9. If you are also rebuilding the amd64 PE repeat the above procedure for
> >> >amd64.
> >> >
> >> >10. Do a full deployment point update for the Lab deployment point, and then
> >> >any other deployment points you are using after the lab one is complete
> >>
>