All systems inadvertently targeted for an advertisement after modifying a collection in System Center Configuration Manager 2007

All systems inadvertently targeted for an advertisement after modifying a collection in System Center Configuration Manager 2007

  • Comments 1
  • Likes

KBJust a heads up on a new ConfigMgr 2007 Knowledge Base article we published today.  If you do any work with query based collections, and who doesn't, then you'll want to check this one out:

=====

Symptoms

All systems show in a collection after removing the criteria from a query for a query based collection in System Center Configuration Manager 2007.

Cause

Removing the criteria in the query for a query based collection removes the from statement from the query and leaves only the select statement. This causes all systems to be added to a collection that may already have an OSD or other advertisement targeted to it.

Resolution

If you need to modify an existing query based collection, delete the existing query and create a new one instead.

=====

For the latest version of this article see the link below:

KB2471057 - All systems inadvertently targeted for an advertisement after modifying a collection in System Center Configuration Manager 2007

J.C. Hornbeck | System Center Knowledge Engineer

The App-V Team blog: http://blogs.technet.com/appv/
The WSUS Support Team blog: http://blogs.technet.com/sus/
The SCMDM Support Team blog: http://blogs.technet.com/mdm/
The ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
The SCOM 2007 Support Team blog: http://blogs.technet.com/operationsmgr/
The SCVMM Team blog: http://blogs.technet.com/scvmm/
The MED-V Team blog: http://blogs.technet.com/medv/
The DPM Team blog: http://blogs.technet.com/dpm/
The OOB Support Team blog: http://blogs.technet.com/oob/
The Opalis Team blog: http://blogs.technet.com/opalis

clip_image001 clip_image002

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • Any SMS/SCCM worth their salt has been aware of this issue for years! We've all made the mistake at least once!