How to remove the Null Entries from SCCM

  • Run this query select SYS1.ResourceID,SYS1.ResourceType,SYS1.Name,SYS1.SMSUniqueIdentifier,SYS1.ResourceDomainORWorkgroup,SYS1.Client from SMS_R_System as sys1 inner join SMS_R_System as sys2 on sys2.NetbiosName = sys1.NetbiosName where (sys1.ResourceId < sys2.ResourceId) to find system with null entries
  • Run this query Select R.ResourceID,R.ResourceType,R.Name,R.SMSUniqueIdentifier,R.ResourceDomainORWorkgroup,R.Client from SMS_R_System as r full join SMS_R_System as s1 on s1.ResourceId = r.ResourceId full join SMS_R_System as s2 on s2.Name = s1.Name where s1.Name = s2.Name and s1.ResourceId != s2.ResourceId and R.Client = null to find system with Null Entries in the console having properties with values "blocked=Null,Client Type=Null,Obsolete=Null,Active=Null" moreover their Hardware id Null System UUID is null and SMS unique identifier is null.

Resolution: These are not obsolete clients, they are what we call “timing issue records” this happens when a PC registers in AD and AD discovery find them before the same PC submits its data to the MP. Really your only option is the delete the AD discovery record ones.

SoYou cannot vote on your own post stretch the AD discovery time to 1 day, That probably can make a difference.

Comments

Popular posts from this blog

The install4j wizard could not find a Java Runtime Environment on your system. Please locate a suitable JRE...

Clients Unable to update - "Cached cookie has expired or new PID is available"

Java Control Panel Icon "Application Not Found"