Thread: Quick SMS Question

If anyone else uses SMS during their job, maybe they can answer me this. What the hell is the point of making 2 rules, when it seems more like an "or" Statement. Basically if a Computer Fits into Rule #1 but fails Rule #2 it still gets in. I'd like to keep my stuff separated down as far as possible so I can understand what I'm doing but I can't seem to get it to cooperate when I'm making multiple rules and have to stuff a bunch of "And" statements into just one rule.

Maybe I'm doing something wrong, or maybe its functioning the way its supposed to....

Anyways a quick example would be Rule A, Stating you have to be in a certain Naming Convention.
While Rule B states that you have to be in a certain IP Range.

I wish I could answer your question myself but I don't get involved with the mechanics of the SMS config in our environement as I manage the team that does that. But if I don't see an answer here I'll ask my guys and get back with you.

I believe it has to do with inner and outer joins on tables. It confuses the hell out of me too. If you're an Excel person, you're used to working with data in a certain fashion and SMS does not work that way. SMS uses it in a completely different fashion (relational tables like Access).

I'm trying to find the explanation I wrote up for one of my staff but I can't find it yet. I'll post it when I do.

This isn't the explanation I used since I can't find it but here I go trying to explain something I barely understand.

Imagine that you have one table (or excel spreadsheet) with computer names and some other information. Now imagine that you have another table (or excel spreadsheet) with the IP address and other information. When you use AND, it's going through the first table and giving you the results. It's also going through the second table and giving you that information. If you used the same table in SMS, I believe it would just give you results like you'd expect.

What you need to do is run a query that collects all the information from the first table and then takes that and runs the second query on the results of the first query results. This would give you your subset of information.

OK, I found an example and I've got the query statement for you. Basically, this checks add remove programs and returns and computer that has BOTH Office 2003 installed and any Office 2007 program.

So the first part returns all the Netbios names for all the computers with one of the following: "Microsoft Office SharePoint Designer 2007", "Microsoft Office Visio Professional 2007", "Microsoft Office Professional Plus 2007", "Microsoft Office Project Professional 2007"

Then it (because of the select distinct), looks through only that list of computers with those netbios names Add/Remove programs for "Microsoft Office Professional Edition 2003" and returns only those. I think I was wrong in my earlier post about the table idea.


select SMS_R_System.* from SMS_R_System inner join SMS_G_System_ADD_REMOVE_PROGRAMS on SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceID = SMS_R_System.ResourceId where SMS_R_System.NetbiosName in (select distinct SMS_R_System.NetbiosName from SMS_R_System inner join SMS_G_System_ADD_REMOVE_PROGRAMS on SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceID = SMS_R_System.ResourceId where SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName in ( "Microsoft Office SharePoint Designer 2007", "Microsoft Office Visio Professional 2007", "Microsoft Office Professional Plus 2007", "Microsoft Office Project Professional 2007" )) and SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName = "Microsoft Office Professional Edition 2003"