Quick if silly sounding question about setting the site boundaries. When setting a site boundary of an IP subnet, does SCCM assume a mask of 255.255.255.0, or will it be aware of ALL IPs on a NNN.NNN.NNN.0 subnet, even if the subnet mask is 255.255.255.240, or 255.255.255.128, etc. I've never given it much thought before, but for whatever reasons, the customer I'm dealing with has several subnets which are masked so that they get several subnets for a single range. for instance a subnet of 195.206.140.0 may be masked at 255.255.255.128. Thus even though you can have several subnets within that masking, you still effectively only get nnn.nnn.nnn.1 to nnn.nnn.nnn.254 available IP addresses. they just will be on different subnets. So, in this case. will I have to use an IP range, or can I just use the .0 subnet setting? Thanks for any help. (Posting this in myITforum as well)

ConfigMgr doesn't use masks, it uses network IDs. Thus "supernetting", or more accurately aggregate subnets, do not work as expected. When in doubt, use IP ranges.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

Thanks Jason. It's what I thought, but wasn't exactly sure. I know if you enter a .0 for the "subnet" entry under the boundary page it will cover every IP address on that subnet, however, when informed that many of the .0 subnets were actually aggregates, I got concerned that SCCM would only see the 15 (or however many) that were associated with that "slice" of the subnet range. I've been entering in IP ranges for that very reason, but wanted to be sure I wasn't missing something.