Tuesday, May 22, 2012 2:41 PM
I am trying to do the following:
Inside my Applications, I have borrowed the VBScript wrapper from Johan for the Dell Drivers Pack. I have imported this into MDT 2012. When I try to install a 2003 server using this, it does not run due to the New Hardware Wizard.
How can I get this to work?
Wednesday, May 23, 2012 3:49 AM
Configuring the following registry key should prevent the wizard from showing up.
Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\PlugPlay\Parameters] "SuppressUI"=dword:00000001
If one of these posts answered your question or issue, please click on "Mark as answer".
My Blog | Twitter: @Schwarz_Stephan | MCTS, MCITP, MCC.
How to configure Windows RE/OEM Recovery Partition with MDT
Wednesday, May 23, 2012 2:54 PMI've added a TS Step to put this key in, however (after reboot) it still pops up. Is it because it's already found the new hardware and has asked for it once?
Sunday, May 27, 2012 4:05 AM
Here's a follow up..
I re-captured my image with this key set via the Hotfix (<cite>support.microsoft.com/kb/938596</cite>)
I re-ran my build and it failed. I noticed i had it csript.exe Install-DellDriversPack.wsf. I fixed this problem.
Now the drivers start to install, then the reboot task immediately following the install causes the driver install to fail. This is because the script calls the OS driver pack install.exe /auto then that extracts and opens a batch script to install. How can I get it to wait and not move to the next TS step?
I do want to avoid any user interaction.