_____________________________________________________________Please consider voting for these ERs:Provide Better Pre/Post LDMS Patch/Sp/.0 Information To The CommunityCumulative Patch List for LANDesk ProductsQuery Builder ImportProvide bulk client deletions without carpal tunnel syndrome.Core Synchronization Allow Mirror functionality from Master Core
- Create a separate client configuration for these devices and uncheck Software Distribution in the client config GUI first screen. Think about this since you may want to selectively push to these machines in the future.
- Find a discerning feature about these machines and create a query excluding these machines based on this feature (e.g., all in the same OU, similar computer name, custom registry key - you can create, software package, etc...). You can use this as as a preq. query for distro packages or the target query. Prereq queries will be good since it does not mater what the target is they will be excluded.
- If you can't find any commonality use the Query Builder to import the list to create an exclusion query.
To add to what ZMAN suggested, when you create a new agent for them, make the agent something that stands out, and you can use that for the query to filter by... also, depending on who needs access to these systems, and for what, you can use scoping to reduce what can be done to these system and by whom.
As a best practice I would recommend using queries to target tasks as well, not just a simple drag and drop.
I create a custom field for groups of computers. On these computers I create a registry value called Config Type. In it I store a value for the different types of computers I have to manage in different ways (User, Lab, Shared, Kiosk, etc). I can now query on this field to include or exclude groups of computers.