Cool- thanks for the feedback folks.
From: [email protected] [mailto:[email protected]] On Behalf Of Chris Nackers Sent: Tuesday, July 23, 2013 3:43 PM To: [email protected] Subject: EXTERNAL:RE: [MDT-OSD] MDT 2012 U1 Task Sequence Variables I believe the TS honors the Application Requirements, but most of the time we create new App models with a single deployment type and no fancy requirements to make sure it works with OSD. So definitely TEST that before you rely on it. As for variables, if you are using MDT, then MachineObjectOU is a variable for the OU you can use. You could very well do conditional TS variables look ps on each app install step, but that could get long, but it would work. If MachineObjectOU=whatever, then install App A... etc... 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]] On Behalf Of Benjamin Monrad Sent: Tuesday, July 23, 2013 10:59 AM To: mdtosd Subject: Re: [MDT-OSD] MDT 2012 U1 Task Sequence Variables If you can use Applications (rather than Package/Program), then you can set the device OU as a Requirement in the Deployment Type rather than using Task Sequence Variables. ----------------------------------------- This message is intended only for the individual or entity to which it is addressed and contains information that is proprietary to The Babcock & Wilcox Company and/or its affiliates, or may be otherwise confidential. If the reader of this message is not the intended recipient, or the employee agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by return e-mail and delete this message from your computer. Thank you.
