Discussion:
MDT 2008 - warning about duplicate drivers on a build and capture job?
(too old to reply)
James
2009-02-11 21:41:53 UTC
Permalink
Have not run into this before. Using MDT 2008 Update 1 my build and capture
task sequence completed with no errors but 6 warnings about duplicate
drivers... its a server 2003 sp2 build.

Does this need to be addressed? what problems may occur when deploying this
resultant custom wim image to other machines?
Esben
2009-04-08 11:07:01 UTC
Permalink
Hi James,

I cant imagine it having any impact on the wim file. - What MDT does when
you import a duplicate driver is to tag it "(1)" in the end this tag will
also be visible in the deployment workbench, so you should be able to quite
easily pick out the duplicates... - But again, I don´t think it will cause
you any grief since the OS install will collect the drivers it needs during
installation, and leave what it doesn´t.

/Esben
Post by James
Have not run into this before. Using MDT 2008 Update 1 my build and capture
task sequence completed with no errors but 6 warnings about duplicate
drivers... its a server 2003 sp2 build.
Does this need to be addressed? what problems may occur when deploying this
resultant custom wim image to other machines?
James
2009-04-08 16:38:01 UTC
Permalink
hi, thanks for the input. Its appreciated.
Post by Esben
Hi James,
I cant imagine it having any impact on the wim file. - What MDT does when
you import a duplicate driver is to tag it "(1)" in the end this tag will
also be visible in the deployment workbench, so you should be able to quite
easily pick out the duplicates... - But again, I don´t think it will cause
you any grief since the OS install will collect the drivers it needs during
installation, and leave what it doesn´t.
/Esben
Post by James
Have not run into this before. Using MDT 2008 Update 1 my build and capture
task sequence completed with no errors but 6 warnings about duplicate
drivers... its a server 2003 sp2 build.
Does this need to be addressed? what problems may occur when deploying this
resultant custom wim image to other machines?
Loading...