This information was taken from Microsoft and could come in handy:
http://technet.microsoft.com/en-us/library/jj822981.aspx
Use the information in the following check list to help you identify and plan for pre-upgrade configurations and additional actions that are related to upgrading your sites and hierarchy to Configuration Manager SP1.
| Step | More Information | ||||
| Ensure that your computing environment meets the supported configurations that are required for upgrading to System Center 2012 Configuration Manager SP1. | Before you upgrade to Configuration Manager SP1, install the required prerequisites on each computer that hosts a site system role. Several site system roles require new or upgraded prerequisites.
For example, to deploy an operating system, Configuration Manager SP1 uses the Windows Assessment and Deployment Kit (Windows ADK) instead of Windows Automated Installation Kit (Windows AIK). Before you run Setup, you must download and install Windows ADK on the site server and on each computer that runs an instance of the SMS Provider. For general information about supported platforms and perquisite configurations, see Supported Configurations for Configuration Manager. For information about how to use the Windows ADK with Configuration Manager, see the Prerequisites For Deploying Operating Systems in Configuration Manager topic in the Deploying Software and Operating Systems in System Center 2012 Configuration Manager guide. |
||||
| Review the site and hierarchy status and verify that there are no unresolved issues. | Before you upgrade a site, resolve all operational issues for the site server, the site database server, and site system roles installed on remote computers. A site upgrade can fail due to existing operational problems.
For information about the status of sites and site system roles, see Monitor Configuration Manager Sites and Hierarchy. |
||||
| Install all applicable critical updates for operating systems on computers that host the site, the site database server, and remote site system roles. | Before you upgrade a site, install any critical updates for each applicable site system. If it is required by an update that you install, reboot the applicable computers before you start the service pack update.
For more information, see Windows Update. |
||||
| Disable database replicas for management points at primary sites. | Configuration Manager cannot successful 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 to Configuration Manager SP1.
For more information, see Configure Database Replicas for Management Points. |
||||
| Reconfigure software update points that use NLBs. | Configuration Manager cannot upgrade a site that uses a NLB cluster to host software update points. For more information, see the Upgrading from Configuration Manager with No Service Pack to Configuration Manager SP1 section in the Planning for Software Updates in Configuration Manager topic. | ||||
| Back up the site database at the central administration site and primary sites. | Before you upgrade a site, back up the site database to ensure that you have a successful back to use for disaster recovery.
For more information, see Backup and Recovery in Configuration Manager. |
||||
| Disable the site maintenance task Delete Aged Client Operations on primary sites. | Before you upgrade any sites to Configuration Manager SP1, disable this site maintenance task on each primary site in the hierarchy. When this task remains active at a primary site that runs Configuration Manager with no service pack, this task deletes information about active client operations for clients that run Configuration Manager SP1. After all primary sites are upgraded to Configuration Manager SP1; you can enable this task for standard site maintenance at each primary site.
For more information about site maintenance tasks, see the Planning for Maintenance Tasks for Configuration Manager section in the Planning for Site Operations in Configuration Manager topic. |
||||
| Create a copy of each built-in collection you have modified. | When you upgrade to Configuration Manager SP1, the built-in collections are overwritten in the site database. If you have customized a built-in collection, create a copy of that collection before you upgrade.
In Configuration Manager SP1, the built-in collections are read-only and cannot be modified. |
||||
| Run the Setup Prerequisite Checker. | Configuration Manager SP1 introduces new prerequisite checks. Before you upgrade a site, you can run the prerequisite checker independently from Setup to validate that your site meets the prerequisites. When you upgrade the site, the prerequisite checker runs again.
For more information, see the Prerequisite Checker section in the Install Sites and Create a Hierarchy for Configuration Manager topic. For information about prerequisite checks, see Technical Reference for the Prerequisite Checker in Configuration Manager. |
||||
| Download prerequisite files and redistributable files for Configuration Manager SP1. | Use the Setup Downloader from the Configuration Manager SP1 source media to download prerequisite redistributable files, Configuration Manager SP1 language packs, and the latest product updates for the service pack upgrade.
For information about Setup Downloader, see the Setup Downloader section in the Install Sites and Create a Hierarchy for Configuration Manager topic. |
||||
| Plan to manage server and client languages when you upgrade a site. | Configuration Manager SP1 supports the same server and client languages as Configuration Manager with no service pack and it also supports additional languages that are introduced with Configuration Manager SP1. However, when you upgrade to Configuration Manager SP1, the site upgrade 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 that are available with the perquisite files you download are available.
If you have previously installed a language pack for servers or clients at a site and a Configuration Manager SP1 version of that language pack is not available with the prerequisite files, that language cannot be selected and support for that language is removed from the site when it upgrades. For more information about language packs, see the Planning for Client and Server Operating System Languages in Configuration Manager section in the Planning for Sites and Hierarchies in Configuration Manager topic. For information about Setup Downloader, see the Setup Downloader section in the Install Sites and Create a Hierarchy for Configuration Manager topic. |
||||
Plan for new site system role prerequisites.
|
Several site system roles have new prerequisites for Configuration Manager SP1. Before you upgrade a site, verify that each computer that hosts a site system role meets any new prerequisites for Configuration Manager SP1.
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 fail to operate correctly. For information about prerequisites for site system roles, see the Site System Requirements section in the Supported Configurations for Configuration Manager topic. |
||||
| Review the list of considerations for site upgrades. | When you upgrade a site, some features and configurations reset to a default configuration. To help you plan for these and related changes in Configuration Manager SP1, review the information in the Considerations For Upgrading to Configuration Manager SP1 section in this topic. | ||||
| Test the database upgrade process on a copy of the most recent site database backup. | Before you upgrade a Configuration Manager central administration site or primary site to a new service pack, plan to test the site database upgrade process on a copy of the site database. This is because when you upgrade a site, the site database might be modified and although a test database upgrade is not required, it 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.
Although the site database is shared between sites in a hierarchy, plan to test the database at each applicable site before upgrading that site. If you use database replicas for management points at a primary site, disable replication before you create the backup of the site database.
For more information, see the Test the Configuration Manager Site Database for the Upgrade section in the Upgrade Configuration Manager to a New Service Pack topic. |
||||
| Restart the site server and each computer that hosts a site system role to ensure that there are no pending actions from recent installation of updates or prerequisites. | Internal process that is company-specific. | ||||
| Install the service pack. | Starting at the top-level site in the hierarchy, run Setup.exe from the Configuration Manager SP1 source media. After the top-level site completes upgrade to Service Pack 1, you can begin upgrade of each child site. Complete the upgrade of each site before beginning upgrade of the next site.
Until all sites in your hierarchy upgrade to the same service pack version, you hierarchy operates in a mixed service pack version mode. For information about how to run the service pack installation, see the Upgrade a Configuration Manager Site section in the Upgrade Configuration Manager to a New Service Pack topic. For information about operating a Configuration Manager hierarchy in mixed mode, see the Interoperability between Sites with Different Service Pack Versions in System Center 2012 Configuration Manager section in the Interoperability between Different Versions of Configuration Manager topic. |
||||
| Upgrade stand-alone Configuration Manager consoles. | 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 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 Configuration Manager console on computers other than site servers, you can use any method that Configuration Manager supports to install the Configuration Manager console. This can include a manual installation, or a deployment that installs the console. For more information about how to install the Configuration Manager console, see the Install a Configuration Manager Console section in the Install Sites and Create a Hierarchy for Configuration Manager topic. |
||||
| Reconfigure database replicas for management points at primary sites. | If you use database replicas for management points at primary sites, you must uninstall the database replicas before you upgrade the site. After you upgrade a primary site, reconfigure the database replica for management points.
For more information, see the Configurations for Using a Database Replica section in Configure Database Replicas for Management Points topic. |
||||
| Upgrade clients. | 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 should be a temporary configuration. Clients that run a previous service pack version of Configuration Manager cannot use the new functionality that is available with the new service pack version of Configuration Manager.
When you upgrade a client, the current client software uninstalls and the new client software version installs. To upgrade clients, you can use any method that Configuration Manager supports.
For information about how to upgrade existing clients and how to install new clients, see How to Install Clients on Windows-Based Computers in Configuration Manager. |
