Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Package Distribution- Using SMS to Target the Proper SMS Clients: COLL

Status
Not open for further replies.

Jpoandl

MIS
Jun 23, 2000
2,008
US
I'm having trouble using SMS to target package distribution to my client machines. It is easy for me to create custom dynamic collections but using them to target my machines is becoming a problem.

I think my problem is related to filtering a collection.

For example, say I want to run a package (that reboots the machine) on all systems using Internet Explorer 5.5 with SP2. But I also need to avoid running this package on 80 SMS client machines because they are high visibility IIS servers and other important application servers.

1) I can create a SQL query to contain all SMS clients running IE 5.5 w/SP2. I can even create an SMS collection based on this SQL query.

2) I can also create a collection using MAKECOLL.exe to create a collection of the 80 servers that I can not deploy the SMS package to...do to management declaring these servers high visibility and important application servers, etc so I must skip these (filter these systems out.)

However, I don't know if there is a way to Build a Collection based on the SQL query but also subtracting the 80 servers Collection. (i.e. SQL Query with filter based on another Collection.)

My goal is to create dynamic queries in SMS (because systems are added and subtracted all the time) and the filter these queries or collection on a Direct Membership static list of high availability servers.

Is there any way to do this? Or am I approaching this the wrong way? Any help would be greatly appreciated.

Thank you,




Joseph L. Poandl
MCSE 2000

If your company is in need of experts to examine technical problems/solutions, please check out (Sales@njcomputernetworks.com)
 
Well it sounds like a two fold appraoch and I beleive your
correct in building a seperate collection for servers only.

Once you have these broken out into it's own group you may
want to distribute your packages, updates, etc.. and limit the push to that particular collection.

There are more granular controls I have yet to drill through, however this is the way I'm able to push out code while avoiding servers.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top