Pages

Friday, 11 May 2012

Empty program list in SCCM Task Sequence

I've just come in to find our Windows 7 builds are failing on a specific program that is installed during the task sequence.  It happens it was Trend Anti Virus which I had been working on the previous day.

Before getting into the log files I had a look at the task sequence and noticed that there was no program listed.  Ah ha!  Problem solved > click drop down and select program....  No programs are listed ??!!  I checked the package and I have two programs in there - a standard install and one with verbose logging enabled...

Tried deleting the step in the TS and recreating it... Still nothing...

Resolution

I hold my hand up here - I had changed the interaction to "Only when a user is logged in"

Changed it back and sure enough it was back to normal.


Not so much a problem but it's worth noting - if it's a Friday morning and you haven't had your coffee yet it may catch you out...

Hope this helps someone :)
Posted by
Labels: , , , , ,

9 comments:

  1. Unknown5 October 2012 at 13:47

    This comment has been removed by the author.

    ReplyDelete
  2. Unknown5 October 2012 at 13:49

    Thank you, THank you, Thank you. Was beating my head this morning trying to figure out why the program list was empty. This was it!

    kc2ate@gmail.com

    ReplyDelete
  3. Doc Norton26 June 2013 at 15:42

    Hi KC2ate,

    Thanks for the comment and I'm glad it helped out :)

    docN

    ReplyDelete
  4. Leonid Orlov19 July 2013 at 10:01

    Thanks!

    ReplyDelete
  5. Doc Norton26 November 2013 at 13:13

    You're welcome :)

    ReplyDelete
  6. Anonymous11 December 2013 at 14:29

    It is not whether the user is logged in or not that creates this issue, it is the "allow user interaction". Remove this and you will be able to see the program.

    ReplyDelete
    Replies
    1. Doc Norton13 December 2013 at 15:32

      Hey thanks for the feedback.

      I cannot comment on this as the above worked for me in that scenario and for the other people who have commented here. Maybe it sounds like your scenario is slightly different (I never allow user interaction so this wasn't ticked).

      Also there would never be a user logged in during OSD. You made me doubt myself so I just went back and recreated this and it is only the "Program can run" option set as "whether or not a user is logged in" that causes this outcome.

      Thanks for the input though as this may also help people in the future. That's the way these forums work!

      Please spread the word about Pheasant Plucker :)

      Delete
    2. Doc Norton13 December 2013 at 15:34

      **and it is only the "Program can run" option set as "whether or not a user is logged in" that causes this outcome.

      **In that I didn't need to tick the "allow interaction box" to recreate.

      Delete

Let me know if this helped.

I'd really appreciate any comments (well, only nice ones) so please feel free to let me know what you think of the blog and also ask for further help...

Subscribe to: Post Comments (Atom)