locked
Side by Side - Site Assignment RRS feed

  • Question

  • I'm doing a Side by Side migration from R2 to 1511.

    Its going to take a few weeks to migrate all clients.

    In the meantime, I'm thinking what to do about site assignment.

    Old Environment - 4 Regional Primary Sites

    New Environment - 1 Primary

    I still need to do OSD in the old environment, so ideally need to leave my boundary groups for site assignment set up. But because the boundaries overlap, some new clients will find the old site codes!?

    Not sure how other people do it?

    Thursday, May 12, 2016 9:13 AM

Answers

  • It will be assigned to the site that was used for PXE booting or where the media was created.

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

    Thursday, May 12, 2016 10:51 AM
  • I am almost done with my side by side migration.   I placed my new primary site in a different OU (AD) to avoid confusion with the site code, this OU is not as part of the AD System Discovery.   After that you can change the site code of the workstations and servers with the new site code.   I tested that using some servers and workstations not in production.   I changed the DHCP scope to the new site to test the OSD, the site code will be assign properly. By the way you will need to use a different side code, cannot use the same.
    Thursday, May 12, 2016 7:30 PM

All replies


  • so ideally need to leave my boundary groups for site assignment set up.


    No. Just remove boundary groups for site assignment. They are not needed in an OSD Scenario (exception: using dynamic media. PXE is not affected though).

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

    Thursday, May 12, 2016 9:41 AM
  • Hmm, so if I build a machine how does it find its site?
    Thursday, May 12, 2016 9:43 AM
  • It will be assigned to the site that was used for PXE booting or where the media was created.

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

    Thursday, May 12, 2016 10:51 AM
  • I am almost done with my side by side migration.   I placed my new primary site in a different OU (AD) to avoid confusion with the site code, this OU is not as part of the AD System Discovery.   After that you can change the site code of the workstations and servers with the new site code.   I tested that using some servers and workstations not in production.   I changed the DHCP scope to the new site to test the OSD, the site code will be assign properly. By the way you will need to use a different side code, cannot use the same.
    Thursday, May 12, 2016 7:30 PM