Close Menu
    Facebook X (Twitter) Instagram
    Sunday, October 12
    X (Twitter) LinkedIn Reddit RSS
    All about Endpoint Management
    • Home
    All about Endpoint Management
    Home»Collections»Membership Rules-Query Vs direct-based

    Membership Rules-Query Vs direct-based

    Eswar KonetiBy Eswar KonetiJuly 02, 10:40 am2 Mins Read Collections 3,690 Views
    Share
    Facebook Twitter LinkedIn Reddit

    Query based versus Direct membership:

    Direct membership rules should be created when you want to target a very specific user or SMS client. Direct membership rules are not automatically updatable; therefore, any change of targeted resources is a manual process. If a targeted resource(workstation) is removed from the site database, the associated direct membership rules will be deleted from all collections. For example, if the workstation ESKON00 is a resource, and ESKON00 ages out of the site database(removed) for any reason, all direct membership rules referring to ESKON00 will also be Deleted. If ESKON00 is later rediscovered or inventoried, the direct membership rules must be recreated. For this reason, static membership rules should be used for focused, short-term distribution efforts only.
    Query-based rules use a proprietary language known as WQL to pull information from the SMS Administrator console’s site database connection into a readable format. WQL is a subset of the SQL database language that allows for basic operations only through the SMS Administrator console. It supports select statements with the where and from clauses, as well as basic joins. Please note that WQL is used for queries from the SMS Administrators console only. Reports are written in the native SQL language. The SMS Administrator console handles conversion of WQL to SQL when contacting the site database, and returns formatted results.

     Queries should dynamically update to take full advantage of their capabilities. A component Called Collection Evaluator runs as part of the SMS service on site servers. This component updates collection membership on a schedule specified by administrators (daily by default). Because collections with only direct membership rules do not require dynamic updates, they should not be scheduled for reevaluation. Collections with query-based rules should be scheduled to update on an interval appropriate for their purpose. For example, it might be desirable to have a collection responsible for deploying security patches to newly created machines updated on a very frequent basis. Alternatively, a one-time distribution of an advertisement might require only manual updates.

    More information can be found here

    collection quiries Collections Membership Rules-Query Vs direct-based SCCM 2007 what is sccm 2007 query based and direct based rules
    Share. Twitter LinkedIn Email Facebook Reddit

    Related Posts

    SCCM report list collections with no deployments

    December 05, 12:04 pm

    Tool for managing the import and export of SSRS report – ReportSync Tool

    October 27, 9:10 pm

    Investigating SCCM Client Policy Request and Communication Status with a Collection Specific Report

    October 15, 11:22 pm

    1 Comment

    1. Rajashekar on February 8, 2011 7:27 AM

      Its nice.

      Reply

    Leave a ReplyCancel reply

    This site uses Akismet to reduce spam. Learn how your comment data is processed.

    Sign Up

    Get email notifications for new posts.

    Author

    I’m Eswar Koneti ,a tech enthusiast, security advocate, and your guide to Microsoft Intune and Modern Device Management. My goal? To turn complex tech into actionable insights for a streamlined management experience. Let’s navigate this journey together!

    Support

    Awards

    Archives

    © Copyright 2009-2025 Eswar Koneti, All rights reserved.

    Type above and press Enter to search. Press Esc to cancel.