Another way would be to use a separate driver step in the TS, and filter with the wmi query. I'll be diving into HP and Lenovo drivers shortly at my present client. I MISS DELL!!!!!!
Warren, you guys are the best. Christopher Catlett Consultant | Detroit [MCTS_2013_small] Sogeti USA Office 248-876-9738 |Fax 877.406.9647 26957 Northwestern Highway, Suite 130, Southfield, MI 48033-8456 www.us.sogeti.com<http://www.us.sogeti.com/> From: [email protected] [mailto:[email protected]] On Behalf Of Ryan Sent: Wednesday, September 18, 2013 9:48 AM To: [email protected] Subject: Re: [mssms] mdt & drivergroup I'm more of a fan of HP's bleh line myself. Are you sure the correct drivers are in PE for the NIC? On Wed, Sep 18, 2013 at 8:41 AM, Stuart Watret <[email protected]<mailto:[email protected]>> wrote: implemented drivergroup entries in my mdt the other day to get specific machines to use certain drivers. this worked well by adding the line to the rules tab like this: [HP blah blah 8440b] drivergroup0001=path blah blah driver selectionprofile=nothing This was working well until I tried the above model. No drivers getting installed. Checked the bdd log, sure enough it finds the entry for the model, so that works but doesn't pick up the path. No rhyme or reason I can see, found another hp model failing this also and have revoked them back to the total kaos drivers bin, which works but is slow. Any thoughts. Stuart Watret Offshore - IT Ltd
<<inline: image001.jpg>>
