locked
Boundaries and Boundary Groups - 300 Physical locations RRS feed

  • Question

  • Hey guys -

    I'm going to be deploying 300 or so Pull DP's across our environment.  For the most part, it's one Pull-DP per physical location, with very little overlap.  Only one site.

    Based on what I'm reading, I'll need 300 Boundaries and 300 (seemingly identical) Boundary Groups, with one boundary per group.  Am I getting this right?  It doesn't seem that the new "Boundary Groups" really offers any benefits to us, unless I am missing something; it's simply extra work for us.

    Please correct me if I'm wrong though, and thanks!

    Monday, March 24, 2014 2:49 PM

Answers

  • Sounds accurate to me.

    John Marcum | http://myitforum.com/myitforumwp/author/johnmarcum/

    Monday, March 24, 2014 2:54 PM
  • Hi,

    You are correct you need a Boundary and a Boundary Group per Pull DP. Boundary groups makes it possible to use a boundary for Site assignment or Content location and you can reuse the boundaries created.

    Regards,
    Jörgen


    -- My System Center blog ccmexec.com -- Twitter @ccmexec

    Monday, March 24, 2014 2:57 PM

All replies

  • Sounds accurate to me.

    John Marcum | http://myitforum.com/myitforumwp/author/johnmarcum/

    Monday, March 24, 2014 2:54 PM
  • Hi,

    You are correct you need a Boundary and a Boundary Group per Pull DP. Boundary groups makes it possible to use a boundary for Site assignment or Content location and you can reuse the boundaries created.

    Regards,
    Jörgen


    -- My System Center blog ccmexec.com -- Twitter @ccmexec

    Monday, March 24, 2014 2:57 PM