Software Update Compliance Report Doesn't List Results For All Collection Computers RRS feed

  • Question

  • Good Morning!

    This past weekend, I advertised a Software Update Group to a Collection containing 64 workstations.  The Collection only has one rule - to add all computers in a specific AD OU.

    After deployment, I ran the "Compliance 1 - Overall Compliance" report for initial results.  It reported that 24 machines were compliant, 10 were not, and 1 was unknown - equaling only 45 machines.


    1. Why did it not give a status for 64 machines?

    2. I found an example of one computer which was recently replaced whose updates didn't install.  Details are below

    I looked at one computer (the IT Director's) whose was recently replaced.  He received his new computer a couple of weeks ago and it had the same hostname as his old computer.  When building it, I do not believe his old hostname was deleted from AD - just overwritten when joined to the domain.

    In AD, his hostname was listed just once in an OU covered by the collection's rule.  In SCCM, though, his hostname is listed twice in All Systems - one reports the SCCM Client installed - one does not.  Also - his hostname is listed in the Collection I deployed to, but only the one that shows the client is NOT installed. How do I prevent this?

    Example of Above

    Example Hostname: WORKST55

    In AD Users & Computers, it's listed once under DOMAIN.COM\LOCATION\DEPARTMENT\COMPUTERS\LAPTOPS

    In the SCCM Admin Console, it has two entries in the "All Systems" Collection

    - Name: WORKST55  /  Client Type: None  /  Client: No  /  Site Code: ABC  /  Client Activity:  empty

    - Name: WORKST55  /  Client Type: Computer  /  Client: Yes  /  Site Code: ABC  /  Client Activity:  Active 

    Also in the SCCM Admin Console, it only has one entry in the Collection I made with the rule to add all computers in the DOMAIN.COM\LOCATION\DEPARTMENT\COMPUTERS\LAPTOPS OU

    - Name: WORKST55  /  Client Type: None  /  Client: No  /  Site Code: ABC  /  Client Activity: empty

    Note:  I also have the collection set to "Use incremental updates for this collection" if that makes a difference.

    So...  what happened?  Is this by design?  How can I fix this for the future?  Thanks!

    Ben K.

    Monday, August 27, 2012 3:41 PM


  • Since no else has replied, I recommend that you contact Microsoft Support (CSS), they should be able to help you out.


    Saturday, July 6, 2013 3:59 PM

All replies

  • Hi,

    I haven't actually tried reusing a computername in SCCM 2012 yet for new hardware, in SCCM this has always created a duplicate object as you are seeing now. I would recommend that you don't reuse computernames, that is definatly the easiest way to avoid these problems..

    For SCCM 2007 there are a log of solutions, one would be this script: http://blogs.technet.com/b/configmgrteam/archive/2011/09/09/known-issue-and-workaround-duplicate-records-when-you-use-unknown-computer-support-with-active-directory-delta-discovery.aspx

    I would start by searching the Status Messages for anything useful there as well.


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

    Monday, August 27, 2012 6:17 PM
  • Just bring up the properties of those duplicate ressources and check which discovery methods added them.
    Reinstalling an existing computer using CM12 should not result in duplicate records (compared to CM07 where dupes were created though). The compliance is only calculated for "client = yes" systems, so how many "real" clients are member of that collection?

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

    Monday, August 27, 2012 6:53 PM
  • Thanks - I just looked it all up and here are the answers...

    I'll use the same WORKST55 for example as it represents a real machine with the issue.

    - WORKST55 (Without client) was added by "SMS_AD_SYSTEM_DISCOVERY_AGENT"

    - WORKST55 (With Client) was added by "Heartbeat Discovery"

    I checked many of the listed hostnames and all that I checked had been added by "SMS_AD_SYSTEM_DISCOVERY_AGENT", too.  Should I just turn that discovery off, leave Heartbeat on, and configure maintenance to remove ones without heartbeats in the past 14 or 30 days perhaps?  What's the norm for people who don't have a perfectly kept AD?

    I did reconfigure some of the maintenance tasks from 90 days to 30 days which took a lot of the false positives out, but WORKST55 and many others remained.  

    Also - In the collection I created in the second part of my question which listed the old hostname, but not the new one, it still only shows the old name.  Below is the query I set up for the collection.

    select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.SystemOUName = "DOMAIN.COM/LOCATION/IT DEPT/IT COMPUTER ACCOUNTS"

    The "IT COMPUTER ACCOUNTS" OU contains 4 other OUs - Desktops, Laptops, Laptops Encrypted v8, and Laptops Encrypted v9.  The old WORKST55 is in the Laptops OU and the new one is in the Laptops Encypted v9 OU - still - only the old one is listed.  Shouldn't both old and new be?  Thanks!

    Ben K.

    Monday, August 27, 2012 7:10 PM
  • Yes, I know this is an old post but I’m trying to clean up old posts.

    Did you figure this out?


    Saturday, December 29, 2012 9:29 PM
  • Since no else has replied, I recommend that you contact Microsoft Support (CSS), they should be able to help you out.


    Saturday, July 6, 2013 3:59 PM