- Remove From My Forums
Question
Hi Everyone,
I've created my Boundaries and a Boundary Group.
But I see that the "Default-Site-Boundary-Group is automatically created, and it's almost all option are grayed out.For what is that?
Cheers
All replies
Hello
The client uses fallback to the default site boundary group as a safety net for content that is not available from any other location.
Regards, Regin Ravi
- Proposed as answer by Wednesday, February 8, 2017 8:43 AM
Hello Ravi,
Thanks for the answer.
But when I open the Default Site Boundary Grup, under Boundaries it's empty [and grey].
So the Default-Site-boundary_group is only for fallback [It's new in 1610?]Cheers
Yes it is
Regards, Regin Ravi
It will create automatically. You can't edit anything. The use of this when no DP found it fall on this boundary network
- Proposed as answer by Gokulnatharavind Wednesday, February 8, 2017 8:54 AM
While we're at it, I noticed this new default "Boundary Group" option this morning. I have another question regarding the now deprecated "Slow/Fast link" boundaries. What has replaced the slow link? If you want to deploy a script or small a package on a certain VPN subnet that was flagged as slow link, how does it work now? You could select this in the application/packages before... what is the other option now?
What is replacing Slow Link?
- Edited by HEALTH_DISCO Monday, January 9, 2017 8:33 PM
Configurations for Fast or Slow are removed since current branch 1610. You are no longer able to configure individual distribution points to be fast or slow. Instead, each site system associated with a boundary group is treated the same. Because of this change, the References tab of the boundary group properties no longer supports the configuration of Fast or Slow.
You can also see the changes in the deployment wizard pages. However, a copy is made of each existing boundary group that includes a site server configured with a slow connection. The name of the new group is -.
Detailed information are on the official document below for content locate/fallback capacity:
//docs.microsoft.com/en-us/sccm/core/servers/deploy/configure/define-site-boundaries-and-boundary-groups
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact .- Edited by Frank Dong Tuesday, January 10, 2017 10:56 AM
- Proposed as answer by Frank Dong Wednesday, February 8, 2017 8:43 AM
- CTGlobal Home
Default Site-Boundary-Group and boundaries
The purpose of the Default Site-Boundary-Group is to service clients that are not served by any other boundary group [that being local boundary group or neighbor boundary group]. However in ConfigMgr 1610 there has been some confusement around the fact that you can add boundaries to the Default Site-Boundary-Group . I’ve been asked a couple of times if we should add all boundaries to the Default Site-Boundary-Group since the group is automatically configured for Site assignment.
My take on that is NO, don’t use the Default Site-Boundary-Group as you don’t really control it. You will also notice that you can’t add boundaries to the group [from within the boundary group].
However if you right click a boundary in ConfigMgr 1610, select Add Selected Items to Existing boundary Groups, then you are able to add the boundary!
Now, with this knowledge you have found a way to include all your boundaries to the Default Boundary group – but stop! Don’t think that’s a valid path. Instead create a new boundary group, add your boundaries and configure that for site assignment.
Changes in ConfigMgr 1701
In the latest ConfigMgr TP 1701 the ability to add boundaries to the Default Site-Boundary-Group is removed
So what should be added to the Default Boundary group?
In my opinion, a “fallback distribution point” and from ConfigMgr 1701 TP also a “fallback Software Update point”. That way clients without a managed boundary will still have site systems that can manage them.
Share This Story, Choose Your Platform!
Microsoft Regional Director, Enterprise Mobility MVP. Microsoft Certified Trainer and Principal consultant. I have been working with Enterprise client management since 1992. Co-founder of System Center User Group Denmark in 2009. Certified MCITP: Enterprise Administrator, MCSA+Messaing, and much more. Member of: Microsoft Denmark System Center Partner Expert Team The Danish Technet Influencers program System Center Influencers Program.
Beslægtede indlæg
Der er lukket for kommentarer.