When creating custom discovery data using the smsresgen class there is no way to remove this from the discovery related tables in ConfigMgr. Since there is a supported way to add this data, there should be a supported way to remove it. This is necessary as a rollback option, to return ConfigMgr to its default state, before the custom discovery data was added.63 votes
When System Discovery finds an object that seems invalid, currently it won`t be imported (which is good).
ERROR: System <systemname> is a unsupported operating system, unsupported version, or malformed AD entry. Reported system type is: ().
However if the same object has an AD Group Membership and AD Group Discovery finds it, it won't check if it is valid, but write the DDR and create the object record in SCCM DB.
Please change AD Group Discovery so it validates new objects too.36 votes
It would be great if we could exclude certain OS's from discovery. I have over 5500 machines in my DB that I couldn't care less about but they reside in an OU where I have machines I do care about.3 votesNoted · AdminAdam Meltzer (ConfigMgr Product Team) (Software Engineer, Microsoft Endpoint Configuration Manager) responded
Reopened and updated title for clarity
If I import a new computer using its MAC Address but later I install manually the client in the actual computer, two resources with the same name end up in the SCCM Database.
An option to make the default action merging both resources or just associating the client DDR to the manual import.0 votes
- Don't see your idea?