It isn't populated by MDT. That variable is for you to specify where the computer object should be placed when the machine joins the domain. If you do not specify a value for that variable then it will contain nothing.
If you are going to specify a value, then I don't see any reason that you could not use it as a condition for the installs. It will be complicated as it will have a value like "ou=laptops,ou=clients,ou=computers..." You may want to use a script to find your computer in AD and then just strip off the OU name you're interested in then assign that to a variable of your choosing to use as a condition. The script finds the computer in "ou=payroll,ou=HR,ou=computers...". Parse out the "payroll" (if that's what you're interested in) and then assign that to a variable. (MyOU = Payroll). Then the condition of your software install would be IF MyOU = Payroll, then install the payroll applications.... Mike From: [email protected] [mailto:[email protected]] On Behalf Of Tate, Stephen Sent: Tuesday, July 23, 2013 11:33 AM To: [email protected] Subject: [MDT-OSD] MDT 2012 U1 Task Sequence Variables I'm looking for a way to target software deployments per OU in an MDT 2012 U1/ SCCM sequence. I saw that there was a variable named OSDDomainName, but it states this is used to specify the name of the OU in the domain to which the computer account should be created. Has anyone tested this? Would this work to use as a condition in the task sequence to use for software installs? If not, are you aware of another variable that would do the trick? Thanks in advance, Stephen ________________________________ 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. ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues
