locked
SCCM computer discovery RRS feed

  • Question

  • Hi All,

    I have a computer in the SCCM environment which is not dicovered in SCCM but is present in the OU of AD. The computer is on the network(wired) , i have checked for the boundary it was there , but still no luck.

    One information i can give is in the AD it shows that system was last logged on 15 days before but presently the laptop is on the network(wired). How can i resolve this issue?what logs should i check , how should i go about it.

    Rgs,

    Thursday, April 25, 2013 5:49 PM

Answers

  • Everything is already listed in this thread for AD System Discovery:

    - Within the scope specified within the config of AD System Discovery

    - Account is not disabled

    - Name is resolvable via DNS by the site server

    If you need to troubleshoot this, as mentioned above, review/monitor the adsysdis.log

    Also, AD System discovery has nothing to do with heartbeat discovery.


    Jason | http://blog.configmgrftw.com

    • Marked as answer by Juke Chou Friday, April 26, 2013 8:32 AM
    • Unmarked as answer by Juke Chou Friday, April 26, 2013 8:33 AM
    • Proposed as answer by Juke Chou Friday, April 26, 2013 8:34 AM
    • Marked as answer by Juke Chou Wednesday, May 8, 2013 11:11 AM
    Friday, April 26, 2013 3:22 AM

All replies

  • Hi,

    Check the Adsysdis.log file, the site server must be able to resolve the computer name in DNS, otherwise the computer will not be discovered.

    Regards,
    Jörgen


    -- My System Center blog ccmexec.com -- Twitter @ccmexec

    Thursday, April 25, 2013 5:56 PM
  • Check adsysdis.log

    Does the machine exist in the dns?

    • Proposed as answer by Abraham Ajo Monday, May 26, 2014 11:03 PM
    Thursday, April 25, 2013 5:56 PM
  • In additional, check the machines have valid IP address in DNS. It requires valid records in DNS in order to create a discovery record.

    Thursday, April 25, 2013 6:11 PM
  • Two additional notes are that the account must not be disabled in AD and also that boundaries have absolutely nothing to do with discovery.

    Jason | http://blog.configmgrftw.com

    Friday, April 26, 2013 2:41 AM
  • Can anyone list all the necessary things/steps that one should check to ensure that what ever machines are present in AD OU same is reflecting in SCCM All systems, provided Heart discovery is enabled and collections are query based collections.

    Rgs,

    Friday, April 26, 2013 3:11 AM
  • Everything is already listed in this thread for AD System Discovery:

    - Within the scope specified within the config of AD System Discovery

    - Account is not disabled

    - Name is resolvable via DNS by the site server

    If you need to troubleshoot this, as mentioned above, review/monitor the adsysdis.log

    Also, AD System discovery has nothing to do with heartbeat discovery.


    Jason | http://blog.configmgrftw.com

    • Marked as answer by Juke Chou Friday, April 26, 2013 8:32 AM
    • Unmarked as answer by Juke Chou Friday, April 26, 2013 8:33 AM
    • Proposed as answer by Juke Chou Friday, April 26, 2013 8:34 AM
    • Marked as answer by Juke Chou Wednesday, May 8, 2013 11:11 AM
    Friday, April 26, 2013 3:22 AM
  • in our environment only heart beat discovery method is enabled , any inputs..

    Sunday, April 28, 2013 10:56 AM
  • Heartbeat discovery is a client initiated keep alive that only works with a fully functioning, installed client agent and has nothing to do with AD or AD OUs. If you need info from AD then you need to enable AD system discovery.

    Jason | http://blog.configmgrftw.com

    Sunday, April 28, 2013 3:32 PM
  • Go through the below link for SCCM Discovery

    http://technet.microsoft.com/en-us/library/bb632938.aspx


    Monday, April 29, 2013 11:18 AM
  • hi Narendra,

    If its for a single machine,if you have the client center tool try to connect on it if its successful,please initiate the Update datadiscovery record that will update the record in DB and collection, i faced this too once i repaired the WMI and re-installed the client its got updated.

    Definitely it could be because of the WMI it might have discovered and due the heartbeat it should have changed as no and delete aged discovery removed it i guess.

    Regards,

    Kamala kannan.c

    Monday, April 29, 2013 11:46 AM