none
Task sequence any condition with more than one option not being matched

    Question

  • I've been following this blog post to setup a task sequence to inject OoB drivers during a LTI.  It works fine if I set the Option for a inject drivers task that says

    "If any conditions are true

    Task sequence variable Model equals Latitude E6420"

    If I adjust the option to have...

    "If any conditions are true

    Task sequence variable Model equals Latitude E6420

    Task sequence variable Model equals Latitude E6520"

    ...the condition doesn't match and the drivers aren't injected, and the task is skipped over.  I can't figure out why adding the second option causes this task not to run.  

    Is there a log file I can look at to see how it's matching things up against the option?  I'd rather not have to create 3 or 4 tasks to inject drivers for models of the same series that mostly share the same drivers.  I would think I could build the rule to match more than one model. 


    • Edited by Utegrad Thursday, April 04, 2013 12:41 AM Formatting
    Thursday, April 04, 2013 12:39 AM

Answers

  • In my experience, that graphic and the statement are a bit off (from your linked blog).  Since the single example isn't a child of the "If" condition, the "If" condition has no bearing and it's basically a straight match to the single Model check:

    -- If all conditions are true
    -- Task sequence ....

    Instead, for you, I believe you need to ensure it looks like this:

    -- If any conditions are true
    ---- Model equals Latitude E6420
    ---- Model equals Latitude E6520

    When you add the child conditions, make sure the "If any conditions are true" is selected, THEN add your condition.  This should ensure they are properly nested, and handled appropriately.  Here's an example of what I mean:

    This condition will fire if (Test and / or Test2) AND (Test3) AND (Test4) is true.


    David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek

    • Marked as answer by Utegrad Thursday, April 04, 2013 2:12 AM
    Thursday, April 04, 2013 2:01 AM

All replies

  • In my experience, that graphic and the statement are a bit off (from your linked blog).  Since the single example isn't a child of the "If" condition, the "If" condition has no bearing and it's basically a straight match to the single Model check:

    -- If all conditions are true
    -- Task sequence ....

    Instead, for you, I believe you need to ensure it looks like this:

    -- If any conditions are true
    ---- Model equals Latitude E6420
    ---- Model equals Latitude E6520

    When you add the child conditions, make sure the "If any conditions are true" is selected, THEN add your condition.  This should ensure they are properly nested, and handled appropriately.  Here's an example of what I mean:

    This condition will fire if (Test and / or Test2) AND (Test3) AND (Test4) is true.


    David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek

    • Marked as answer by Utegrad Thursday, April 04, 2013 2:12 AM
    Thursday, April 04, 2013 2:01 AM
  • Thank you for your response.  It showed me what I was doing wrong.  I wasn't selecting the if ... any statement before adding the task sequence variable check, so the variables weren't nested in the any statement.

    Before:

    Before Nesting

    After:

    After nesting

    I'll check it in the morning when I'm back in the office, but I'm confident this will correct my error. 

    Thursday, April 04, 2013 2:11 AM