James
2009-01-30 20:03:41 UTC
Hello,
I am having an issue with drivers.. I have read:
http://www.deployvista.com/Blog/tabid/70/EntryID/72/language/en-US/Default.aspx
but before I completely change methods altogether I want to be sure I can't
make it work just using the method I'm using now.
I'm having an issue with HP Smart Array SAS/SATA controller driver
(hpcissx2.inf). The issue that has brought me to needing to get a more
detailed understanding of how MDT handles drivers for server 2k3 is that the
driver I was using has a known issue with server 2003, but that issue is
fixed in server 2003 sp2. My problem is that sp2 is not in my image, and
can't be. So I had a succesfull build with this image but the problem is
when deploying it, it often crashes before SP2 gets installed, or during. So
what I need to do is use an older version of the driver (which I have).
I removed the drivers (both x86 and x64 versions) and added the older
versions to the workbench. The version that was removed was a version that
worked for 2k3 and 2k8 so I also had to add 2k8 only version of the drivers
because 1) I also need to support 2k8 deployments and 2) the WinPE boot
images needs vista/2k8 version to run the unattended install of 2k3 or 2k8.
When I imported the drivers I checked the box to allow duplicates, and after
import I configured each one to only be x86 or x64, based on what the
download info for the driver said. This is from something else I read some
time ago about drivers erroneously reporting supporting both x86 and x64.
now I can't even run the build, blue screen stop error (7B), clearly mass
storage driver related.
1. how do I know what driver it is trying to use at that point? When there
are multiple drivers for the same controller, just older/newer versions for
example?
2. how does the out-of-box drivers work? should I be able to get the control
I need here using them? I don't really think I need to break down by
computer model as I am only dealing with HP servers and several different
models may be using the same storage controller.
not sure how to address this.
I am having an issue with drivers.. I have read:
http://www.deployvista.com/Blog/tabid/70/EntryID/72/language/en-US/Default.aspx
but before I completely change methods altogether I want to be sure I can't
make it work just using the method I'm using now.
I'm having an issue with HP Smart Array SAS/SATA controller driver
(hpcissx2.inf). The issue that has brought me to needing to get a more
detailed understanding of how MDT handles drivers for server 2k3 is that the
driver I was using has a known issue with server 2003, but that issue is
fixed in server 2003 sp2. My problem is that sp2 is not in my image, and
can't be. So I had a succesfull build with this image but the problem is
when deploying it, it often crashes before SP2 gets installed, or during. So
what I need to do is use an older version of the driver (which I have).
I removed the drivers (both x86 and x64 versions) and added the older
versions to the workbench. The version that was removed was a version that
worked for 2k3 and 2k8 so I also had to add 2k8 only version of the drivers
because 1) I also need to support 2k8 deployments and 2) the WinPE boot
images needs vista/2k8 version to run the unattended install of 2k3 or 2k8.
When I imported the drivers I checked the box to allow duplicates, and after
import I configured each one to only be x86 or x64, based on what the
download info for the driver said. This is from something else I read some
time ago about drivers erroneously reporting supporting both x86 and x64.
now I can't even run the build, blue screen stop error (7B), clearly mass
storage driver related.
1. how do I know what driver it is trying to use at that point? When there
are multiple drivers for the same controller, just older/newer versions for
example?
2. how does the out-of-box drivers work? should I be able to get the control
I need here using them? I don't really think I need to break down by
computer model as I am only dealing with HP servers and several different
models may be using the same storage controller.
not sure how to address this.