|
| 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 | |
sintaks
Posts:5
 | | 10/28/2008 7:12 AM |
| I was just wondering if I could get some feedback from you guys on driver management. I have two schools of thought here: - Ben Hunter's way - using the model directory structure and driverspath1=\\server\share\%model% in cs.ini
- Task sequence variable - setting driversgroup001=%model% and then importing all drivers to the workbench, using model as the group name.
The second option is appealing because it seems easier, but less organized. The first option is organized and I'll have all my drivers in one clean directory structure, but it's more work. Either way seems like it would be an efficient way to handle drivers. Feel free to chime in... | | | |
| David
Posts:50
| | 11/04/2008 10:14 AM |
| driver group way sounds more appealing to me... I am at the same point as you, and need to decide which way to go. The driver group way just has a cleaner feel to me, and the drivers will all be in the workbench... I want to make sure I understand correctly though, the part of 'driver management' these 2 options are refering to is 'post os installation' as opposed to making the right drivers available for 1, winPE to actually be able to do the deployment (nic and storage drivers), and 2, the driver injection feature needed to make one image work for many machines (storage drivers)... right? The 2 methods you mention would handle all the drivers for the machine like audio, video, etc... | | | |
| Simon Hardy
Posts:20
| | 11/05/2008 3:57 AM |
| I eventually went for option 3....
All network and mass storage drivers imported into workbench so WinPE and OS will allways be able to boot, map drives and install.
Then using the folder structure and DriversPath variable for all other drivers..... This allows me to lock specific drivers to specific makes and models and to issue "driver packs". | | | |
| FarmerPete
Posts:168
| | 11/12/2008 7:27 AM |
| | I've been adding drivers directly into the workbench. It's worked fine. I haven't even done it the way you suggested and limited the drivers to a specific model. I instead just added drivers for each model of computer, and then when I deployed to a new computer that was missing drivers, I added the missing drivers only. It's worked out great for me thus far, and I've only had one real hiccup. I added some drivers for a Lenovo X61 tablet to MDT and it caused a problem with my Fujtisu tablet deployments. Apparently the lenovo keyboard driver would get installed for the Fujitsu, and it made the brightness keys on the Fujitsu not work. After a bit of digging I figured out exactly what was going on, went into the INF file for the lenovo driver and deleted the device ID of the Fujitsu hardware. Now it works great again. We have a LOT of different models. We have 28 different types/models of IBM systems alone. It would be very difficult to find and maintain all of those drivers, let alone maintain CS.ini | | | |
|
| | 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. |
| |
| |
|