none
SCCM 2012 R2 server installation on SCCM 2012 environment RRS feed

  • Question

  • Due to some disaster, I have lost my SCCM 2012 server VM completely my production. But my dedicated SQL server VM for SCCM is still available, which is SQL 2008 R2 SP2. 

    Now I want to install SCCM 2012 R2 in my production.

    1. Is there any preparation I need to take, such as preparing AD

    2. Is there any issue I may encounter, if I want to use my existing SQL 2008 R2 SP2 server for SCCM or I better use a new SQL 2012

    3. What else I need to consider before installing SCCM 2012 R2 to avoid unwanted trouble in production?

    4. SCCM agents are installed on all desktops and servers in my environment. Is it simply uninstalling those agents manually and installing new SCCM R2 agent or I need to take some more precautions/steps?

    5. Is there any step-by-step guide to install SCCM R2

    Thanks in advance.



    • Edited by mkhan100 Friday, April 25, 2014 9:39 PM
    Friday, April 25, 2014 9:33 PM

Answers

  • You can fully recover ConfigMgr 2012 from the existing database, there's no need to rebuild everything. You just need another server as the site server and go through the recovery procedures: http://technet.microsoft.com/en-us/library/gg712697.aspx

    Jason | http://blog.configmgrftw.com

    • Marked as answer by mkhan100 Tuesday, April 29, 2014 2:39 AM
    Friday, April 25, 2014 9:45 PM
  • Hi mkhan100,

    First question: Do you have your Site Server and SQL backup (from the built in Site Backup task)?  If so you would better served with a site recovery on a new VM, then once everything is stable again, upgrade to R2.

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

    Now I'll try my best to answer your questions. ;-)

    1.  The AD preparation might be just removing the old objects from the System Management container.  Other than that there are no additional Schema changes required.

    2.  When you say use your existing SQL server, you mean you want to attempt to use the same database or simply the same database server and you will be creating a NEW SCCM DB for the R2 environment?  If its a new DB (and you don't care about any data in the existing) then just remove the old DB from SQL. 

    3.  I would start with technet article: http://technet.microsoft.com/en-us/library/gg682077.aspx

    4.  Your SCCM agents prereqs I do not believe change between the 2012 client and the R2 client with the exception of a newer version of Silverlight.  This was released several months ago so if you manage Silverlight updates you have likely already deployed the required version or newer.  Regardless, I believe when you deploy the SCCM 2012 R2 client it will upgrade or install any missing prerequisites.

    5.  Not a lot has changed from an installation perspective.  If you are familiar with the SCCM 2012 setup, R2 wont be a challenge.

    • Marked as answer by mkhan100 Tuesday, April 29, 2014 2:39 AM
    Friday, April 25, 2014 9:47 PM

All replies

  • You can fully recover ConfigMgr 2012 from the existing database, there's no need to rebuild everything. You just need another server as the site server and go through the recovery procedures: http://technet.microsoft.com/en-us/library/gg712697.aspx

    Jason | http://blog.configmgrftw.com

    • Marked as answer by mkhan100 Tuesday, April 29, 2014 2:39 AM
    Friday, April 25, 2014 9:45 PM
  • Hi mkhan100,

    First question: Do you have your Site Server and SQL backup (from the built in Site Backup task)?  If so you would better served with a site recovery on a new VM, then once everything is stable again, upgrade to R2.

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

    Now I'll try my best to answer your questions. ;-)

    1.  The AD preparation might be just removing the old objects from the System Management container.  Other than that there are no additional Schema changes required.

    2.  When you say use your existing SQL server, you mean you want to attempt to use the same database or simply the same database server and you will be creating a NEW SCCM DB for the R2 environment?  If its a new DB (and you don't care about any data in the existing) then just remove the old DB from SQL. 

    3.  I would start with technet article: http://technet.microsoft.com/en-us/library/gg682077.aspx

    4.  Your SCCM agents prereqs I do not believe change between the 2012 client and the R2 client with the exception of a newer version of Silverlight.  This was released several months ago so if you manage Silverlight updates you have likely already deployed the required version or newer.  Regardless, I believe when you deploy the SCCM 2012 R2 client it will upgrade or install any missing prerequisites.

    5.  Not a lot has changed from an installation perspective.  If you are familiar with the SCCM 2012 setup, R2 wont be a challenge.

    • Marked as answer by mkhan100 Tuesday, April 29, 2014 2:39 AM
    Friday, April 25, 2014 9:47 PM