locked
Upgrade process to SCCM ConfigMgr 1511 RRS feed

  • Question

  • Hi,

    I'm currently running SCCM 2012 R2 SP1 CU1 and I'd like to get the process of moving to SCCM ConfigMgr 1511 started.  I understand that I can do a direct upgrade from SCCM 2012 R2 SP1 to SCCM ConfigMgr 1511 but my concern is that I'm currently running my SCCM 2012 R2 SP1 system on a Windows 2008 R2 system with SQL Server 2008 R2 and WSUS.

    But I'd ideally like to end up with SCCM ConfigMgr 1511 running on Windows 2012 R2 and SQL Server 2014 SP1.

    So I think my two options are:

    1. Stay with Windows Server 2008 R2, SQL Server 2008 R2 and WSUS and upgrade SCCM 2012 R2 SP1 CU1 to SCCM ConfigMgr 1511.  Then do a SCCM migration to a new server that is running Windows 2012 R2 and SQL Server 2014 SP1

    2. Do a SCCM server migration to a new server that is running Windows 2012 R2 and SQL Server 2014 SP1.  Then upgrade from upgrade SCCM 2012 R2 SP1 CU1 to SCCM ConfigMgr 1511.


    I'm leaning towards do option two as I think it's probably better to get the OS and SQL Server configured correctly first before moving to SCCM ConfigMgr 1511.  Given that, are there any good links that document how to do a site migration to a new server?

    Thanks in advance,
    Nick

    Tuesday, January 5, 2016 12:17 AM

Answers

  • Neither. I would upgrade in place to 1511 and SQL 2014. Then I would do a backup and restore of ConfigMgr to a new server running Server 2012 R2 and SQL 2014. Much quicker and cleaner without having to worry about any migration messiness like reinstalling all of the client agents.


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

    • Proposed as answer by TorstenMMVP Tuesday, January 5, 2016 7:20 AM
    • Marked as answer by Frank Dong Monday, January 25, 2016 7:04 AM
    Tuesday, January 5, 2016 1:08 AM

All replies

  • Neither. I would upgrade in place to 1511 and SQL 2014. Then I would do a backup and restore of ConfigMgr to a new server running Server 2012 R2 and SQL 2014. Much quicker and cleaner without having to worry about any migration messiness like reinstalling all of the client agents.


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

    • Proposed as answer by TorstenMMVP Tuesday, January 5, 2016 7:20 AM
    • Marked as answer by Frank Dong Monday, January 25, 2016 7:04 AM
    Tuesday, January 5, 2016 1:08 AM
  • Jason, I'm in the exact same boat as Nick and I've seen your recommendation many times from others.  The problem I have is that there seems to be no MS documentation or guides of any sort on that method.  What if someone has offloaded some roles(DP, MP, SUP, etc) onto a second server, how is that handled?  Thanks for your time and input.

    EDIT: I wanted to add one of the major hangups with this method.  From https://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SupConfigSQLDBconfig

    Configuration Manager does not support using Windows Server Update Services (WSUS) 3 SP2 on the following Windows Server versions when the Server also runs SQL Server 2014:

    • Windows Server 2008 SP2

    • Windows Server 2008 R2 SP1


    • Edited by Andrew.JR Tuesday, January 5, 2016 2:58 PM
    Tuesday, January 5, 2016 2:40 PM
  • Backup and recovery are fully documented at https://technet.microsoft.com/en-us/library/gg712697.aspx

    What if someone has offloaded some roles(DP, MP, SUP, etc) onto a second server, how is that handled?

    This doesn't change anything. As far as the roles are concerned, nothing has changed because in fact, nothing has. It's the same ConfigMgr site and the site server has the same name.

    As for the WSUS issue, it does work to my knowledge and will only be temporary in any event. If you are worried about this, simply move the WSUS DB to the Windows Internal DB temporarily.


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

    Tuesday, January 5, 2016 3:12 PM
  • Thanks, Jason.  The WSUS issue was one of my major sticking points so I may do the temporary move like you suggest.  I was also not looking at this from a site backup and recovery method, for some reason.  I'm going to test some things out in our lab and see how it goes.  Thanks, again.
    Tuesday, January 5, 2016 3:18 PM
  • Hi Nick,

    As per Your requirements, I have found some below reference links:

    https://kobile.wordpress.com/2010/10/10/moving-sccm-server-to-new-hardware/

    https://technet.microsoft.com/en-us/library/gg712697.aspx

    https://www.systemcenterdudes.com/sccm-1511-migration/

    Mark as Answer if this helps You!

    Thanks,

    Mayank Dhama

    Tuesday, January 5, 2016 3:19 PM
  • Dear Sir,

    Sorry, but I'm trying to clean some old posts. Did above replies helpful? Please mark them as answers so that it will be easier to read.

    Thanks in advance.

    Best regards

    Frank

    Friday, January 15, 2016 7:34 AM
  • Hi -

    Sorry for the delayed response, I was away on vacation.

    So it looks like the best option is as Jason said is to do an in place to 1511 and SQL 2014 and then using the standard SCCM backup and restore I can move everything to a newly rebuilt server (same server) with Windows 2012 R2 and SQL 2014.

    The only issue I see here is WSUS as Andrew Jr. pointed out.  Currently my WSUS server runs on my SCCM server in the same database.  So if I upgrade the database to SQL 2014 that will break WSUS on that server correct?

    Another thought I had was to temporarily move the WSUS database to a different machine and then do the SCCM upgrade process and then when everything is good move the WSUS database back to the SCCM machine. Will that work?  Are there any docs on how to move a WSUS database that's integrated with SCCM?

    Thanks

    Nick

    Saturday, January 23, 2016 1:25 AM
  • So even SQL Server in place upgrade is supported? Running SQL 2012 on ConfigMgr server, is it possible to just upgrade it to 2014 along with ConfigMgr to 1511?
    Saturday, January 23, 2016 4:26 AM
  • "So if I upgrade the database to SQL 2014 that will break WSUS on that server correct?"

    No. Why would that break WSUS? Not listed as supported doesn't mean it will break. As noted, just move the DB to the Windows Internal if you are truly concerned about this though. Yes, you could move it to another system also -- but now you are paying for an additional SQL license and managing an additional SQL instance and server -- no reason to go this far IMO. I'd say try it on SQL 2014. What's the worst that can happen? You restore have to restore your WSUS DB again -- that's trivial at best. The WSUS DB is *not* integrate with ConfigMgr. It's simply WSUS so there's nothing special to do except configure WSUS -- ConfigMgr doesn't know about or care about the WSUS DB itself.


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

    Saturday, January 23, 2016 7:50 PM
  • Yes, in-place SQL Server upgrades work just fine and are supported.

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

    Saturday, January 23, 2016 7:50 PM
  • Nick,

    My environment is all 2008R2 Server and SQL 2008R2 running on the primary site server.  I have SUP, DP, MP running on a second server.  Friday night I upgraded the database to 2014 SP1.  Other than a few hiccups during the ugprade process(see below), everything is working just fine, including SUP.  My next step is to do a backup/restore of the primary site server to a new 2012R2 server with the same name, disk layout, etc.  Once that is complete I will be upgrading to 1511.

    I had to uninstall SQL 2012 Native Client in order for the SQL upgrade to run.  SSRS also didn't get upgraded correctly, so I had to do the following.  The links are references to issues I came across during the deployment of SSRS.  You may or may not experience the same. My reporting services point is running on the same SQL instance on the primary site server where SQL was upgraded.

    Added SSRS 2014 Feature

    In SSRS Configuration Tool

    Pointed to existing databases

    Removed old URL reservations

    Applied Web service url and report manager url config(defaults, but different config would have resulted in not needing to remove old reservations)

    Encryption Keys > Delete encrypted content

    Reinstall Reporting Services Point

    Set data source on custom reports

    Sunday, January 24, 2016 3:43 PM
  • Hi Jason,

    I can't find any links on moving a WSUS database to the Windows Internal DB, all I find our links for how to go the other way. 

    That said, I'm going to try all this out in a lab setup so I'll give the direct upgrade to SQL 2014 a shot and see what happens. 

    Andrew,

    Thanks for the info on the steps you had to follow. I'll follow those things when I do the test SQL Server upgrade

    Nick

    Monday, January 25, 2016 5:53 PM
  • Hi Jason,

    I can't find any links on moving a WSUS database to the Windows Internal DB, all I find our links for how to go the other way. 


    Who would you want move your WSUS DB from much more faster and reliable solution to something else?
    • Edited by Narcoticoo Monday, January 25, 2016 10:01 PM
    Monday, January 25, 2016 10:01 PM