IP Subnet Boundaries = Evil
I saw Jason’s post on this, and had to agree…IP Subnet Boundaries in Configuration Manager are indeed evil. Use IP Range boundaries instead!
Definitely check out Jason’s post for full info.
Share this:
- Click to share on Facebook (Opens in new window) Facebook
- Click to share on X (Opens in new window) X
- Click to share on Pinterest (Opens in new window) Pinterest
- Click to share on LinkedIn (Opens in new window) LinkedIn
- Click to share on Reddit (Opens in new window) Reddit
- Click to share on Tumblr (Opens in new window) Tumblr
- Click to email a link to a friend (Opens in new window) Email
Related
June 8, 2012 - Posted by Jarvis | Uncategorized
2 Comments »
Leave a comment Cancel reply
-
Recent Ramblings
- Chess Board
- An urn for my friend
- Building a Hammered Dulcimer–Take 2
- Building a Hammered Dulcimer
- Choose to Love
- New Blog on Hackers and End of Life Products
- Windows 10 Cisco AnyConnect Issue
- Another Windows 10 / OneDrive Issue
- Windows 10 OneDrive Bug
- Windows Phone 8.1 Update Oddness
- Traveling With My Surface 2
- A Hypothetical Future of SCCM
- Windows 8.1–Initial Impressions
- No–Windows 8 Does Not Suck
- Trust Google? No Thanks.
Top Posts

Subscribe
-
Categories
Recent Comments
Realm Index
Disclaimer
The postings on this site are my own and don’t necessarily represent my employer’s positions, strategies or opinions.

I still think AD Site boundaries are ideal, but only in a well managed environment.
I don’t disagree..but there are just so few well managed environments…or at least AD is not designed in such a way that it works well for SCCM sites/boundaries.
Forest Discovery and the auto boundary creation in SCCM 2012 rocks though! All you have to do is manage boundary groups at that point.