MDT workbench - drivers - x86 and x64 - will I have conflicts?

[James]

Hello,

wds/mdt 2008 infrastructure supporting about a dozen different hardware
models (mosty HP Proliant servers). I intend on making only one image per
operating system version that will work on all the servers... eg. one
windows 2003 standard image, one windows 2003 enterprise image, etc... and
also one image for each respective 64 bit version of the operating system.
Right now I'm downloading all the drivers (real fun) and I recall coming
across a post somewhere where someone was having an issue with x86 and x64
drivers... If I remember correctly they were adding the x86 version of the
drivers to the deplyment workbench followd by the x64 version of the drivers
and the x64 version was overwritting the x86 files... due do some files
between the x86 and x64 versions having the same filenames?

I have not started adding the drivers to the workbench yet and wanted to
find out about this before I do... anyone know? what happens? precautions?
links to procedure to follow to avoid this issue? is it even an issue
anymore with MDT 2008 Update 1?

any input on this would be greatly appreciated.

[unknown]

In update 1 you can tag the device drivers for a specific platform...
that removes most issues with x64 vs x86 drivers...

For a 100 percent working solution... check this article

They call me a control-freak... a drivers tale...
http://www.deployvista.com/Home/tabid/36/EntryID/72/language/en-US/Default.aspx

Regards

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

Post by James
Hello,
wds/mdt 2008 infrastructure supporting about a dozen different hardware
models (mosty HP Proliant servers). I intend on making only one image per
operating system version that will work on all the servers... eg. one
windows 2003 standard image, one windows 2003 enterprise image, etc... and
also one image for each respective 64 bit version of the operating system.
Right now I'm downloading all the drivers (real fun) and I recall coming
across a post somewhere where someone was having an issue with x86 and x64
drivers... If I remember correctly they were adding the x86 version of the
drivers to the deplyment workbench followd by the x64 version of the drivers
and the x64 version was overwritting the x86 files... due do some files
between the x86 and x64 versions having the same filenames?
I have not started adding the drivers to the workbench yet and wanted to
find out about this before I do... anyone know? what happens? precautions?
links to procedure to follow to avoid this issue? is it even an issue
anymore with MDT 2008 Update 1?
any input on this would be greatly appreciated.

[James]

thanks, I'll check it out.

Post by unknown
In update 1 you can tag the device drivers for a specific platform...
that removes most issues with x64 vs x86 drivers...
For a 100 percent working solution... check this article
They call me a control-freak... a drivers tale...
http://www.deployvista.com/Home/tabid/36/EntryID/72/language/en-US/Default.aspx
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by James
Hello,
wds/mdt 2008 infrastructure supporting about a dozen different hardware
models (mosty HP Proliant servers). I intend on making only one image per
operating system version that will work on all the servers... eg. one
windows 2003 standard image, one windows 2003 enterprise image, etc... and
also one image for each respective 64 bit version of the operating system.
Right now I'm downloading all the drivers (real fun) and I recall coming
across a post somewhere where someone was having an issue with x86 and x64
drivers... If I remember correctly they were adding the x86 version of the
drivers to the deplyment workbench followd by the x64 version of the drivers
and the x64 version was overwritting the x86 files... due do some files
between the x86 and x64 versions having the same filenames?
I have not started adding the drivers to the workbench yet and wanted to
find out about this before I do... anyone know? what happens? precautions?
links to procedure to follow to avoid this issue? is it even an issue
anymore with MDT 2008 Update 1?
any input on this would be greatly appreciated.

[James]

Hi Johan,

Could you confirm for me that I understand the following correctly:?

out of box drivers:

1) they are added to the PE image (can be filtered by group) to support the
pe phases of deployment (network and mass storage drivers) and therefore you
need the vista/server 2008 version of those drivers...

2) the mass storage drivers here are also used for driver injection, which
based on pnp id's are copied to the machine being imaged during sysprep
before the image is captured... so you also need the correct driver version
to match the OS you are capturing.. such server 2k3

does this sound like I have it here?

Post by unknown
In update 1 you can tag the device drivers for a specific platform...
that removes most issues with x64 vs x86 drivers...
For a 100 percent working solution... check this article
They call me a control-freak... a drivers tale...
http://www.deployvista.com/Home/tabid/36/EntryID/72/language/en-US/Default.aspx
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by James
Hello,
wds/mdt 2008 infrastructure supporting about a dozen different hardware
models (mosty HP Proliant servers). I intend on making only one image per
operating system version that will work on all the servers... eg. one
windows 2003 standard image, one windows 2003 enterprise image, etc... and
also one image for each respective 64 bit version of the operating system.
Right now I'm downloading all the drivers (real fun) and I recall coming
across a post somewhere where someone was having an issue with x86 and x64
drivers... If I remember correctly they were adding the x86 version of the
drivers to the deplyment workbench followd by the x64 version of the drivers
and the x64 version was overwritting the x86 files... due do some files
between the x86 and x64 versions having the same filenames?
I have not started adding the drivers to the workbench yet and wanted to
find out about this before I do... anyone know? what happens? precautions?
links to procedure to follow to avoid this issue? is it even an issue
anymore with MDT 2008 Update 1?
any input on this would be greatly appreciated.

[unknown]

1. Close.... You should use Vista Drivers in the first hand... but
normally XP drivers works fine as welll

2. Depends, if you deploy vista or srv 2008, MDT will inject even
storage drivers on the fly... if using XP or 2003, they need to be
present in the image. there is a built'in action that will help you
populate sysprep.inf... I don't like it one bit, I prefer to edit
sysprep.inf manually, and disable the action...

Regards

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

Post by James
Hi Johan,
Could you confirm for me that I understand the following correctly:?
1) they are added to the PE image (can be filtered by group) to support the
pe phases of deployment (network and mass storage drivers) and therefore you
need the vista/server 2008 version of those drivers...
2) the mass storage drivers here are also used for driver injection, which
based on pnp id's are copied to the machine being imaged during sysprep
before the image is captured... so you also need the correct driver version
to match the OS you are capturing.. such server 2k3
does this sound like I have it here?

Post by unknown
In update 1 you can tag the device drivers for a specific platform...
that removes most issues with x64 vs x86 drivers...
For a 100 percent working solution... check this article
They call me a control-freak... a drivers tale...
http://www.deployvista.com/Home/tabid/36/EntryID/72/language/en-US/Default.aspx
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by James
Hello,
wds/mdt 2008 infrastructure supporting about a dozen different hardware
models (mosty HP Proliant servers). I intend on making only one image per
operating system version that will work on all the servers... eg. one
windows 2003 standard image, one windows 2003 enterprise image, etc... and
also one image for each respective 64 bit version of the operating system.
Right now I'm downloading all the drivers (real fun) and I recall coming
across a post somewhere where someone was having an issue with x86 and x64
drivers... If I remember correctly they were adding the x86 version of the
drivers to the deplyment workbench followd by the x64 version of the drivers
and the x64 version was overwritting the x86 files... due do some files
between the x86 and x64 versions having the same filenames?
I have not started adding the drivers to the workbench yet and wanted to
find out about this before I do... anyone know? what happens? precautions?
links to procedure to follow to avoid this issue? is it even an issue
anymore with MDT 2008 Update 1?
any input on this would be greatly appreciated.

[James]

thanks Johan,

interesting point on 2: what kind of issues have you had with xp/2k3 driver
injection (sysprep.inf edit part)?

oh and on 1: when you said "you should use Vista drivers in the first hand"
do you mean as opposed to 2k8? My deployment server is 2k8 and I'm
deploying 2k3 and 2k8 servers only, no xp or vista. I was under the
impression this pe version was vista/2k8, meaning vista and 2k8 were
equivilent as far as this PE goes... same cores, so to speak? Thus far in a
test setup with only one target server to test deployments it has worked and
I never supplied any vista source files, only 2k8 (and 2k3). I'm now moving
to a production environment where supporting all the various hardware models
will be required... and thus, time to do the drivers thing.

Post by unknown
1. Close.... You should use Vista Drivers in the first hand... but
normally XP drivers works fine as welll
2. Depends, if you deploy vista or srv 2008, MDT will inject even
storage drivers on the fly... if using XP or 2003, they need to be
present in the image. there is a built'in action that will help you
populate sysprep.inf... I don't like it one bit, I prefer to edit
sysprep.inf manually, and disable the action...
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by James
Hi Johan,
Could you confirm for me that I understand the following correctly:?
1) they are added to the PE image (can be filtered by group) to support the
pe phases of deployment (network and mass storage drivers) and therefore you
need the vista/server 2008 version of those drivers...
2) the mass storage drivers here are also used for driver injection, which
based on pnp id's are copied to the machine being imaged during sysprep
before the image is captured... so you also need the correct driver version
to match the OS you are capturing.. such server 2k3
does this sound like I have it here?

Post by unknown
In update 1 you can tag the device drivers for a specific platform...
that removes most issues with x64 vs x86 drivers...
For a 100 percent working solution... check this article
They call me a control-freak... a drivers tale...
http://www.deployvista.com/Home/tabid/36/EntryID/72/language/en-US/Default.aspx
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by James
Hello,
wds/mdt 2008 infrastructure supporting about a dozen different hardware
models (mosty HP Proliant servers). I intend on making only one image per
operating system version that will work on all the servers... eg. one
windows 2003 standard image, one windows 2003 enterprise image, etc... and
also one image for each respective 64 bit version of the operating system.
Right now I'm downloading all the drivers (real fun) and I recall coming
across a post somewhere where someone was having an issue with x86 and x64
drivers... If I remember correctly they were adding the x86 version of the
drivers to the deplyment workbench followd by the x64 version of the drivers
and the x64 version was overwritting the x86 files... due do some files
between the x86 and x64 versions having the same filenames?
I have not started adding the drivers to the workbench yet and wanted to
find out about this before I do... anyone know? what happens? precautions?
links to procedure to follow to avoid this issue? is it even an issue
anymore with MDT 2008 Update 1?
any input on this would be greatly appreciated.

[unknown]

Put it this way... you will not get a hardware independent image if
you allow MDT to inject all built-in drivers... you will find that
some of the built-in XP ones are conflicting with newer hardware..

Vista and 2008 are using the same driver model, and for WinPE it
doesn't matter as far as drivers goes...

Regards

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

Post by James
thanks Johan,
interesting point on 2: what kind of issues have you had with xp/2k3 driver
injection (sysprep.inf edit part)?
oh and on 1: when you said "you should use Vista drivers in the first hand"
do you mean as opposed to 2k8? My deployment server is 2k8 and I'm
deploying 2k3 and 2k8 servers only, no xp or vista. I was under the
impression this pe version was vista/2k8, meaning vista and 2k8 were
equivilent as far as this PE goes... same cores, so to speak? Thus far in a
test setup with only one target server to test deployments it has worked and
I never supplied any vista source files, only 2k8 (and 2k3). I'm now moving
to a production environment where supporting all the various hardware models
will be required... and thus, time to do the drivers thing.

Post by unknown
1. Close.... You should use Vista Drivers in the first hand... but
normally XP drivers works fine as welll
2. Depends, if you deploy vista or srv 2008, MDT will inject even
storage drivers on the fly... if using XP or 2003, they need to be
present in the image. there is a built'in action that will help you
populate sysprep.inf... I don't like it one bit, I prefer to edit
sysprep.inf manually, and disable the action...
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by James
Hi Johan,
Could you confirm for me that I understand the following correctly:?
1) they are added to the PE image (can be filtered by group) to support the
pe phases of deployment (network and mass storage drivers) and therefore you
need the vista/server 2008 version of those drivers...
2) the mass storage drivers here are also used for driver injection, which
based on pnp id's are copied to the machine being imaged during sysprep
before the image is captured... so you also need the correct driver version
to match the OS you are capturing.. such server 2k3
does this sound like I have it here?

Post by unknown
In update 1 you can tag the device drivers for a specific platform...
that removes most issues with x64 vs x86 drivers...
For a 100 percent working solution... check this article
They call me a control-freak... a drivers tale...
http://www.deployvista.com/Home/tabid/36/EntryID/72/language/en-US/Default.aspx
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by James
Hello,
wds/mdt 2008 infrastructure supporting about a dozen different hardware
models (mosty HP Proliant servers). I intend on making only one image per
operating system version that will work on all the servers... eg. one
windows 2003 standard image, one windows 2003 enterprise image, etc... and
also one image for each respective 64 bit version of the operating system.
Right now I'm downloading all the drivers (real fun) and I recall coming
across a post somewhere where someone was having an issue with x86 and x64
drivers... If I remember correctly they were adding the x86 version of the
drivers to the deplyment workbench followd by the x64 version of the drivers
and the x64 version was overwritting the x86 files... due do some files
between the x86 and x64 versions having the same filenames?
I have not started adding the drivers to the workbench yet and wanted to
find out about this before I do... anyone know? what happens? precautions?
links to procedure to follow to avoid this issue? is it even an issue
anymore with MDT 2008 Update 1?
any input on this would be greatly appreciated.

[Erik Droszcz]

Johan, I am curious about when the drivers in MDT Out-of-Box Drivers are used
(when deploying XP).

For example I need to add NIC drivers to WinPE so it will be able to connect
to the deployment share. Since the WinPE used in MDT is build on Vista you
should use the Vista NIC drivers, right?

But what happens when LTI has deployed the Windows XP WIM-image and boots
into Windows XP? Then LTI needs to create a new connection to the deployment
share and then I need the NIC drivers for XP. Should I add both the Vista and
XP NIC drivers to the Out-of-Box Drivers to make sure it will work?

Or did I get this all mixed up :) ?

Regards
Erik

Post by unknown
1. Close.... You should use Vista Drivers in the first hand... but
normally XP drivers works fine as welll
2. Depends, if you deploy vista or srv 2008, MDT will inject even
storage drivers on the fly... if using XP or 2003, they need to be
present in the image. there is a built'in action that will help you
populate sysprep.inf... I don't like it one bit, I prefer to edit
sysprep.inf manually, and disable the action...
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by James
Hi Johan,
Could you confirm for me that I understand the following correctly:?
1) they are added to the PE image (can be filtered by group) to support the
pe phases of deployment (network and mass storage drivers) and therefore you
need the vista/server 2008 version of those drivers...
2) the mass storage drivers here are also used for driver injection, which
based on pnp id's are copied to the machine being imaged during sysprep
before the image is captured... so you also need the correct driver version
to match the OS you are capturing.. such server 2k3
does this sound like I have it here?

Post by unknown
In update 1 you can tag the device drivers for a specific platform...
that removes most issues with x64 vs x86 drivers...
For a 100 percent working solution... check this article
They call me a control-freak... a drivers tale...
http://www.deployvista.com/Home/tabid/36/EntryID/72/language/en-US/Default.aspx
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by James
Hello,
wds/mdt 2008 infrastructure supporting about a dozen different hardware
models (mosty HP Proliant servers). I intend on making only one image per
operating system version that will work on all the servers... eg. one
windows 2003 standard image, one windows 2003 enterprise image, etc... and
also one image for each respective 64 bit version of the operating system.
Right now I'm downloading all the drivers (real fun) and I recall coming
across a post somewhere where someone was having an issue with x86 and x64
drivers... If I remember correctly they were adding the x86 version of the
drivers to the deplyment workbench followd by the x64 version of the drivers
and the x64 version was overwritting the x86 files... due do some files
between the x86 and x64 versions having the same filenames?
I have not started adding the drivers to the workbench yet and wanted to
find out about this before I do... anyone know? what happens? precautions?
links to procedure to follow to avoid this issue? is it even an issue
anymore with MDT 2008 Update 1?
any input on this would be greatly appreciated.

[unknown]

Yes, the out-of-box drivers will be used even when deploying legacy
os's like XP or srv2003.

I recommend you to create a WnPE drivers group, and add only winpe
drivers to that one. the same winpe image is used no matter what os
you deploy....

You should also add the xp drivers to the workbench, but not add them
to the winpe drivers group (unless that's the only driver for that
nic)

Regards

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


On Wed, 5 Nov 2008 12:30:00 -0800, Erik Droszcz

Post by Erik Droszcz
Johan, I am curious about when the drivers in MDT Out-of-Box Drivers are used
(when deploying XP).
For example I need to add NIC drivers to WinPE so it will be able to connect
to the deployment share. Since the WinPE used in MDT is build on Vista you
should use the Vista NIC drivers, right?
But what happens when LTI has deployed the Windows XP WIM-image and boots
into Windows XP? Then LTI needs to create a new connection to the deployment
share and then I need the NIC drivers for XP. Should I add both the Vista and
XP NIC drivers to the Out-of-Box Drivers to make sure it will work?
Or did I get this all mixed up :) ?
Regards
Erik

Post by unknown
1. Close.... You should use Vista Drivers in the first hand... but
normally XP drivers works fine as welll
2. Depends, if you deploy vista or srv 2008, MDT will inject even
storage drivers on the fly... if using XP or 2003, they need to be
present in the image. there is a built'in action that will help you
populate sysprep.inf... I don't like it one bit, I prefer to edit
sysprep.inf manually, and disable the action...
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by James
Hi Johan,
Could you confirm for me that I understand the following correctly:?
1) they are added to the PE image (can be filtered by group) to support the
pe phases of deployment (network and mass storage drivers) and therefore you
need the vista/server 2008 version of those drivers...
2) the mass storage drivers here are also used for driver injection, which
based on pnp id's are copied to the machine being imaged during sysprep
before the image is captured... so you also need the correct driver version
to match the OS you are capturing.. such server 2k3
does this sound like I have it here?

Post by unknown
In update 1 you can tag the device drivers for a specific platform...
that removes most issues with x64 vs x86 drivers...
For a 100 percent working solution... check this article
They call me a control-freak... a drivers tale...
http://www.deployvista.com/Home/tabid/36/EntryID/72/language/en-US/Default.aspx
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by James
Hello,
wds/mdt 2008 infrastructure supporting about a dozen different hardware
models (mosty HP Proliant servers). I intend on making only one image per
operating system version that will work on all the servers... eg. one
windows 2003 standard image, one windows 2003 enterprise image, etc... and
also one image for each respective 64 bit version of the operating system.
Right now I'm downloading all the drivers (real fun) and I recall coming
across a post somewhere where someone was having an issue with x86 and x64
drivers... If I remember correctly they were adding the x86 version of the
drivers to the deplyment workbench followd by the x64 version of the drivers
and the x64 version was overwritting the x86 files... due do some files
between the x86 and x64 versions having the same filenames?
I have not started adding the drivers to the workbench yet and wanted to
find out about this before I do... anyone know? what happens? precautions?
links to procedure to follow to avoid this issue? is it even an issue
anymore with MDT 2008 Update 1?
any input on this would be greatly appreciated.

[Erik Droszcz]

Just to see if I got this straight...

I create a driver group called WinPE . In that group I place Vista NIC
drivers for the models I need to support. Under the Windows PE properties tab
for my deployment point I select the WinPE driver group for driver injection.

I guess this should be enough for the WinPE part of the deployment?

Once WinXP boots, what drivers will be used then? Will it look in Out-of-Box
Drivers for _all_ added drivers, regardless of what group they belong to? If
that is true, would it be OK to add another driver group called 'XP NIC
Drivers' and add the XP NIC drivers to that group?

Is it during the XP Mini Setup the XP NIC drivers will be installed?

I do have MDT deployment solution up and running. But I think there are many
things I can improve it. And I though one thing to start with would be how I
manage drivers :)

// Erik

Post by unknown
Yes, the out-of-box drivers will be used even when deploying legacy
os's like XP or srv2003.
I recommend you to create a WnPE drivers group, and add only winpe
drivers to that one. the same winpe image is used no matter what os
you deploy....
You should also add the xp drivers to the workbench, but not add them
to the winpe drivers group (unless that's the only driver for that
nic)
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com
On Wed, 5 Nov 2008 12:30:00 -0800, Erik Droszcz

Post by Erik Droszcz
Johan, I am curious about when the drivers in MDT Out-of-Box Drivers are used
(when deploying XP).
For example I need to add NIC drivers to WinPE so it will be able to connect
to the deployment share. Since the WinPE used in MDT is build on Vista you
should use the Vista NIC drivers, right?
But what happens when LTI has deployed the Windows XP WIM-image and boots
into Windows XP? Then LTI needs to create a new connection to the deployment
share and then I need the NIC drivers for XP. Should I add both the Vista and
XP NIC drivers to the Out-of-Box Drivers to make sure it will work?
Or did I get this all mixed up :) ?
Regards
Erik

Post by unknown
1. Close.... You should use Vista Drivers in the first hand... but
normally XP drivers works fine as welll
2. Depends, if you deploy vista or srv 2008, MDT will inject even
storage drivers on the fly... if using XP or 2003, they need to be
present in the image. there is a built'in action that will help you
populate sysprep.inf... I don't like it one bit, I prefer to edit
sysprep.inf manually, and disable the action...
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by James
Hi Johan,
Could you confirm for me that I understand the following correctly:?
1) they are added to the PE image (can be filtered by group) to support the
pe phases of deployment (network and mass storage drivers) and therefore you
need the vista/server 2008 version of those drivers...
2) the mass storage drivers here are also used for driver injection, which
based on pnp id's are copied to the machine being imaged during sysprep
before the image is captured... so you also need the correct driver version
to match the OS you are capturing.. such server 2k3
does this sound like I have it here?

Post by unknown
In update 1 you can tag the device drivers for a specific platform...
that removes most issues with x64 vs x86 drivers...
For a 100 percent working solution... check this article
They call me a control-freak... a drivers tale...
http://www.deployvista.com/Home/tabid/36/EntryID/72/language/en-US/Default.aspx
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by James
Hello,
wds/mdt 2008 infrastructure supporting about a dozen different hardware
models (mosty HP Proliant servers). I intend on making only one image per
operating system version that will work on all the servers... eg. one
windows 2003 standard image, one windows 2003 enterprise image, etc... and
also one image for each respective 64 bit version of the operating system.
Right now I'm downloading all the drivers (real fun) and I recall coming
across a post somewhere where someone was having an issue with x86 and x64
drivers... If I remember correctly they were adding the x86 version of the
drivers to the deplyment workbench followd by the x64 version of the drivers
and the x64 version was overwritting the x86 files... due do some files
between the x86 and x64 versions having the same filenames?
I have not started adding the drivers to the workbench yet and wanted to
find out about this before I do... anyone know? what happens? precautions?
links to procedure to follow to avoid this issue? is it even an issue
anymore with MDT 2008 Update 1?
any input on this would be greatly appreciated.

[ron]

Johan, nice job! One of the things that makes me uncomfortable with putting
drivers in the Out-of-Box container is that it is easy to loose track of
which ones are which. If I understand your process correctly, wouldn't that
mean, I only have to put drivers in the Out-of-Box container to inject into
building the Litetouch_x86. boot image like NIC drivers so I connect to the
distribution share?

Post by unknown
In update 1 you can tag the device drivers for a specific platform...
that removes most issues with x64 vs x86 drivers...
For a 100 percent working solution... check this article
They call me a control-freak... a drivers tale...
http://www.deployvista.com/Home/tabid/36/EntryID/72/language/en-US/Default.aspx
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by James
Hello,
wds/mdt 2008 infrastructure supporting about a dozen different hardware
models (mosty HP Proliant servers). I intend on making only one image per
operating system version that will work on all the servers... eg. one
windows 2003 standard image, one windows 2003 enterprise image, etc... and
also one image for each respective 64 bit version of the operating system.
Right now I'm downloading all the drivers (real fun) and I recall coming
across a post somewhere where someone was having an issue with x86 and x64
drivers... If I remember correctly they were adding the x86 version of the
drivers to the deplyment workbench followd by the x64 version of the drivers
and the x64 version was overwritting the x86 files... due do some files
between the x86 and x64 versions having the same filenames?
I have not started adding the drivers to the workbench yet and wanted to
find out about this before I do... anyone know? what happens? precautions?
links to procedure to follow to avoid this issue? is it even an issue
anymore with MDT 2008 Update 1?
any input on this would be greatly appreciated.

[unknown]

If you use the driverpaths method, don't use any drivers in out-of-box
drivers.. (well you need to add one, and then remove it for
drivers.xml to be created)

For the Lite Touch WinPE image, I have a script that injects WinPE
drivers afterwards... I do this because it needs to be done anyway,
MDT does not set the "correct" scratchspace in WinPE.

You can also work with driver groups... assign os installations to use
an empty OS Drivers Group, and WinPE to use a WinPE Drivers Group (you
assign your winpe driver to it)

Regards

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

Post by ron
Johan, nice job! One of the things that makes me uncomfortable with putting
drivers in the Out-of-Box container is that it is easy to loose track of
which ones are which. If I understand your process correctly, wouldn't that
mean, I only have to put drivers in the Out-of-Box container to inject into
building the Litetouch_x86. boot image like NIC drivers so I connect to the
distribution share?

Post by unknown
In update 1 you can tag the device drivers for a specific platform...
that removes most issues with x64 vs x86 drivers...
For a 100 percent working solution... check this article
They call me a control-freak... a drivers tale...
http://www.deployvista.com/Home/tabid/36/EntryID/72/language/en-US/Default.aspx
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by James
Hello,
wds/mdt 2008 infrastructure supporting about a dozen different hardware
models (mosty HP Proliant servers). I intend on making only one image per
operating system version that will work on all the servers... eg. one
windows 2003 standard image, one windows 2003 enterprise image, etc... and
also one image for each respective 64 bit version of the operating system.
Right now I'm downloading all the drivers (real fun) and I recall coming
across a post somewhere where someone was having an issue with x86 and x64
drivers... If I remember correctly they were adding the x86 version of the
drivers to the deplyment workbench followd by the x64 version of the drivers
and the x64 version was overwritting the x86 files... due do some files
between the x86 and x64 versions having the same filenames?
I have not started adding the drivers to the workbench yet and wanted to
find out about this before I do... anyone know? what happens? precautions?
links to procedure to follow to avoid this issue? is it even an issue
anymore with MDT 2008 Update 1?
any input on this would be greatly appreciated.

[ron]

Johan, I noticed if I leave drivers in the Out of box container and add the
driverspath1 variable, it seems both areas are grabbed and put into the
C:\Drivers folder. Is that normal?

I have been using your driverspath1 process and I tell you what, there is
nothing that is built into MD to come close to the straightforward process
of creating folders for specific models of hardware. Yea, it takes up more
disk space, but that disadvantage pales in comparison to having the drivers
split out for clarity.

Can the driverspath1 procedure work for mass storage drivers for captured XP
images? Or does it have to be sysprepped with them already on the drive?

It sounds like having an empty drivers group for the deployment and having a
drivers group for the PE building is the way to go. Can you tell me how to
define an empty drivers group for deployments?

I am going to use your script to modify the boot.wim (other post from me).
Looks like I need to concentrate on building different PE flavors. Do you
have a posting of your script on your blog that injects PE drivers?

Thanks Johan, you rock!

Post by unknown
If you use the driverpaths method, don't use any drivers in out-of-box
drivers.. (well you need to add one, and then remove it for
drivers.xml to be created)
For the Lite Touch WinPE image, I have a script that injects WinPE
drivers afterwards... I do this because it needs to be done anyway,
MDT does not set the "correct" scratchspace in WinPE.
You can also work with driver groups... assign os installations to use
an empty OS Drivers Group, and WinPE to use a WinPE Drivers Group (you
assign your winpe driver to it)
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by ron
Johan, nice job! One of the things that makes me uncomfortable with putting
drivers in the Out-of-Box container is that it is easy to loose track of
which ones are which. If I understand your process correctly, wouldn't that
mean, I only have to put drivers in the Out-of-Box container to inject into
building the Litetouch_x86. boot image like NIC drivers so I connect to the
distribution share?

Post by unknown
In update 1 you can tag the device drivers for a specific platform...
that removes most issues with x64 vs x86 drivers...
For a 100 percent working solution... check this article
They call me a control-freak... a drivers tale...
http://www.deployvista.com/Home/tabid/36/EntryID/72/language/en-US/Default.aspx
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by James
Hello,
wds/mdt 2008 infrastructure supporting about a dozen different hardware
models (mosty HP Proliant servers). I intend on making only one image per
operating system version that will work on all the servers... eg. one
windows 2003 standard image, one windows 2003 enterprise image, etc... and
also one image for each respective 64 bit version of the operating system.
Right now I'm downloading all the drivers (real fun) and I recall coming
across a post somewhere where someone was having an issue with x86 and x64
drivers... If I remember correctly they were adding the x86 version of the
drivers to the deplyment workbench followd by the x64 version of the drivers
and the x64 version was overwritting the x86 files... due do some files
between the x86 and x64 versions having the same filenames?
I have not started adding the drivers to the workbench yet and wanted to
find out about this before I do... anyone know? what happens? precautions?
links to procedure to follow to avoid this issue? is it even an issue
anymore with MDT 2008 Update 1?
any input on this would be greatly appreciated.

[unknown]

Well, you have to set the DriverGroups variable in the same way as you
do with DriverPaths... as for post-config in WinPE I will publish a
tool for that in one or two weeks time...

Regards

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

Post by ron
Johan, I noticed if I leave drivers in the Out of box container and add the
driverspath1 variable, it seems both areas are grabbed and put into the
C:\Drivers folder. Is that normal?
I have been using your driverspath1 process and I tell you what, there is
nothing that is built into MD to come close to the straightforward process
of creating folders for specific models of hardware. Yea, it takes up more
disk space, but that disadvantage pales in comparison to having the drivers
split out for clarity.
Can the driverspath1 procedure work for mass storage drivers for captured XP
images? Or does it have to be sysprepped with them already on the drive?
It sounds like having an empty drivers group for the deployment and having a
drivers group for the PE building is the way to go. Can you tell me how to
define an empty drivers group for deployments?
I am going to use your script to modify the boot.wim (other post from me).
Looks like I need to concentrate on building different PE flavors. Do you
have a posting of your script on your blog that injects PE drivers?
Thanks Johan, you rock!

Post by unknown
If you use the driverpaths method, don't use any drivers in out-of-box
drivers.. (well you need to add one, and then remove it for
drivers.xml to be created)
For the Lite Touch WinPE image, I have a script that injects WinPE
drivers afterwards... I do this because it needs to be done anyway,
MDT does not set the "correct" scratchspace in WinPE.
You can also work with driver groups... assign os installations to use
an empty OS Drivers Group, and WinPE to use a WinPE Drivers Group (you
assign your winpe driver to it)
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by ron
Johan, nice job! One of the things that makes me uncomfortable with putting
drivers in the Out-of-Box container is that it is easy to loose track of
which ones are which. If I understand your process correctly, wouldn't that
mean, I only have to put drivers in the Out-of-Box container to inject into
building the Litetouch_x86. boot image like NIC drivers so I connect to the
distribution share?

Post by unknown
In update 1 you can tag the device drivers for a specific platform...
that removes most issues with x64 vs x86 drivers...
For a 100 percent working solution... check this article
They call me a control-freak... a drivers tale...
http://www.deployvista.com/Home/tabid/36/EntryID/72/language/en-US/Default.aspx
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by James
Hello,
wds/mdt 2008 infrastructure supporting about a dozen different hardware
models (mosty HP Proliant servers). I intend on making only one image per
operating system version that will work on all the servers... eg. one
windows 2003 standard image, one windows 2003 enterprise image, etc... and
also one image for each respective 64 bit version of the operating system.
Right now I'm downloading all the drivers (real fun) and I recall coming
across a post somewhere where someone was having an issue with x86 and x64
drivers... If I remember correctly they were adding the x86 version of the
drivers to the deplyment workbench followd by the x64 version of the drivers
and the x64 version was overwritting the x86 files... due do some files
between the x86 and x64 versions having the same filenames?
I have not started adding the drivers to the workbench yet and wanted to
find out about this before I do... anyone know? what happens? precautions?
links to procedure to follow to avoid this issue? is it even an issue
anymore with MDT 2008 Update 1?
any input on this would be greatly appreciated.

[unknown]

I tried using MDT 2008 to manage server deployments, I tried out the whole image on a desktop to behave as server and it went well. Finally when I tried to roll it out on the server I was not able get past the welcome screen which promts you for the Keyboard layout and an option to configure static IP. Here starts the problems with with the NIC's. I dont find any, I tried adding win2k3 X64 drivers to the out of box, tried adding the monolithic drivers from the broadcom site, tried manually injecting them by mounting the wim.

Then came this DELL DTK, as alone DELL DTK is able to mount the network card. But when I try to use the same drivers to work with MDT2008, it still fails to recognise the n/w card.

Any help will appreciated.

EggHeadCafe - .NET Developer Portal of Choice
http://www.eggheadcafe.com/default.aspx?ref=ng

[unknown]

Add only the monolithic driver (v4.0 or 4.4 should work with 1950) to
the WinPE image.

Regards

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

Post by unknown
I tried using MDT 2008 to manage server deployments, I tried out the whole image on a desktop to behave as server and it went well. Finally when I tried to roll it out on the server I was not able get past the welcome screen which promts you for the Keyboard layout and an option to configure static IP. Here starts the problems with with the NIC's. I dont find any, I tried adding win2k3 X64 drivers to the out of box, tried adding the monolithic drivers from the broadcom site, tried manually injecting them by mounting the wim.
Then came this DELL DTK, as alone DELL DTK is able to mount the network card. But when I try to use the same drivers to work with MDT2008, it still fails to recognise the n/w card.
Any help will appreciated.
EggHeadCafe - .NET Developer Portal of Choice
http://www.eggheadcafe.com/default.aspx?ref=ng