http://technet.microsoft.com/en-us/library/hh825070.aspx
From: [email protected] [mailto:[email protected]] On Behalf Of Stephen Owen Sent: Thursday, October 24, 2013 8:24 AM To: [email protected] Subject: Re: [MDT-OSD] RE: Variable Driven Driver installs? Well, what does the Install Drivers step really do under the covers? (Purely hypothetical guessing begins here) If it just copies the files from the driver package into the C:\windows\system32\DriverStore directory and then runs an install action on the .inf files it finds, you could create a single VB or PowerShell script to do this action, that accepts and TS Variable as an input parameter to pull down the driver package and start the install. On Mon, Oct 21, 2013 at 5:55 PM, Miller, Todd <[email protected]<mailto:[email protected]>> wrote: What I mean is that I have a bunch of driver packages like I'm sure everyone else has.... [cid:[email protected]] I would like to set a variable like SMSDriverPackage to "Windows7x64-Dell-LatitudeE6410-A09" (or even specify the packageID)- perhaps using a make/model value in MDT database or perhaps in the CustomSettings.ini or it could be a script that populates this value - how the variable gets set doesn't matter. Then, instead of 30 or more nearly identical Install Driver Package sections in the TS, I could have just one that says install driver package %SMSDriverPackage% and it would link up to the package name (or package ID) stored in the variable rather than needing to be explicitly defined in the Install Driver step. I think what this would take is to create a new custom Install Driver Package step (by the SA team or whatever...) that takes a variable as input rather than the one currently there that requires explicit selection from a pull down menu. From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Niall Brady Sent: Friday, October 04, 2013 9:06 AM To: [email protected]<mailto:[email protected]> Subject: Re: [MDT-OSD] RE: Variable Driven Driver installs? in R2 you can have dynamic variables<http://technet.microsoft.com/en-us/library/dn236351.aspx#BKMK_WhatsNew_Client_Deployment> Set Dynamic Variables: This task sequence step gathers information and sets specific task sequence variables with the information. Then, it evaluates defined rules and sets task sequence variables based on the variables and values configured for rules that evaluate to true. so set foo=bar If SUPPORTEDMODEL = TRUE then set foo=bar1 so if foo=bar1 then use Auto Apply driver package instead of Apply Driver Package, just a thought... On Fri, Oct 4, 2013 at 1:00 PM, Chris Nackers <[email protected]<mailto:[email protected]>> wrote: I'm sure it's possible, you can add custom fields to the DB... but I'm not sure that would really minimize things, you would still have to create all the if x equals y in the database.... But at least it wouldn't be in each TS... Chris Nackers Microsoft MVP - Enterprise Client Management Email: [email protected]<mailto:[email protected]> Nackers Consulting Services, LLC From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Miller, Todd Sent: Tuesday, October 01, 2013 10:23 AM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] Variable Driven Driver installs? Is there a way to make Driver installation in the "Total Control" model be OSD variable driven like packages are? What I mean is, can I use MDTDB or some other method to assign the Driver package to a Model and then just have a single "Install Driver Package" line in my Task Sequence? You can install Packages with a base variable, I'm thinking something like that. Right now, I have something like this... repeated > 100 times. [cid:[email protected]] Followed by [cid:[email protected]] To fall back to "chaos" if the model being installed is not specifically supported by "total control" What I'd like to do is move all that to the MDT Database and then have two things in the TS. If SUPPORTEDMODEL = TRUE, Install "DRIVERPACKAGE001" If SUPPORTEDMODEL = FALSE, Auto Apply Drivers In MDT DB, I would assign SUPPORTEDMODEL and DRIVERPACKAGE What would it take to add code to inject drivers based on a variable package name/GUID? Are there any community developed add-ins to Task Sequencing? ________________________________ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you. ________________________________ ________________________________ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you. ________________________________ [CONFIDENTIALITY AND PRIVACY NOTICE] Information transmitted by this email is proprietary to Medtronic and is intended for use only by the individual or entity to which it is addressed, and may contain information that is private, privileged, confidential or exempt from disclosure under applicable law. If you are not the intended recipient or it appears that this mail has been forwarded to you without proper authority, you are notified that any use or dissemination of this information in any manner is strictly prohibited. In such cases, please delete this mail from your records. To view this notice in other languages you can either select the following link or manually copy and paste the link into the address bar of a web browser: http://emaildisclaimer.medtronic.com
<<inline: image001.png>>
<<inline: image002.png>>
<<inline: image003.png>>
