Using the Subnet Criterion to Keep Installs from Occurring Over the WAN

Using the Subnet Criterion to Keep Installs from Occurring Over the WAN


August 21, 2000

Last week John Paesano had a great article on a wrapper to prevent this from happening. In my article I solve this problem from a different angle. 

If I'm concerned that a traveling laptop user may pull a particular install over the WAN I will use the Subnet criterion while building the collection that I'm advertising to.

When you build a query to add membership to your collection go to the Collecton Properties\Membership tab\Add a Query or edit one you have already created\Select Edit Query Statement. Then add an "AND  SystemResources.IPSubnets is equal to xxx.xxx.xxx.xxx (where xxx.xxx.xxx.xxx is your subnet or subnets).

If you  need some help creating collections based on queries take a look at some of my other articles at my home site. 

I've added the WQL below to help to clarify.

select SMS_R_System.ResourceID,SMS_R_System.ResourceType,SMS_R_System.Name,SMS_R_System.SMSUniqueIdentifier,SMS_R_System.ResourceDomainORWorkgroup,SMS_R_System.Client from SMS_R_System where OperatingSystemNameandVersion like "%Windows 98%" and SMSInstalledSites = "CXS" and (IPSubnets = "174.2.0.0" or IPSubnets = "174.2.1.0") order by Name.

There is no right or wrong way to solve this problem. John's method will allow a traveling laptop user to install a package while visiting another site (given the package resides at the new sites distribution point) but is a bit more complex than my method.