locked
Discovery Issues - Missing Client Actions (only 4 showing) and clients not pulling policies after image/reimage RRS feed

  • Question

  • We’re having an issue where when we image/reimage a computer (mainly laptops is what we’re seeing) they are not fully grabbing the policies and required software.  It finds the site in Configuration Manager, so it can talk to the MP…but when you go to Actions, it does not have a Discovery Data Collection Cycle available.  Honestly, it is only showing 4 of the actions…I’m stumped. 

    I’m wondering if we have our computer rename program in the wrong place and that’s throwing it off?

    Here’s a screenshot of our task sequence, as well as what available actions are listed.  The laptop will sit there online and not gather any software, and most times is not online long enough to gather the required software even after it gains the policies (if it ever does).

    This is our task sequence/order

    I'm probably overlooking something, any help would be greatly appreciated!  The Computer Rename is an EXE a guy that works for me wrote that renames the computer based on serial number.  I'm wondering if it's placed in the wrong location in the task sequence...i honestly don't know. 

    Here's the actions we do have on each laptop that's been reimaged, a lot missing:

    Any thoughts/Ideas?

    Thank you!

    Wednesday, September 3, 2014 7:20 PM

All replies

  • Have you already tried just waiting for a day or so? Are the actions appearing then?
    Have you checked if the client is stuck in provisioning mode?

    Torsten Meringer | http://www.mssccmfaq.de

    Wednesday, September 3, 2014 7:47 PM
  • Have you verified that the TS is completing successfully?

    Have you verified that the client is not stuck in provisioning mode?

    Why are you "renaming" the computer in the TS instead of just naming it correctly in the first place by setting the OSDComputerName task sequence variable with a script?


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Wednesday, September 3, 2014 7:48 PM
  • Have you already tried just waiting for a day or so? Are the actions appearing then?
    Have you checked if the client is stuck in provisioning mode?

    Torsten Meringer | http://www.mssccmfaq.de


    And, i just looked and it was stuck in provisioning mode?  I found this site based on research after your suggestion of finding if it was in provision mode and it sounds right along what's going on with our environment:

    http://www.toolzz.com/?p=1278

    I ran those commands (i'll list them here to save time for anyone else having this issue), rebooted, and it immediately popped up downloading / installing new software!

    I really appreciate your help on this! thank you!

    Wednesday, September 3, 2014 8:27 PM
  • Have you verified that the TS is completing successfully?

    Have you verified that the client is not stuck in provisioning mode?

    Why are you "renaming" the computer in the TS instead of just naming it correctly in the first place by setting the OSDComputerName task sequence variable with a script?


    Jason | http://blog.configmgrftw.com | @jasonsandys

    the TS was completing, yes...i saw it in the logs.  

    it was stuck in provisioning mode, and i posted a blog link that helped me to get it fixed up.  any clue if this is just a bug, or if this is something wrong with the organization of my task sequence?

    As for renaming, we have 6 sites.. and we rename our computers based on site name - serial number.  Examples:

    mphs-dsdf9
    mpjh-df90df
    mpes-d9ddf
    mpce-asdf0
    mpwk-sdf88
    mpkc-adfsd0

    I'm not sure of a way to do this natively with SCCM...if any of you know, i'm all ears!  I want to be able to rename a computer based on the subnet the computer is imaging from, and then add the serial number after a hyphen.  I know you can do it thorugh MDT/customsettings.ini files...just not really sure how.

    Wednesday, September 3, 2014 8:30 PM
  • Being in provisioning mode implies that the TS didn't finish successfully. You need to troubleshoot this and determine why otherwise you're just fixing a symptom.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Wednesday, September 3, 2014 8:31 PM
  • There's tons of info on the web about renaming during a TS. Ultimately, as mention, you are always simply setting the OSDComputerName task sequence variable which in turn gets populated in the unattend.xml to drive Windows setup and name the system correct from the get go.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Wednesday, September 3, 2014 8:51 PM