Hello all, my name is Kevin Zaner and I’m a long time trainer (18 years now) for
a variety of Microsoft products, (including SMS/SCCM and MOM/SCOM), VMWare ESX,
and a few other technologies thrown in once in awhile.
Over the years I have met many people in this industry, maybe even some of you reading
this! I will be updating and responding to this blog on a regular basis regarding
the System Center products, VMWare, or whatever happens to trip my trigger that
day. Please feel free to respond, suggest topics, etc. My goal is for this to be
a place where likeminded technical professionals can rant, give and receive advice,
or just tell us about your golf game. Happy Blogging
SCCM Boundaries
Tags:
While there are many new features and overall changes to SCCM (compared to SMS 2003), one change that doesn't seem to get much press is the site boundaries. As you may know, in '03 boundaries were defined as ip subnets or AD sites. Roaming boundaries (local or remote) were defined as ip subnets, ip ranges, or AD sites. For roaming to work globally boundaries defined in one site would/should be added to a any other site's a client may roam to as roaming boundaries. This 'overlapping' of boundaries was standard practice.
In SCCM boundaries are defined as 'fast' or 'slow' and can be ip subnets, ip ranges, AD sites or IPv6 prefixes. And ANY 'overlapping' boundaries produces unpredictable results. This will be a challenge in upgrades and planning scenarios.. What do you think?