Resources for IT Professionals >
System Center Configuration Manager Forums
>
Configuration Manager Admin Console
>
Query based collection that displays Distribution Points.
Query based collection that displays Distribution Points.
- Here is the query I have setup:
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.SystemRoles = "SMS Distribution Point" and SMS_R_System.OperatingSystemNameandVersion not like "Microsoft Windows NT Server%"
It works well, however it displays distribution points that have the role removed.
How do I remove the "SystemRole" from computers that are no longer being used as distribution points and have been removed from the "site system" node?
Answers
- Sorry for the extremely late response.
I went about creating the collection a different way. I made the collection a direct membership collection and exported the list from site systems.- Marked As Answer bywerknhrd Thursday, January 28, 2010 4:04 PM
All Replies
- The result is based on information in the db, not on the SP. You have to make sure a hardware discovery cycle has been run since you removed the role before this change will be reflected in the report.
- I am finding pc's in the collection that have had the role removed for several weeks now (hardware discovery, set to once a week).
- I would assume this comes from WINNT Server Discovery. The next time that discovery method runs (which is an automatic dscovery method, you have no control over it) that would clean it out. However, you said it has been weeks now, that method runs weekly.
Of course, you could delete the discovery record from a collection (be careful, this removes *all* data for that system - discovery, inventory, and status), and then when it is next discovered, such as from Heartbeat Discovery or an inventory process (will take a couple of cycles if it has been deleted), it should report in without the role.
Wally Mead - Our infrastructure is Server 2003.
With that being the case, the only way to resolve this is to manually delete the computers from SCCM, wait until it is re-discovered and re-install the client? - With Wally's approach you don't have to uninstall the client. Just delete the computerobject from sccm and wait for the next discovery cycle.
- Great. I will give this a try.
I appreciate everyone's response. - Did you try, and did it work? If so, it is always requested that you update the forum so we all know the answer, and can see that the thread has been answered.
Wally Mead - Sorry for the extremely late response.
I went about creating the collection a different way. I made the collection a direct membership collection and exported the list from site systems.- Marked As Answer bywerknhrd Thursday, January 28, 2010 4:04 PM
