Upgrading SCCM 2012 SP1 to SP2
Table of Contents
Ensure all sites in the hierarchy run a version supported for upgrade
Plan for prerequisites for new site system roles and, ensure site system servers still meet prerequisite for installed site system roles.
- To start Prerequisite Checker and run default checks
- Review the list of considerations for site upgrades
Disable database replicas for management points at primary sites
Reconfigure software update points that use NLBs
Disable all site maintenance tasks at each site for the duration of that site’s upgrade.
Download prerequisite files and redistributable files.
Plan to manage server and client languages when you upgrade a site
- Review the list of considerations for site upgrades
Test the database upgrade process on a copy of the most recent site database backup
Install System Center 2012 Configuration Manager SP2
Upgrade stand-alone Configuration Manager consoles
Reconfigure any database maintenance tasks you disabled prior to the upgrade.
- Upgrade clients.
Service pack 2 provides a bundle of updates and fixes that apply equally to System Center 2012 Configuration Manager SP1 and System Center 2012 R2 Configuration Manager. The same update is applied to either product to bring your deployment the benefit of these updates while maintaining your current version.
The version of your site after upgrading to System Center 2012 Configuration Manager SP2 depends on the pre-upgrade version:
System Center 2012 Configuration Manager SP1: After installing service pack 2 your new site version will be System Center 2012 Configuration Manager SP2.
System Center 2012 Configuration Manager SP2 Upgrade Checklist.
- Ensure all sites in the hierarchy run a version supported for upgrade
Each site in the hierarchy must run the same version of Configuration Manager prior to beginning the upgrade. This is either System Center 2012 Configuration Manager SP1.
The version of cumulative updates for Configuration Manager that are installed a site is not evaluated, and does not affect the upgrade process or success.
- Plan for prerequisites for new site system roles and, ensure site system servers still meet prerequisite for installed site system roles.
During a site upgrade, Configuration Manager automatically upgrades site system roles at the site by reinstalling each site system role. When prerequisites are not met, the site system role might not reinstall or might reinstall, but might fail to operate correctly.
Pre-requisites to follow before upgrade.
- Prerequisite Checker (Prereqchk.exe) is a stand-alone application that verifies server readiness for a site server or specific site system roles. Before site installation, Setup runs Prerequisite Checker. You might choose to manually run Prerequisite Checker on potential site servers or site systems to verify server readiness. This process lets you to remediate any issues that you find before you run Setup. When you run Prerequisite Checker without command-line options, the local computer is scanned for an existing site server, and only the checks that are applicable to the site are run. If no existing sites are detected, all prerequisite rules are run. You can run Prerequisite Checker at a command prompt and specify specific command-line options to perform only checks that are associated with the site server or site systems that you specified in the command line. When you specify another server to check, you must have administrative user rights on the server for Prerequisite Checker to complete the checks. For more information about the prerequisite checks that Prerequisite Checker performs, see Technical Reference for the Prerequisite Checker in Configuration Manager.
- When you are planning to upgrade a Configuration Manager site to a new service pack, you can manually run the Prerequisite Checker on each site to verify that site’s readiness for upgrade. To do so, use the Prerequisite Checker files from the source media of that new version of Configuration Manager. When you run the Prerequisite Checker for upgrade, you do not specify command-line options.
To start Prerequisite Checker and run default checks
- In Windows Explorer, browse to <ConfigMgrInstallationMedia>\SMSSETUP\BIN\X64 or <ConfigMgrInstallationPath>\BIN\X64.
- Open prereqchk.exe to start Prerequisite Checker.
- Prerequisite Checker detects existing sites, and if found, performs checks for upgrade readiness. If no sites are found, all checks are performed. The Site Type column provides information about the site server or site system with which the rule is associated.
Once you run prereq it will show all the prerequisites to be done before upgrading on the server.
In addition to prerequisites for site system roles, some features might require updates as well, like the version of the Windows Assessment and Deployment Kit for use when deploying an operating system.
For example, to deploy an operating system, System Center 2012 Configuration Manager SP2 uses Windows Assessment and Deployment Kit 8.1 instead of Windows Assessment and Deployment Kit 8.0. Before you run Setup, on the site server and on each computer that runs an instance of the SMS Provider you must uninstall the Windows Assessment and Deployment Kit 8.0, and then download and install Windows Assessment and Deployment Kit 8.1.( http://www.microsoft.com/en-US/download/details.aspx?id=39982)
( https://technet.microsoft.com/en-us/library/gg682187.aspx)
Please take a copy of the existing ADK configuration.
To un-install open regedit and go to HKLM- software-Micorosft-windows-currentverssion-uninstall-search for the name same as in ARP.
Copy the un-install string value and run it from command prompt as a dministrator.
Verify the un-install success from the controlpanel,registry and start.
To install the new version copy the file locally and right click run as administrator.
Instlal the ADK in the same place wherever the older one is, in PROD it is D:\Program Files (X86\
After this screen we will get all the features just select windows reinstallation environment (windows PE)and Deployment Tools one more is there I missed it will update later.
Once installation completed you will get close window and launch the guide, verify the installation from start and registry and control panel.
Before proceeding with any installation we need to upgrade our HW please find the link https://technet.microsoft.com/en-us/library/Hh846235.aspx
Review the list of considerations for site upgrades.( https://technet.microsoft.com/en-us/library/gg712676.aspx)
Before you upgrade a site, you must resolve all operational issues for the site server, the site database server, and site system roles that are installed on remote computers. A site upgrade can fail due to existing operational problems
Before you upgrade a site, install any critical updates for each applicable site system. If an update that you install requires a restart, restart the applicable computers before you start the upgrade.
Before you upgrade a site, review available details for product add-ins and extensions that you use with Configuration Manager to ensure compatibility or potential issues during or after the upgrade of the Configuration Manager site.
https://msdn.microsoft.com/en-us/subscriptions/downloads/
- Disable database replicas for management points at primary sites.
( https://technet.microsoft.com/en-us/library/hh846234.aspx)
Configuration Manager cannot successfully upgrade a primary site that has a database replica for management points enabled. Disable database replication before you create the backup of the site database to test the database upgrade, and before you upgrade the production site.
- Reconfigure software update points that use NLBs.
Configuration Manager cannot upgrade a site that uses a Network Load Balancing (NLB) cluster to host software update points. If you use NLB clusters for software update points, use PowerShell to remove the NLB cluster. (Beginning with System Center 2012 Configuration Manager SP1, there is no option in the Configuration Manager console to configure an NLB cluster.)
Before you upgrade a site, back up the site database to ensure that you have a successful backup to use for disaster recovery.
For more information, see Backup and Recovery in Configuration Manager.
- Disable all site maintenance tasks at each site for the duration of that site’s upgrade.
Before you upgrade the version of a Configuration Manager site, disable any site maintenance task that might run at that site during the time the upgrade process is active. This includes but is not limited to the following:
•Backup Site Server
•Delete Aged Client Operations
•Delete Aged Discovery Data
When a site database maintenance task runs during the upgrade process, the site upgrade can fail.
Before you disable a task, record the schedule of the task so you can restore its configuration after the site upgrade completes.
- Download prerequisite files and redistributable files.
Use Setup Downloader from the System Center 2012 Configuration Manager SP2 source media to download prerequisite redistributable files, language packs, and the latest product updates for the product version upgrade.
Configuration Manager Setup Downloader is a stand-alone application that verifies and downloads required prerequisite redistributable files, language packs, and the latest product updates for Setup. When you install a Configuration Manager site, you can specify a folder that contains required files, or Setup can automatically start the Setup Downloader to download the latest files from the Internet. You might choose to run Setup Downloader before you run Setup and store the files on a network shared folder or removable hard drive. This approach is necessary when the planned site server computer does not have Internet access, or a firewall prevents the files from downloading. After you download the latest files, you can use the same path to the download folder to install multiple sites. When you install sites, always verify that the path to the download folder contains the most recent version of the files.
To prevent an attacker from tampering with the files, use a local path to the folder that stores the files. If you use a network shared folder for the files, use Server Message Block (SMB) signing or Internet Protocol security (IPsec) to secure the location for the files.
You can open Setup Downloader and specify a path to the folder to host the downloaded files, or you can run Setup Downloader at a command prompt and specify command-line options. Use the following procedures to start Setup Downloader and download the latest Configuration Manager files that Setup requires.
To start Setup Downloader from Windows Explorer
1.On a computer that has Internet access, open Windows Explorer, and browse to <ConfigMgrInstallationMedia>\SMSSETUP\BIN\X64.
2.Double-click Setupdl.exe. The Setup Downloader opens.
3.Specify the path for the folder that will host the updated installation files, and then click Download. Setup Downloader verifies the files that are currently in the download folder and downloads only the files that are missing or are newer than the existing files. Setup Downloader creates subfolders for the downloaded languages. Setup Downloader will create the folder if it does not exist.
To run the Setup Downloader application, you must have Full Control NTFS file system permissions to the download folder.
4.View the ConfigMgrSetup.log file in the root of the drive C to review the download results.
- Plan to manage server and client languages when you upgrade a site.
(https://technet.microsoft.com/en-us/library/gg712681.aspx#BKMK_PlanningForLanguagePacks)
System Center 2012 Configuration Manager SP2 supports the same server and client languages as prior versions. However, when you upgrade the site, the upgrade process installs new versions of each language pack.
When you run Setup, Setup reviews the current language configuration of your site, and then identifies the language packs that are available in the folder where you store previously downloaded prerequisite files. You can then affirm the selection of the current server and client language packs, or change the selections to add or remove support for languages. Only those language packs are available that are available with the prerequisite files that you download.
Server and client language packs are service pack version-specific. You cannot use the language packs from a different version of Configuration Manager with a SP2 site.
If you have previously installed a language pack for servers or clients at a site, and a version of that language pack is not available with the prerequisite files of the upgrade files, that language cannot be selected. Support for that language is removed from the site when it upgrades.
Review the list of considerations for site upgrades.
Considerations for Upgrading to System Center 2012 Configuration Manager SP2
Automatic actions: When you upgrade a Configuration Manager site to a new version, the following actions occur automatically:
•The site performs a site reset, which includes a reinstallation of all site system roles.
•When you upgrade from System Center 2012 Configuration Manager SP1 to SP2: If the site is the top-level site of a hierarchy, it updates the client installation package on each distribution point in the hierarchy. The site also updates the default boot images to use the new Windows PE version that is included with the Windows Assessment and Deployment Kit 8.1. However, the upgrade does not upgrade existing media for use with image deployment.
•If the site is a primary site, it updates the client upgrade package for that site.
Manual actions for the administrative user after an upgrade: After you upgrade a Configuration Manager site to a new version, ensure that the following actions are performed:
•Ensure that clients that are assigned to each primary site upgrade and install the client software for the new version.
•Upgrade each Configuration Manager console that connects to the site and that runs on a computer that is remote from the site server.
•At primary sites where you use database replicas for management points, reconfigure the database replicas.
•After the site upgrades, you must manually upgrade physical media like ISO files for CDs and DVDs or USB flash drives, or prestaged media used for Windows To Go deployments or provided to hardware vendors. Although the site upgrade updates the default boot images it cannot upgrade these media files or devices used external to Configuration Manager.
•When you upgrade from System Center 2012 Configuration Manager SP1 to SP2: Plan to update non-default boot images when you do not require the original (older) version of Windows PE.
Actions that affect configurations and settings: When a site upgrades to System Center 2012 Configuration Manager SP2, some configurations and settings do not persist after the upgrade or are set to a new default configuration. The following table includes configurations and settings that do not persist or that change, and provides details to help you plan for them during a site upgrade.
Configuration or setting |
Details |
Software Center |
When you upgrade to System Center 2012 R2 Configuration Manager, the following Software Center items are reset to their default values:
|
Software update summarization schedules |
When you upgrade to System Center 2012 Configuration Manager SP2, custom summarization schedules for software updates or software update groups are reset to the default value of 1 hour. After the upgrade finishes, reset custom summarization values to the required frequency. |
- Test the database upgrade process on a copy of the most recent site database backup.
https://technet.microsoft.com/en-us/library/jj865691.aspx#BKMK_TestSiteDBUpgrade
Before you upgrade a Configuration Manager central administration site or primary site, plan to test the site database upgrade process on a copy of the site database. The upgrade test is not required but can identify problems for the upgrade before your production database is affected. A failed site database upgrade can render your site database inoperable and might require a site recovery to restore functionality.
Restart the site server and each computer that hosts a site system role to ensure that there are no pending actions from a recent installation of updates or from prerequisites.
To test a Configuration Manager site database for upgrade
- Make a copy of the site database, and then restore that copy to an instance of SQL Server that uses the same edition as your site database and that does not host a Configuration Manager site. For example, if the site database runs on an instance of the Enterprise edition of SQL Server, make sure you restore the database to an instance of SQL Server that also runs the Enterprise edition of SQL Server.
- After you restore the database copy, run Setup from the source media for the new version of Configuration Manager. When you run Setup, use the /TESTDBUPGRADE command-line option. If the SQL Server instance that hosts the database copy is not the default instance, you must also provide the command-line arguments to identify the instance that hosts the site database copy.
For example, you plan to upgrade a site database with the database name SMS_ABC. You restore a copy of this site database to a supported instance of SQL Server with the instance name DBTest. To test an upgrade of this copy of the site database, use the following command line: Setup.exe /TESTDBUPGRADE DBtest\CM_ABC
You can find Setup.exe in the following location on the source media for Configuration Manager SP1: SMSSETUP\BIN\X64.
- On the instance of SQL Server where you run the database upgrade test, monitor the ConfigMgrSetup.log in the root of the system drive for progress and success:
◦If the test upgrade fails, resolve any issues related to the site database upgrade failure, create a new backup of the site database, and then test the upgrade of the new copy of the site database.
◦After the process is successful, you can delete the database copy.
System_CAPS_noteNote
It is not supported to restore the copy of the site database that you use for the test upgrade for use as a site database at any site.
After you successfully upgrade a copy of the site database, proceed with the upgrade of the Configuration Manager site and its site database.
- Install System Center 2012 Configuration Manager SP2.
Starting at the top-level site in the hierarchy, run Setup.exe from the System Center 2012 Configuration Manager SP2 source media. After the top-level site completes the upgrade and replication is Active, you can begin the upgrade of each child site. Complete the upgrade of each site before you begin to upgrade the next site.
Until all sites in your hierarchy upgrade to the new product version, your hierarchy operates in a mixed version mode
After you complete pre-upgrade configurations for your site, test the upgrade of the site database on a database copy, and download prerequisite files and language packs for the service pack version that you plan to install, you are ready to upgrade your Configuration Manager site.
When you upgrade a site in a hierarchy, you upgrade the top-level site of the hierarchy first. This top-level site is either a central administration site or a stand-alone primary site. After the upgrade of a central administration site is completed, you can upgrade child primary sites in any order that you want. After you upgrade a primary site, you can upgrade that site’s child secondary sites, or upgrade additional primary sites before you upgrade any secondary sites.
To upgrade a central administration site or primary site, you run Setup from the Configuration Manager service pack media. However, you do not run Setup to upgrade secondary sites. Instead, you use the Configuration Manager console to upgrade a secondary site after you complete the upgrade of its primary parent site.
Before you upgrade a site, close the Configuration Manager console that is installed on the site server until after the site upgrade is completed. Also close each Configuration Manager console that runs on computers other than the site server. You can reconnect the console after the site upgrade is completed. However, until you upgrade a Configuration Manager console to the new version of Configuration Manager, that console cannot display some objects and information that are available in new version of Configuration Manager.
Use the following procedures to upgrade Configuration Manager sites:
To upgrade a central administration site or primary site
- Verify that the user who runs Setup has the following security rights:
- Local Administrator rights on the site server computer.
- Local Administrator rights on the remote site database server for the site, if it is remote.
- On the site server computer, open Windows Explorer and browse to <ConfigMgrServicePackInstallationMedia>\SMSSETUP\BIN\X64.
- Double-click Setup.exe. The Configuration Manager Setup wizard opens.
- On the Before You Begin page, click Next.
- On the Getting Started page, select Upgrade this Configuration Manager site, and then click Next.
- On the Product Key page, click Next.
If you previously installed Configuration Manager Evaluation, you can select Install the licensed edition of this product, and then enter your product key for the full installation of Configuration Manager to convert the site to the full version.
- On the Microsoft Software License Terms page, read and accept the license terms, and then click Next.
- On the Prerequisite Licenses page, read and accept the license terms for the prerequisite software, and then click Next. Setup downloads and automatically installs the software on site systems or clients when it is required. You must select all check boxes before you can continue to the next page.
- On the Prerequisite Downloads page, specify whether Setup downloads the latest prerequisite redistributable files, language packs, and the latest product updates from the Internet or use previously downloaded files, and then click Next. If you previously downloaded the files by using Setup Downloader, select Use previously downloaded files and specify the download folder
https://technet.microsoft.com/en-us/library/gg712320.aspx#BKMK_SetupDownloader
- On the Server Language Selection page, view the list of languages that are currently installed for the site. Select additional languages that are available at this site for the Configuration Manager console and for reports, or clear languages that you no longer want to support at this site, and then click Next. By default, English is selected and cannot be removed.
Each version of Configuration Manager cannot use language packs from a prior version of Configuration Manager. To enable support for a language at a Configuration Manager site that you upgrade, you must use the version of the language pack for that new version. For example, during upgrade from Configuration Manager with no service pack to Configuration Manager SP1, if the Configuration Manager SP1 version of a language pack is not available with the prerequisite files you download, support for that language cannot be installed. When a language is already installed for Configuration Manager with no service pack and the language pack for the new version is not available, support for that language is uninstalled when the site upgrades. |
- On the Client Language Selection page, view the list of languages that are currently installed for the site. Select additional languages that are available at this site for client computers, or clear languages that you no longer want to support at this site. Specify whether to enable all client languages for mobile device clients, and then click Next. By default, English is selected and cannot be removed.
Each version of Configuration Manager cannot use language packs from a prior version of Configuration Manager. To enable support for a language at a Configuration Manager site that you upgrade, you must use the version of the language pack for that new version. For example, during upgrade from Configuration Manager with no service pack to Configuration Manager SP1, if the Configuration Manager SP1 version of a language pack is not available with the prerequisite files that you download, support for that language cannot be installed. When a language is already installed for Configuration Manager with no service pack and the language pack for the new version is not available, support for that language is uninstalled when the site upgrades. |
- On the Settings Summary page, click Next to start Prerequisite Checker to verify server readiness for the upgrade of the site.
- On the Prerequisite Installation Check page, if there are no problems listed, click Next to upgrade the site and site system roles. When Prerequisite Checker finds a problem, click an item on the list for details about how to resolve the problem. Resolve all items in the list that have an **Error ** status before you continue Setup. After you resolve the issue, click Run Check to restart prerequisite checking. You can also open the ConfigMgrPrereq.log file in the root of the system drive to review the Prerequisite Checker results. The log file can contain additional information that is not displayed in the user interface. For a complete list of installation prerequisite rules and descriptions
Perform Post-Upgrade Tasks on Configuration Manager Sites
After you upgrade a site to a new service pack, you might have to complete additional tasks to finish the upgrade or reconfigure the site. These tasks can include the upgrade of Configuration Manager clients or Configuration Manager consoles, re-enabling database replicas for management points, or restoring settings for Configuration Manager functionality that you use and that does not persist after the service pack upgrade.
10. Upgrade stand-alone Configuration Manager consoles.
https://technet.microsoft.com/en-us/library/gg712320.aspx#BKMK_InstallConsole
By default, when you upgrade a central administration site or primary site, the installation also upgrades a Configuration Manager console that is installed on the site server. However, you must manually upgrade each Configuration Manager console that is installed on a computer other than the site server.
When you use a Configuration Manager console that is of a lower service pack version than the site that you connect to, the console cannot display or create some objects and information that are available in the new service pack version. When you use a Configuration Manager console that is of a higher service pack version than the site that you connect to, the connection is blocked. |
When you upgrade a Configuration Manager console, the installation process uninstalls the existing Configuration Manager console, and then installs the new version of the software. Therefore, to upgrade a console on computers other than site servers, you can use any method that Configuration Manager supports to install the Configuration Manager console. These supported methods can include a manual installation or a deployment that installs the console.
11. Reconfigure any database maintenance tasks you disabled prior to the upgrade.
If you disabled database maintenance tasks at a site prior to the upgrade, reconfigure those tasks at the site using the same settings that were in place prior to the upgrade
Upgrade clients.
https://technet.microsoft.com/en-us/library/gg712298.aspx
After you upgrade a primary site, plan to upgrade clients that are assigned to that site. Although a Configuration Manager primary site or secondary site can support communication from clients that have a lower service pack version, this communication should be a temporary configuration. Clients that run a previous version of Configuration Manager cannot use the new functionality that is available with the new version of Configuration Manager.
When you upgrade the top-level site of a hierarchy to a new service pack, the client installation package on each distribution point in the hierarchy is also updated. When you upgrade a primary site, the client upgrade package that is available from that primary site is updated. |
Reference Links.
https://technet.microsoft.com/en-us/library/jj822981.aspx#BKMK_PlanningSP2Upgrade
https://technet.microsoft.com/en-us/library/gg712320.aspx#BKMK_PrerequisiteChecker
boot images
http://blogs.technet.com/b/umairkhan/archive/2014/03/25/configmgr-2012-drs-troubleshooting-faqs.aspx