locked
Effect of Boundary Groups RRS feed

  • Question

  • I've asked this before in a different way and received an answer but I want to ask more concisely and confirm it before I move forward.  We're migrating from 2007 to 2012.  Currently all devices have 2007 client installed and are managed by our 2007 Site. 

    In our 2012 environment I've got Boundaries set up but no boundary groups.  Discovery Methods are enabled and devices are present as expected.  (Client Type=none, Client=no, Site Code=" ")  Client Push is NOT enabled. 

    When I enable Client Push Installation will 2012 push the 2012 client to the devices in the defined Boundaries or will it only push to devices that are defined in Boundary Groups, once I create them? I need to test the implementation and want to make sure that having Boundaries configured will not allow a Client Installation.  Also, what does creating the Boundaries do, other than making them available for Boundary Group assignment?

    You time and patience is greatly appreciated.

    Dino


    Thanks, Dino

    Monday, July 29, 2013 4:23 PM

Answers

  • Thanks for the clarification, Torsten! I was under the incorrect impression that the assignment was only important after the push had started on the discovered device. Nash

    Nash Pherson, Senior Systems Consultant
    Now Micro - My Blog Posts
    <-- If this post was helpful, please click "Vote as Helpful".

    • Marked as answer by ingram59 Wednesday, July 2, 2014 6:59 PM
    Wednesday, July 31, 2013 12:24 PM

All replies

  • Hi Dino,

    First thing to understand - Boundaries do absolutely nothing unless they are part of a boundary group.  Boundary Groups can be used for Site Assignment and/or for Content Location (picking Distribution Points).

    Regarding Automatic Client Push in ConfigMgr 2012, this feature will try to do a Client Push to all devices that have been discovered.  This doesn't directly interact with Boundary Groups, although they will come into play once the client is installing and trying to find what site to join (such as when you use the SITECODE=AUTO parameter).

    > "I need to test the implementation and want to make sure that having Boundaries configured will not allow a Client Installation."  Boundaries do not allow or disallow client installation. 

    I suggest that you plan to leave Automatic Client Push turned off until after you have completed your testing and initial pilot deployment.  Use the Client Push wizard to deploy clients to individual or small groups of resources to start with.

    I hope that helps,


    Nash Pherson, Senior Systems Consultant
    Now Micro - My Blog Posts
    <-- If this post was helpful, please click "Vote as Helpful".

    Tuesday, July 30, 2013 10:32 PM
  • Regarding Automatic Client Push in ConfigMgr 2012, this feature will try to do a Client Push to all devices that have been discovered.  This doesn't directly interact with Boundary Groups,


    Boundary groups for site assignment are involved in automatic client push, because the push will happen for assigned resources only.

    Torsten Meringer | http://www.mssccmfaq.de

    Wednesday, July 31, 2013 7:16 AM
  • Thanks, that is definitely clarifying.  I'm glad I checked.  Regarding a 2012 client push, is it a possibility to use 2007 to push the 2012 client, along with the specific site, assigning them to the new server?  That way I can use a collection to control installation and migration to the new servers.

    Thanks, Dino

    Wednesday, July 31, 2013 12:05 PM
  • Thanks for the clarification, Torsten! I was under the incorrect impression that the assignment was only important after the push had started on the discovered device. Nash

    Nash Pherson, Senior Systems Consultant
    Now Micro - My Blog Posts
    <-- If this post was helpful, please click "Vote as Helpful".

    • Marked as answer by ingram59 Wednesday, July 2, 2014 6:59 PM
    Wednesday, July 31, 2013 12:24 PM
  • So, I'm confused.  If Client Push is enabled, will it occur only devices defined within a Boundary Group or will it push to all discovered devices?

    Thanks, Dino

    Wednesday, July 31, 2013 1:06 PM
  • Thanks, that is definitely clarifying.  I'm glad I checked.  Regarding a 2012 client push, is it a possibility to use 2007 to push the 2012 client, along with the specific site, assigning them to the new server?  That way I can use a collection to control installation and migration to the new servers.

    Thanks, Dino

    Pushing the 2012 client removes the 2007 client.  If you don't want to use 2012 to push clients, my suggestion would be to use a logon script on AD OUs containing the computers you want to install the 2012 client on.  Jason has one you can use here:

    http://blog.configmgrftw.com/?page_id=349


    • Edited by Mike H Leach Wednesday, July 31, 2013 1:14 PM name
    Wednesday, July 31, 2013 1:13 PM
  • *Automatic* client push will only be initiated to discovered resources that are assigned (=those that are within a boundary group for site assignment).

    Torsten Meringer | http://www.mssccmfaq.de

    Wednesday, July 31, 2013 1:14 PM