locked
2012 and 2007 client co-existence RRS feed

  • Question

  • For many of us, 2012 will be installed in the same domain as 2007. Therefore, AD data will exist for both versions.

    When installing a 2012 client, this is not an issue as it ignores and 2007 AD data.

    However, if a phased migration is occurring and you still have the odd 2007 client being installed, it could potentially get confused and assign itself to a 2012 Site.

    So what are the ways to prevent this?

    One obvious one would be to specify the site as a parameter during 2007 client installation. That wouldnt work for us as we have one delivery method and many sites so we rely on automatic site assignment.

    Lets assume that a boundary for the new 2007 client exists in both 2007 and 2012. If that boundary (in 2012) has not yet been assigned to a boundary group and therefore would not have site assignment, then it would not inadvertently end up being assigned to a 2012 site?

    Cheers

    David Z

    Sunday, May 27, 2012 11:10 PM

Answers

  • That's why it's not supported to have overlapping boundaries (boundary groups) for site assignment.
    A boundary that was not added to a boundary group in CM12 is just an object without any functionality.

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

    • Marked as answer by David Zemdegs Tuesday, May 29, 2012 10:08 PM
    Monday, May 28, 2012 11:23 AM

All replies

  • That's why it's not supported to have overlapping boundaries (boundary groups) for site assignment.
    A boundary that was not added to a boundary group in CM12 is just an object without any functionality.

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

    • Marked as answer by David Zemdegs Tuesday, May 29, 2012 10:08 PM
    Monday, May 28, 2012 11:23 AM
  • Thanks for confirming that.
    Tuesday, May 29, 2012 10:08 PM