locked
About Computer is not there in AD but there is in SCCM RRS feed

  • Question

  • Hello guys,

    I check my Active Directory and was excluded computerXXX. In SCCM was excluded manually computerXXX, but after 10 minutes this computer back again and I can see it in console SCCM.

    Delete Aged Discovery Data Task is configured OK.In my DNS I don't have any data about computerXXX.

    Why occur this? How to solve this issue?

    In my adsysdis.log I can't see the computerXXX then I understand this computer don't have display in SCCM.

    Any idea?

    Thanks a bunch!



    • Edited by Curious_007 Monday, April 28, 2014 2:27 PM Add info.
    Monday, April 28, 2014 2:24 PM

Answers

  • Well the client computer isn't contact with my MP, because it not in my environment AD and SCCM. I excluded this machine.

    This will NOT stop the PC from contacting the MP. The PC would be consider a workgroup PC.


    http://www.enhansoft.com/

    • Marked as answer by Curious_007 Tuesday, April 29, 2014 1:03 PM
    Tuesday, April 29, 2014 12:50 PM

All replies

  • How did you "exclude" that PC in AD and ConfigMgr?
    Have you already brought up the properties of XXX in ConfigMgr and checked which agent added that resource?

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

    Monday, April 28, 2014 3:03 PM
  • Is the CM12 client installed on this PC?

    http://www.enhansoft.com/

    Monday, April 28, 2014 3:10 PM
  • I excluded this computer in Active Directory normally, right click and deleted.

    I don't understand this: "checked which agent added that resource" . What are resources you say? Sorry I don't understand really.

    Yes CM12 client installed on PC, but it there isn't more in my environment, was excluded.

    Thank's yours opinion.

    I hope solve this issue.

    Thanks again.

    Monday, April 28, 2014 3:19 PM
  • If the CM12 client is installed on it, it will report to CM12, even if you have removed it form AD or "excluded" it. You will need to move the CM12 client from that PC to have it not report to CM12 site server.

    http://www.enhansoft.com/

    Monday, April 28, 2014 3:22 PM
  • Jones, I think is not necessary uninstall CM12 client because this computer don't have more contact with my environment SCCM, because it was deleted.

    Maybe I'm not expressing myself correctly,because, when I deleted any other desktop first in AD second in my environment SCCM this not display for me anymore in SCCM, in others words I deleted and OK.

    Now I have a problem with some machines, because I do same process said up and 10 minutes the desktop back display in my console SCCM.

    Really I don't understanding what's cause this.

    Do you have another idea?

    Thanks!

    Monday, April 28, 2014 3:52 PM
  • Post a screenshot of the computer visible in your ConfigMgr console. Also double click the computer within ConfigMgr console and let us know the name of the discovery agent.

    Kindly mark as answer/Vote as helpful if a reply from anybody helped you in this forum. Delphin

    Monday, April 28, 2014 4:20 PM
  • First, when did you remove the computer from AD? did you wait for AD replication?

    Did you configured "Discover object within AD group"?

    Try to remove that and see if it solve your issue.


    Please take a moment to Vote as Helpful and/or Mark as Answer where applicable. Thanks.

    Monday, April 28, 2014 4:34 PM
  • Jones, I think is not necessary uninstall CM12 client because this computer don't have more contact with my environment SCCM, because it was deleted.

    This is not correct. If the CM12 client is installed on the PC it WILL show up again at the next Heartbeat discovery or HW inventory.

    http://www.enhansoft.com/


    • Proposed as answer by Narcoticoo Monday, April 28, 2014 7:47 PM
    • Edited by Garth JonesMVP Tuesday, April 29, 2014 12:14 PM typo
    Monday, April 28, 2014 4:43 PM
  • Post a screenshot of the computer visible in your ConfigMgr console. Also double click the computer within ConfigMgr console and let us know the name of the discovery agent.

    Kindly mark as answer/Vote as helpful if a reply from anybody helped you in this forum. Delphin

    Follow:

    This desktop only "MP_ClientRegistration".

    Others desktops have: SMS_AD_SYSTEM_DISCOVERY_AGENT,Heartbeat.

    Any idea?Thanks

    Tuesday, April 29, 2014 12:07 PM
  • "MP_ClientRegistration" is because the CM12 client is installed on the PC.

    http://www.enhansoft.com/

    Tuesday, April 29, 2014 12:13 PM
  • First, when did you remove the computer from AD? did you wait for AD replication?

    Did you configured "Discover object within AD group"?

    Try to remove that and see if it solve your issue.


    Please take a moment to Vote as Helpful and/or Mark as Answer where applicable. Thanks.

    Yes I wait replication AD, actually I wait more 24 hours.

    Discover objects within AD groups is not marked.

    Thanks your opinion. Any other idea?

    Tuesday, April 29, 2014 12:17 PM
  • As Garth Jones mentioned above twice, the client registered itself on SCCM server. uninstall the client will solve your issue.

    Please take a moment to Vote as Helpful and/or Mark as Answer where applicable. Thanks.

    Tuesday, April 29, 2014 12:18 PM
  • How is possible? If heartbeat discovery not discovery this machine I think don't have reasons this happen.

    Because I have problem only some machines, others machines I excluded and are OK, not display in my console SCCM.

    Thanks Jones, I still want understand because some machines have the situation I said.

    Thanks.

    Tuesday, April 29, 2014 12:19 PM
  • Yup.. You need to uninstall ConfigMgr client from that computer..


    Kindly mark as answer/Vote as helpful if a reply from anybody helped you in this forum. Delphin

    Tuesday, April 29, 2014 12:21 PM
  • http://technet.microsoft.com/en-us/library/gg712308.aspx#BKMK_HeartbeatDisc


    Please take a moment to Vote as Helpful and/or Mark as Answer where applicable. Thanks.

    Tuesday, April 29, 2014 12:24 PM
  • How is possible? If heartbeat discovery not discovery this machine I think don't have reasons this happen.

    Because I have problem only some machines, others machines I excluded and are OK, not display in my console SCCM.

    Thanks Jones, I still want understand because some machines have the situation I said.

    Thanks.

    Why do you think Heartbeat discovery is not discovering this PC?

    You can clearly see from your screenshot this the client is registering with CM12. This is normal behavior. if you want to solve this remove the CM12 client form the PC.


    http://www.enhansoft.com/

    Tuesday, April 29, 2014 12:30 PM
  • http://technet.microsoft.com/en-us/library/gg712308.aspx#BKMK_HeartbeatDisc


    Please take a moment to Vote as Helpful and/or Mark as Answer where applicable. Thanks.

    Thanks Idan, but this line say:

    Heartbeat Discovery is the only discovery method that provides details about the client installation status by updating a system resource client attribute that has the value Yes. To send the Heartbeat Discovery record, the client computer must be able to contact a management point

    Well the client computer isn't contact with my MP, because it not in my environment AD and SCCM. I excluded this machine.

    Thanks again.

    Tuesday, April 29, 2014 12:35 PM
  • What do you mean "Exclude"? how did you exclude?

    If the client have network access (ping) to the server, it will register itself.


    Please take a moment to Vote as Helpful and/or Mark as Answer where applicable. Thanks.

    Tuesday, April 29, 2014 12:38 PM
  • What do you mean "Exclude"? how did you exclude?

    If the client have network access (ping) to the server, it will register itself.


    Please take a moment to Vote as Helpful and/or Mark as Answer where applicable. Thanks.

    First I deleted in my AD, second in my environment SCCM. No, the client don't have network access, it not in my DNS, AD, SCCM. This machine don't have more any communication with my AD or SCCM, because I say don't understand this reasons computer still display in my console SCCM.

    Thanks Idan.

    Tuesday, April 29, 2014 12:44 PM
  • Well the client computer isn't contact with my MP, because it not in my environment AD and SCCM. I excluded this machine.

    This will NOT stop the PC from contacting the MP. The PC would be consider a workgroup PC.


    http://www.enhansoft.com/

    • Marked as answer by Curious_007 Tuesday, April 29, 2014 1:03 PM
    Tuesday, April 29, 2014 12:50 PM
  • Well the client computer isn't contact with my MP, because it not in my environment AD and SCCM. I excluded this machine.

    This will NOT stop the PC from contacting the MP. The PC would be consider a workgroup PC.


    http://www.enhansoft.com/

    Jones, OK I understand your opinion. There is some wrong this machine as I said deleting desktop AD and SCCM, DNS, I can't ping this machine. in the field "Last Activity" in SCCM say 04-29/today.

    Maybe only rename this machine before delete it in AD. Maybe this happen or no, I don't know.

    Tuesday, April 29, 2014 12:55 PM
  • Jones, OK I understand your opinion. There is some wrong this machine as I said deleting desktop AD and SCCM, DNS, I can't ping this machine. in the field "Last Activity" in SCCM say 04-29/today.

    Maybe only rename this machine before delete it in AD. Maybe this happen or no, I don't know.

    At this point I recommend that you contact CSS (MS Support) directly for support.


    http://www.enhansoft.com/

    Tuesday, April 29, 2014 12:58 PM
  • Just uninstall the client from the affected machine by running %windir%\ccmsetup\ccmsetup.exe /uninstall

    Tuesday, April 29, 2014 2:52 PM