|
| Guests can view and read messages in the community forums, but you must register and log in to Deployment Forum before you can post messages. Click Register at the top of this page. Before posting messages, please read the forum guidelines at the bottom of this page. | |
| | Author | Messages | |
Yalu
Posts:3
 | | 02/05/2009 1:42 PM |
| hello everybody,
I defined an unattended Windows XPSP3 setup + applications on VMWare ESX, which I further use as a base image for deployment to my site's physical HW.
I've generally followed instructions at http://blogs.technet.com/deploymentguys/archive/2008/04/17/driver-management-part-2-mdt-2008.aspx for driver specific details.
In my setup I've defined roles that contain driver applications (BAD drivers) who are installed silently when a specific role is chosen (ex. Role-Dell-Latitude-E6500). Everything works fine,except for a rather annoying detail:
When Windows XP detects new hardware, it starts the "Found new hardware wizard".
At the same time, driver applications are installed as a part of a MDT2008 task sequence.
Depending on the type of driver application, I've noticed some of them tend to "hang" while the wizard is showing.
As soon as I cancel the wizard, installation continues.
I have a strong feeling, the problem has something to do with the DPINST utility waiting for the wizard to close.
In a LTI-scenario this is rather annoying.
Has anyone encountered the same issues?
Any suggestions on how to resolve or bypass this problem? Any help is greatly appreciated!
Thanks,
Yalu | | | |
| Mark Allcock
Posts:380
| | 02/06/2009 3:00 AM |
| Yalu
This is probably the worst suggestion you'll get for this issue but you never know, it might work.
You could try setting the Plug and Play service to start Manually or perhaps even settings it to Disabled. Not sure what the effects of this would be on the system and it may even prevent you from installing the BAD drivers...
Try modifying the 'HKLM\SYSTEM\CurrentControlSet\Services\PlugPlay\Start' DWORD value and change it to either 3 for Manual or 4 for Disabled. You could achieve this with a .reg file or even the REG ADD command.
*Before anyone else flames me for this, please consider how difficult an issue this is to get around!*
Mark | | | |
| Yalu
Posts:3
| | 02/11/2009 1:36 AM |
| Disabling the PlugPlay-service seems a bit drastic.
In the meantime I have found a solution to my problem ( a work-around actually).
I inserted an AutoIt-script in the sequence to cancel out the Wizard screens.
Thanks,
Yalu | | | |
| Mark Allcock
Posts:380
| | 02/11/2009 3:39 AM |
| Hi Yalu
Yeah you're right, disabling the Plug and Play service is probably the worst suggestion ever, but I cannot abide Auto-It scripts and so naturally I chose the most drastic solution ever 
Hope it goes okay for you
Mark | | | |
| canni
Posts:26
| | 02/13/2009 3:52 PM |
| http://support.microsoft.com/default.aspx/kb/938596
IF your image is sp3 you do not need to install this KB as it is already included
I use 2 reg. hacks in my Task sequence 1 to disable the " new found hardware wizard" (run reg hack, restart machine) the second to enable it ( near the end of the deployment) This fix has helped me not only clean up the install process from a " display" point of view but also helped in installing applications that require no new hardware screen to be present. i hope this helps
canni
Posts:16
01/22/2009 2:33 PM DeleteEdit Quote ReplyAlert
You have to have the KB938596 installed on your image. Then use the the reg file entrys to control the UI
| | | |
| Mark Allcock
Posts:380
| | 02/15/2009 9:02 AM |
| | Wow! Nice find there canni! Will have to remember this one. | | | |
| Yalu
Posts:3
| | 02/15/2009 11:54 AM |
| Indeed, how could I have missed that one? I had been experimenting with the suppressUI reg setting, not realizing it with x64 only.
This would be a much "cleaner" solution than the auto-it scripts. Yalu | | | |
| Paul
Posts:35
| | 02/16/2009 10:49 PM |
| Yalu, Can I ask what Dell driver it was? Last week I experienced a similar dell driver problem but it had an easy solution. The chipset drivers (bad driver - application type) would automatically install through my driver package, but when the OS logged in it would have a prompt to go through the driver wizard. If the user clicked next it would automatically install the drivers, but it was still an annoyance. To fix this, after I imaged the box I manually ran the executable. This ran through the installation process for the chipset drivers. Once the setup had extracted the drivers to the local drive I was able to copy that directory to the server and import them into configuration manager and then into the driver package. After this it installed the drivers correctly and no longer prompted the user with the install driver wizard. Hope that helps, Paul Goodson | | | |
| FarmerPete
Posts:209
| | 02/18/2009 12:08 PM |
| | I use a mixture of the reg key listed above, as well as a program I downloaded from the MSFN website called "Driver Forge" that uses brute force to install all apps. So if I get windows up, Driver Forge will install the drivers and if it can't, it will tell it to STFU and stop bugging me. | | | |
|
| | You are not authorized to post a reply. |
|
| |
ActiveForums 3.7 | |
|  | These forums are a user-supported community for IT professionals to exchange deployment tips, solutions, and techniques. For the benefit of all Deployment Forum members, please observe the following guidelines when posting to these forums: - We reserve the right to remove any message. Our moderators will remove all messages that are not respectful or productive. Profanity, racism, prejudice, and flaming are not tolerated.
- Do not advertise products or services. Our moderators will remove all advertisements or service announcements. Product and service recommendations from active Deployment Forum members are encouraged, however.
- Make sure your question isn't already answered. Before posting questions, search the forums. After ensuring that your questions are unique, post them to the most appropriate forum. This will help reduce noise in the forums.
- Help make the most of each thread. Do not post unrelated messages to a thread. Also, if you've resolved a question outside of these forums, please share the solution with other members by posting it back to the thread.
- Do not share confidential information. Confidential information includes product keys and addresses. Our moderators will edit any message containing confidential information, so double-check messages and their attachments before posting them.
- Post messages using only the English language. For the benefit of all Deployment Forum members, please post your messages using the English language.
We hope that you enjoy using this community. Please submit your comments and feedback on the Comments and Feedback page or post them to the Comments, Feedback forum. |
| |
| |
|