none
Upgrade or build new? RRS feed

  • Question

  • I am running SCCM 2012 SP1 CU4. We have one primary stand alone site with a remote SQL server and several Distribution Points. The OS for the servers is Win2008R2 and SQL is 2008R2. We are doing a hardware refresh, Server OS upgrades, and SQL upgrade. We want to go to SCCM 1802.

    Is it worth migrating the SCCM server or building it new? We are currently only using SCCM for patching and will start utilizing it to push out software. I am looking for Pro's and Con's for migrating v/s building new.

    If we were to build it out new, are there any known issues with that kind of deployment?

    Thursday, May 9, 2019 5:59 PM

All replies

  • Hi,

    I did a lot migration from SCCM 2012 to current branch and I didn't face any issue yet. it is easy but you have to read its document before take an action. here is a link that will help you to know what have been changed and what features have been added to sccm current branch.

    https://docs.microsoft.com/en-us/sccm/core/plan-design/changes/what-has-changed-from-configuration-manager-2012

    here is a link that will help you prepare to migrate to current branch. read it carefully

    https://docs.microsoft.com/en-us/sccm/core/migration/planning-for-migration

    if you have more question about this process, feel free to ask


    Thursday, May 9, 2019 8:08 PM
  • I also noticed that there were a log of junk in our Deployment drive. (old Office versions, old Dell cab files, etc) I do not want to have those in our new environment. What would the downside be if I were to just power off the old SCCM 2012 server and install 1802 on a new server?
    Thursday, May 9, 2019 8:24 PM
  • If you don't want to lose any data and avoid having to recreate all of your packages, then (without getting into any of the specific details) you must upgrade. if you don't want to upgrade, all of your clients information that sccm collected, all of your packages and lots of these would vanish. also because of created objects under system management in adsiedit and a lot more reason, it is better not to powering off and installing new one. it will cause known and unknown issues.
    Thursday, May 9, 2019 8:40 PM
  • I am not worried about any old packages on the old SCCM server. (for the last two years is has only been used for Windows update) and I have no issues with recreating my ADR's. I would prefer not to migrate The only option I have is upgrade or migrate? If I do migrate the server to a Win2012R2 server, what data is included in the migration? Old packages (as mentioned above for old Office and Dell Cab files) I appreciate your assistance.
    Thursday, May 9, 2019 9:01 PM
  • Hi,

    It is recommend to use upgrade instead of build new, we could refer to below thread:
    https://social.technet.microsoft.com/Forums/en-US/37bf4463-818d-4453-80e1-f7170aab8e65/sccm-2012-sp1-r2-to-sccm-cb1802-migration?forum=configmanagermigration

    Regards,
    Allen

    Please remember to mark the replies as answers if they help.

    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, May 10, 2019 3:14 AM
  • removing server in ungraceful way will cause lots and lots of unknown issue. it is recommended to update your existing sccm environment and then you can remove the packages and drivers that you don't want. But if you insist on removing and installing new server, do it graceful to have least issue in your environment. I don't recommend it but you can do it. here is a link to help you about this process:

    https://www.prajwaldesai.com/uninstall-sccm-primary-site/

    if yo have more question about this process, feel free to ask

     
    Friday, May 10, 2019 8:48 AM
  • > removing server in ungraceful way will cause lots and lots of unknown issue.

    Not really. There is very little impact with doing this and the cleanup would be trivial. I don't recommend you do that for this scenario though.

    The best path here, unless yo are trying to get rid of a CAS or your convinced that your site is hosed beyond repair, is to upgrade the site combined with a backup and restore of the site to a new server (or servers).

    Migration involves a lot of extra work and not all configuration can be directly migrated (basically, anything that did not exist in ConfigMgr 2007 can't be migrated since the tool set was designed to migrate from 2007).

    Here are some supplemental links:

    - https://home.configmgrftw.com/configmgr-site-server-os-instance-change/

    - https://home.configmgrftw.com/configmgr-site-backup-restore/


    Jason | https://home.configmgrftw.com | @jasonsandys

    Friday, May 10, 2019 12:45 PM