Search the Community

Hi All, I have a question about how to best implement boundaries for the purposes of Content Locaation and Site Assignment. We have 4 sites, say A,B,C & D. Should I create 4 separate boundaries for A,B,C & D and then put them into one Boundary Group for Site Assignment? Then create boundary groups using IP Address Ranges (Auto-discovered) for Content Location? We only have the one primary site so I'm just confused about these boundary groups and am trying to prevent any overlaps. If I were to use the IP Addresses strictly, then I would end up with boundary groups with overlapping boundaries (using same IP address ranges) <- hope that makes sense. I've read up on a few blogs including http://myitforum.com/myitforumwp/2012/08/02/secondary-sites-and-boundary-groups/ and http://blogs.technet.com/b/elie/archive/2012/05/14/system-center-2012-configuration-manager-part3-boundaries-and-boundary-groups.aspx but I still don't quite understand. Thanks Guys! Jon

Hi, I was just wondering if there is a best practice use of Content Location field when creating new applications. I had an install of Smartstream I was doing and copied some files from our finance server to my source directory and created my application. The problem I found is that the program has some links back to the install directory which was now C:\ccmcache instead of the finance server network share. Also finance do their own patching and modify some of the source files on the network location which will automatically patch their client. Generally the install was done with a .bat file just pointing at the installer on the network share. So this time I created an application and didn't set a content location, pointed the command line at the installer and provided the network share as the start in field. Everything installed fine. So my question is what is the "best practice" for installing apps. Is this legit way of doing things or is it intended that we already download source files to ccmcache? Cheers,