BIG mdt problem

[James]

hello,

using mdt 2008 update 1

it appears the 'found new hardware' wizard halts the mdt process? how can
this be? that can't be right. I'm sure MS realized it is likely to occur...
I just ran a TS on a machine and 2 bad things happened:

1. system just shut down, suspect driver issue. Since the shutdown was
unexpected the normal auto admin login that mdt uses fails becuase the
prompt requires a reason for the unexpected shutdown... after you login
manually, it appears the TS continues.

2. 'found new hardware' wizards appears and the lti process won't continue
until you dismiss the wizard? huh? thats never happened before, the drivers
it wants get installed later in the TS anyway... why does this stop the
process?

then I went to my test environment to see if I could move the install of the
application that installs drivers up (earlier) in the process, before
instead of after installing sp2 for win server 2k3, in case this is a driver
issue that will occur on other hardware, and this one stops with the 'at
least one service or device failed to start..yada yada' windows message and
again, the whole LTI process stops until you hit 'ok' on that message? this
has never happened before and shouldn't the process just keep running
anyway?

[unknown]

What drivers are you installing that late in the process? and Why?

If you allow the sysprep minisetup process to install the drivers,
there will be no "hardware found" dialogs...

Regards

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

Post by James
hello,
using mdt 2008 update 1
it appears the 'found new hardware' wizard halts the mdt process? how can
this be? that can't be right. I'm sure MS realized it is likely to occur...
1. system just shut down, suspect driver issue. Since the shutdown was
unexpected the normal auto admin login that mdt uses fails becuase the
prompt requires a reason for the unexpected shutdown... after you login
manually, it appears the TS continues.
2. 'found new hardware' wizards appears and the lti process won't continue
until you dismiss the wizard? huh? thats never happened before, the drivers
it wants get installed later in the TS anyway... why does this stop the
process?
then I went to my test environment to see if I could move the install of the
application that installs drivers up (earlier) in the process, before
instead of after installing sp2 for win server 2k3, in case this is a driver
issue that will occur on other hardware, and this one stops with the 'at
least one service or device failed to start..yada yada' windows message and
again, the whole LTI process stops until you hit 'ok' on that message? this
has never happened before and shouldn't the process just keep running
anyway?

[James]

hello Johan,

1. the drivers I'm installing that late in the process done by the HP
Proliant Support Pack, which installs drivers and utilities... it has switch
for silent install and it searches your system and only installs the
drivers/utils that match your system... I'm fortunate enough that I only
support one manufacturer for deployments and this support pack has all the
drivers any of my servers will need. So I put the mass storage and nic
drivers in the workbench so the process can work then later in the TS I
install the support pack which installs the rest.

2. is the 'hardware found' dialog specific to a certian type or 'class' of
driver? like critical system drivers, that should be included in the
workbench? I believe the one that just occured said 'base system', or
something very general like that, very motherboard sounding...

3. shouldn't the LTI process just keep running though? then when the support
pack is installed this driver would be taken care of?

Post by unknown
What drivers are you installing that late in the process? and Why?
If you allow the sysprep minisetup process to install the drivers,
there will be no "hardware found" dialogs...
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by James
hello,
using mdt 2008 update 1
it appears the 'found new hardware' wizard halts the mdt process? how can
this be? that can't be right. I'm sure MS realized it is likely to occur...
1. system just shut down, suspect driver issue. Since the shutdown was
unexpected the normal auto admin login that mdt uses fails becuase the
prompt requires a reason for the unexpected shutdown... after you login
manually, it appears the TS continues.
2. 'found new hardware' wizards appears and the lti process won't continue
until you dismiss the wizard? huh? thats never happened before, the drivers
it wants get installed later in the TS anyway... why does this stop the
process?
then I went to my test environment to see if I could move the install of the
application that installs drivers up (earlier) in the process, before
instead of after installing sp2 for win server 2k3, in case this is a driver
issue that will occur on other hardware, and this one stops with the 'at
least one service or device failed to start..yada yada' windows message and
again, the whole LTI process stops until you hit 'ok' on that message? this
has never happened before and shouldn't the process just keep running
anyway?

[unknown]

1. ok

2. No.

3. Yes, it should, but I recommend including the drivers in the
workbench, or use the below method...

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

Regards

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

Post by James
hello Johan,
1. the drivers I'm installing that late in the process done by the HP
Proliant Support Pack, which installs drivers and utilities... it has switch
for silent install and it searches your system and only installs the
drivers/utils that match your system... I'm fortunate enough that I only
support one manufacturer for deployments and this support pack has all the
drivers any of my servers will need. So I put the mass storage and nic
drivers in the workbench so the process can work then later in the TS I
install the support pack which installs the rest.
2. is the 'hardware found' dialog specific to a certian type or 'class' of
driver? like critical system drivers, that should be included in the
workbench? I believe the one that just occured said 'base system', or
something very general like that, very motherboard sounding...
3. shouldn't the LTI process just keep running though? then when the support
pack is installed this driver would be taken care of?

Post by unknown
What drivers are you installing that late in the process? and Why?
If you allow the sysprep minisetup process to install the drivers,
there will be no "hardware found" dialogs...
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by James
hello,
using mdt 2008 update 1
it appears the 'found new hardware' wizard halts the mdt process? how can
this be? that can't be right. I'm sure MS realized it is likely to occur...
1. system just shut down, suspect driver issue. Since the shutdown was
unexpected the normal auto admin login that mdt uses fails becuase the
prompt requires a reason for the unexpected shutdown... after you login
manually, it appears the TS continues.
2. 'found new hardware' wizards appears and the lti process won't continue
until you dismiss the wizard? huh? thats never happened before, the drivers
it wants get installed later in the TS anyway... why does this stop the
process?
then I went to my test environment to see if I could move the install of the
application that installs drivers up (earlier) in the process, before
instead of after installing sp2 for win server 2k3, in case this is a driver
issue that will occur on other hardware, and this one stops with the 'at
least one service or device failed to start..yada yada' windows message and
again, the whole LTI process stops until you hit 'ok' on that message? this
has never happened before and shouldn't the process just keep running
anyway?

[James]

thanks again Johan.

Post by unknown
1. ok
2. No.
3. Yes, it should, but I recommend including the drivers in the
workbench, or use the below method...
They call me a control-freak... a drivers tale...
http://www.deployvista.com/Blog/tabid/70/EntryID/72/language/en-US/Default.aspx
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by James
hello Johan,
1. the drivers I'm installing that late in the process done by the HP
Proliant Support Pack, which installs drivers and utilities... it has switch
for silent install and it searches your system and only installs the
drivers/utils that match your system... I'm fortunate enough that I only
support one manufacturer for deployments and this support pack has all the
drivers any of my servers will need. So I put the mass storage and nic
drivers in the workbench so the process can work then later in the TS I
install the support pack which installs the rest.
2. is the 'hardware found' dialog specific to a certian type or 'class' of
driver? like critical system drivers, that should be included in the
workbench? I believe the one that just occured said 'base system', or
something very general like that, very motherboard sounding...
3. shouldn't the LTI process just keep running though? then when the support
pack is installed this driver would be taken care of?

Post by unknown
What drivers are you installing that late in the process? and Why?
If you allow the sysprep minisetup process to install the drivers,
there will be no "hardware found" dialogs...
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by James
hello,
using mdt 2008 update 1
it appears the 'found new hardware' wizard halts the mdt process? how can
this be? that can't be right. I'm sure MS realized it is likely to occur...
1. system just shut down, suspect driver issue. Since the shutdown was
unexpected the normal auto admin login that mdt uses fails becuase the
prompt requires a reason for the unexpected shutdown... after you login
manually, it appears the TS continues.
2. 'found new hardware' wizards appears and the lti process won't continue
until you dismiss the wizard? huh? thats never happened before, the drivers
it wants get installed later in the TS anyway... why does this stop the
process?
then I went to my test environment to see if I could move the install of the
application that installs drivers up (earlier) in the process, before
instead of after installing sp2 for win server 2k3, in case this is a driver
issue that will occur on other hardware, and this one stops with the 'at
least one service or device failed to start..yada yada' windows message and
again, the whole LTI process stops until you hit 'ok' on that message? this
has never happened before and shouldn't the process just keep running
anyway?