locked
Effect of Configuring Boundary Groups in SCCM 2012 for migration RRS feed

  • Question

  • I'm migrating from SCCM 2007 (sitecode 001) to 2012 (sitecode 100).  In the 2012 environment I've got one Primary Site and no Secondary Sites.  My discovery methods are running and my boundaries are configured.  I have not created boundary groups yet.  Also, I have only run and re-run some VERY SMALL test migrations to see how things come across and what they look like.  My Client Push Installation IS NOT enabled yet.  Neither is the Software Update-Based Client Installation.  

    Devices (desktops, laptops and servers), Users and AD Groups, etc... are all showing up in the new environment and no 2012 clients have been installed yet.  In the 2012 console all devices show Client = No and Site Code = "  "

    I understand that defining boundaries has no effect on the environment and that it is boundary groups that 'open the gates', so to speak, to the new environment.  My question has to do with defining Boundary Groups.  Given the environment as described above, what will happen once I define boundary groups?  My concern is that 'somehow' the new environment will want to take control of the devices and it will 'somehow' conflict with or cause issues with my current environment.  Please assist me in my understanding of the power or lack thereof of the Boundary Groups, once configured.

    Thanks in advance


    Thanks, Dino

    Wednesday, July 24, 2013 7:37 PM

Answers

  • The worst case is that some of your clients in 2007 will disappear from that console.  But, they will come back when you change the boundary groups back. 

    Boundaries have nothing to do with existing clients reporting to a site. They will continue functioning without any boundaries (with limitations when it comes to roaming, content location and auto site assignment).

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

    • Marked as answer by ingram59 Thursday, July 25, 2013 5:53 PM
    Wednesday, July 24, 2013 8:34 PM

All replies

  • Your clients aren't going to magically reassign themselves and neither automatic client push nor software update point client installation will upgrade those clients to the 2012 client if that's what you are worried about.


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

    Wednesday, July 24, 2013 7:52 PM
  • I realize that magic has nothing to do with it.  And yes that WAS my concern. I get very concerned and cautious here.  With this concern now magically removed, briefly, what is the impact of defining boundary groups at this stage of the process.


    Thanks, Dino

    Wednesday, July 24, 2013 7:58 PM
  • The worst case is that some of your clients in 2007 will disappear from that console.  But, they will come back when you change the boundary groups back.  They will not get automatically upgraded unless you make that selection in the Client Installation settings in 2012.  I had this happen at a client once. 

    So, to play it safe, I have my clients create an isolated test IP range to use for testing in 2012.  I put that range into a boundary and that boundary into a group.  This keeps the 2007 and the 2012 clients totally separate.

    Wednesday, July 24, 2013 8:09 PM
  • The worst case is that some of your clients in 2007 will disappear from that console.  But, they will come back when you change the boundary groups back. 

    Boundaries have nothing to do with existing clients reporting to a site. They will continue functioning without any boundaries (with limitations when it comes to roaming, content location and auto site assignment).

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

    • Marked as answer by ingram59 Thursday, July 25, 2013 5:53 PM
    Wednesday, July 24, 2013 8:34 PM
  • Torsten, I remember being assured the same thing by Eric from Microsoft back at MMS 2012. But, at one of my clients in TN, all the clients disappeared from the 2007 console when I configured the same boundaries in 2012. Logs basically said they were trying to check in to the wrong site. Odd. And I have not been able to repeat it since. But, I assure you that it did happen. As soon as I changed the boundaries back in 2012, the clients showed up in the 2007 console again. So, to make sure I don't have any clients freak out on me again, I configure test boundaries in 2012 that do not exist in 2007.
    Wednesday, July 24, 2013 8:59 PM
  • That might have been caused by overlapping boundaries for site assignment (which is not supported and can cause issues).
    Having overlapping boundaries for content location is supported though (and does not cause issues).

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

    Wednesday, July 24, 2013 9:11 PM
  • That might have been caused by overlapping boundaries for site assignment (which is not supported and can cause issues).
    Having overlapping boundaries for content location is supported though (and does not cause issues).

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


    That sounds about right. I'm very rusty on 2007. So, I don't remember where that's set up there. But, we should be ok configuring identical boundaries as long as keep the check out of the box for "Use this boundary group for site assignment"?
    Wednesday, July 24, 2013 9:38 PM
  • Yes.

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

    Wednesday, July 24, 2013 10:25 PM
  • At while you have both environments up I'd suggest not using automatic site assginment.


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

    Thursday, July 25, 2013 12:56 PM