locked
Migrate SCCM 2012R2 on server 2008 to current branch on Server 2012r2 + SQL 2014 on vSphere RRS feed

  • Question

  • Hello,

    I have been asked to look at migrating our in-house SCCM environment from 2012r2 on Server 2008 running on hypervisor that cannot have server 2012r2 installed to current branch version. There are less than 500 clients.

    The new server is 2012R2 on vSphere 5 with SQL 2014 standard

    I have thought this would require a side by side migration as I have been informed that the install of 1602 has to be on a "clean server" and I cannot move and then upgrade the existing server, what does everyone else think of the side by side?

    With regards to SCCM requirements, as there is always going to be less than 1000 clients, will it perform sufficiently on 16GB RAM running on a SAN, (MS recommend 5MB for every client in the database) with SQL on same server as SCCM.

    AS for the disk usage, what would recommendations be? I was looking the at the MS documentation and it says to place each object on dedicated raid volume but I am unable to do this, and what would the disk partition size recommendations be? OS/SCCM/SQL etc.

    The minimum specs from MS seem overkill for our size

    Drive configuration c:\system 50GB  d:SCCM apps and SCCM logs 75 GB e:\sql 100GB  f:\MDT 75GB g:\application content 100GB

    Thanks for your suggestions.


    many thanks

    Friday, July 22, 2016 10:53 AM

Answers

  • Alternative: upgrade to CM current branch (1511, then 1602) and upgrade the OS from 2008r2 to 2012r2. This will only work if you are on 2008 *R2*.
    You'd have to go the parallel migration route otherwise.
    50GB for C: is not very much and you might run into disk space issues soon. Why bothering with different driveletters at all if all is stored on a SAN anyway?

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

    Friday, July 22, 2016 11:12 AM
  • Rather than running a side-by-side migration why not backup and restore onto a server 2012R2. Then upgrade to 1511 and then 1602.

    Cheers Paul | http://sccmentor.com

    Friday, July 22, 2016 1:09 PM
  • IMO the advantages are many. Migration means additional on-going to work to migrate what can be migrated with the migration toolset, migrating manually the things that aren't migrated using the toolset (like client settings), and redeploying all of the clients. Backup and restore has a small amount of pain as well, but it works quite well and has the advantage of you practicing your restore procedures. Additionally, there is a super easy fallback path.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Tuesday, July 26, 2016 6:00 PM

All replies

  • Alternative: upgrade to CM current branch (1511, then 1602) and upgrade the OS from 2008r2 to 2012r2. This will only work if you are on 2008 *R2*.
    You'd have to go the parallel migration route otherwise.
    50GB for C: is not very much and you might run into disk space issues soon. Why bothering with different driveletters at all if all is stored on a SAN anyway?

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

    Friday, July 22, 2016 11:12 AM
  • Hi Torsten,

    Thanks for the reply, not allowed to upgrade the server which is why I have to migrate, with reference to disks, different drive letters helps the support staff understand what is where, company policy etc.

    Regards


    many thanks

    Friday, July 22, 2016 12:45 PM
  • Rather than running a side-by-side migration why not backup and restore onto a server 2012R2. Then upgrade to 1511 and then 1602.

    Cheers Paul | http://sccmentor.com

    Friday, July 22, 2016 1:09 PM
  • Hi Paul,

    Is that supported by MS?I have read some documentation on doing it that way.

    Thanks for the advice, I'll take another look at backup/restore option


    many thanks


    • Edited by MisterD101 Friday, July 22, 2016 3:56 PM
    Friday, July 22, 2016 3:18 PM
  • Yes, this is perfectly supported as it's exactly the same as a normal disaster recovery scenario (except that your hair is not on fire and your boss's boss isn't standing over your shoulder asking you how it's going every 2 minutes).

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Friday, July 22, 2016 9:33 PM
  • Thanks Jason

    I'll take a look at the process. What's the advantage over a side by side migration??What if its a different version of SQL I'm restoring back to? and hostname of new server has to be the same as old, correct?

    regards


    many thanks


    • Edited by MisterD101 Tuesday, July 26, 2016 5:27 PM
    Tuesday, July 26, 2016 5:26 PM
  • IMO the advantages are many. Migration means additional on-going to work to migrate what can be migrated with the migration toolset, migrating manually the things that aren't migrated using the toolset (like client settings), and redeploying all of the clients. Backup and restore has a small amount of pain as well, but it works quite well and has the advantage of you practicing your restore procedures. Additionally, there is a super easy fallback path.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Tuesday, July 26, 2016 6:00 PM