Step- by- Step SCCM 2. R2 SP1 Upgrade Guide. Microsoft has recently announced the release of SCCM 2. SP2 and SCCM 2. 01. R2 SP1. Before performing an SCCM 2. R2 SP1 upgrade, we recommend that you read carefully all the available resources and carefully plan the upgrade process throughout your SCCM 2.
Complete SCCM 2012 R2 SP1 Upgrade installation guide. It will guide you in details through the whole SCCM 2012 R2 SP1 upgrade process and gives useful links.
R2 hierarchy. The good news is that our SCCM 2. R2 SP1 Upgrade Guide will list everything you need to know before applying this major upgrade to your existing SCCM 2. We’ve got you covered ! What’s new. The main reason you’ll want to upgrade to SCCM 2. R2 SP1 is probably for Windows 1. No plan for Windows 1.
- Everything you ever wanted to know about Microsoft Windows Updates. Quick links for Microsoft Windows updates:-Configuring automatic updates Manually checking for updates.
- Cisco Identity Services Engine Administrator Guide, Release 2.1 -Policy User Interface Reference.
There’s interesting new features and a lots of bug fixes (thousands, which are not fully documented) in this release that are worth it. Do I still need to perform the SCCM 2. R2 SP1 upgrade? See the full list of features on this Technet Article to figure it out. Naming Confusion. Following the announcement, the community was confused on how to apply this Service Pack because Microsoft decide to release it under one binary even if there’s 3 possible “version” of SCCM 2. SCCM 2. 01. 2 RTM, SCCM 2.
Deploy Windows 10 in a test lab using System Center Configuration Manager.
SP1, SCCM 2. 01. 2 R2)If you’re running SCCM 2. SP1 (non- R2) the upgrade process will bring your site to SCCM 2. SP2. If you want to upgrade to SCCM 2. R2 SP1 afterward, you’ll need to run another executable which will enable the R2 features.
If you’re already running SCCM 2. R2, the upgrade process will bring your site to SCCM 2.
R2 SP1. Fellow MVP Jason Sandys explain all the upgrade options in an excellent post. The key is really to understand the upgrade process by identifying your actual version and the desired final version.
Prerequisites. Our post focus on what needs to be done to upgrade a stand- alone SCCM 2. R2 Primary Site to SCCM R2 SP1. This post is not covering all the requirements and checklist steps needed if you’re running SCCM 2. SP1 (non- R2). If you have a hierarchy with a Central Administration Site and multiple Primary Site, start with the top of the hierarchy (CAS) and go down, upgrading all Primary Sites and Secondary Sites. If you’re already running SCCM 2. R2, the upgrade process won’t do a site reset : From Technet: When you run this upgrade, it enables additional capabilities throughout your hierarchy. Because this upgrade enables additional functionality and does not upgrade features and components, there are no considerations or changes to settings or site system roles as there is when you install a new service pack.
Database Replication. If you have a database replica for management point, disable Database replication. If you don’t use this function, skip this step and go to the Backup and Testupgrade section. Open the SCCM Console, browse to Administration / Site Configuration /Servers and Site System Roles. Select the Site System that hosts the management point that uses the database replica.
Right click Management point and select Properties. On the Management Point Database tab, select Use the site database and click Ok.
Connect to the SQL server hosting the replica databases. Open SQL Management Studio. Go to Replication / Local subscription. Right click the replica and select Delete. Select Yes to the warning prompt.
Right click the publisher database and select Delete. Select Close existing connections and click OKConnect to the SQL server hosting the site database. Open SQL Management Studio. Go to Replication and select Disable Publishing and Distribution. On the next screen, click Next. Select Yes, disable publishing on this server and click Next, Next, Next.
Click Finish. Backup and Test. Upgrade. Before upgrading, perform a backup of your SCCM database. It is recommended to test your CM database before the upgrade. Detailed procedure is available on Technet, here’s the resumed version : Backup your site databse. Restore it on a SQL server running the same version as your SCCM SQL instance. On the SQL server, run the SCCM setup command line using the Testdbupgrade switch.
Open the log file on C: \Config. Mgr. Setup. log. If the process is successful, you can delete the database copy. If you have errors, resolve them on your SCCM server, do a new backup and restart this procedure.
After you successfully upgrade a copy of the site database, proceed with the “real” upgrade. Running Console. Close all running console on the server. Check also if remotely logged users are running the console in their sessions. The setup won’t check that and you’ll endup having an error in the installation log at the end of the process. ERROR: Configuration Manager console uninstallation failed. Check log file Config.
Mgr. Admin. UISetup. Installation. The installation process is not like a CU installation.
The user experience is like a new SCCM installation. Download the necessary files. You can download the file from the Technet Evaluation Center.
The non- eval files will be available on the Microsoft Volume Licensing Site on May 2. You can install the evalutation version on a non- eval site without problem, it won’t “convert” your site to an evaluation version. You’ll notice that there’s 2 available SP2 executables.
Refer to the table in Jason Sandys post to understand which one to run. Depending of your actual site version and the desired final version)In our case, the site is already R2 so we extract the SC2. SP2_Configmgr_SCEP. Splash. hta. On the main menu, select Install.
On the Before You Begin screen, click Next. On the Getting Started screen, select Upgrade this Configuration Manager site.
On the Microsoft Software License Terms, check I accept these license terms and click Next. On the Prerequisite Licenses, check all 3 boxes and click Next. On the Prerequisite Downloads screen, specify a location to download the prerequisite files.
This folder can be deleted after the upgrade process. The prerequisite files are downloading.
On the Server Language Selection screen, select the language you want to display in the SCCM Console and Reports. On the Settings Summary screen, you will see that you are performing an Upgrade. The Prerequisite Check is running. You should have no errors since your site is already installed and running. Wait for Prerequisite checking has completed and click on Begin Install. The installation is in progress.
The installation will run for about 3. You can follow the progress by clicking the View Log button or open the Config. Mgr. Setup. log file on the C: \ drive. Wait for Core setup has completed and close the wizard.
Verification. Once the setup has completed, there’s a couple of check that you can make to be sure the upgrade process was successful. C: \Config. Mgr. Setup. Display detailed installation steps. Console. Open the SCCM Console and click on the upper left corner on the blue arrow and select About Configuration Manager. The Console has been upgraded to SP1. A new addition is the Site version which was not available on this screen before. Site. Go to Administration / Site Configuration / Sites.
Right- click your site and select Properties. The Site Version and Build Numbers has been upgraded to 5. Clients. The site server client version will be upgraded to 5.
A full list of client version is available on this post. Boot Image. Go to Software Library / Operating Systems / Boot Images. You’ll notice that the Boot Images has been automatically upgraded on your distribution points. Packages. Go to Software Library / Application Management / Packages. The Configuration Manager Client Package has been automatically upgraded on your distribution points.
Database Replication. Enable the database replicas for Management Points, if it was configured before the upgrade. Updating the Clients and Consoles.
Once your site is upgraded, you need to upgrade the clients and console to SP1. Console. You can manually upgrade by browsing to .\Config.
Mgr. Installation. Folder\tools\Console. Setup and execute Console. Setup. exe on each computer running the console. We suggest to create a package or application pointing on the same directory and deploy it using a collection. All clients with the SCCM console installedselect SMS_R_SYSTEM.
Resource. ID,SMS_R_SYSTEM. Resource. Type,SMS_R_SYSTEM. Name,SMS_R_SYSTEM. SMSUnique. Identifier,SMS_R_SYSTEM. Resource. Domain.
ORWorkgroup,SMS_R_SYSTEM. Client from SMS_R_System inner join SMS_G_System_ADD_REMOVE_PROGRAMS on SMS_G_System_ADD_REMOVE_PROGRAMS.
Resource. ID = SMS_R_System. Resource. Id where SMS_G_System_ADD_REMOVE_PROGRAMS.
Display. Name = 'System Center 2. R2 Configuration Manager Console'Clients. To upgrade the clients, you have various options. Automatic Client Upgrade.
Managing Office 3. Updates with SCCMSCCM Office 3. SCCM 1. 60. 2). Prior to this release it was announced as a new features, but it was not completely managed. It was necessary to add Office 3. WSUS manually in order to manage them trough SCCM software update afterward. It’s now manageable natively with the release of SCCM 1. The integration of Office 3. Updates to SCCM will ease overall management of updates with these key features : Centralized management. Standard Software Update.
Ability to use Automatic Deployment Rules. Easier distribution to branch offices with Software Update packages. Applications can run while updating. Before this integration, Office 3. Updates needed to : Manually downloaded. Manually distributed or to create a package than distribution on Distribution Point. Application need to be shut down before the update.
This post will explain how to natively manage Office 3. SCCM 1. 60. 2 and later. Refer to our post on how to deploy Office 2. SCCM if you’re looking at a complete Office 3.
SCCM Office 3. 65 Updates Configurations. There are two ways to configure Office 3. SCCM : Using the Configuration. Click- to- run package. Using Office 2. 01. GPOPrerequisites. SCCM 1. 60. 2 or later.
Windows Server Update Services (WSUS) 4. Office 3. 65 Client – First Release for Deferred Channel version 1. Determine which Office 3. Channel to use. Office Channel.
The Office team has recently changed terminology from Branch to Channel. Before we go on to the configurations details, choosing your management Channel is key for managing updates.
With standard software updates, you probably used different Software Update Group / Deployment to manage test, pilots and production groups to validate updates. For Office 3. 65, similar process can be done. There’s 4 different Channels : First Release for Current Channel. This is basically an Insider build for Office.
Current Channel. Provide users with the newest features of Office as soon as they’re available. First Release for Deferred Channel.
Provide pilot users and application compatibility testers the opportunity to test the next Deferred Channel. Deferred Channel. Provide users with new Office features a few times a year. The best example on how to use this comes from Technet : Provide a group of pilot users with Current Channel, so they can try out the new features of Office as they become available. Provide your application compatibility testers with First Release for. Deferred Channel so that they can test that the finance applications will work with the next Deferred Channel release.
Provide your finance department, which has several key line- of- business applications, with Defered Channel. As of now, only First Release for Current Channel and First Release for Deferred Channel are available in SCCM. Current Channel and Deferred Channel should be available in the next months. Important. Configuration. GPO haven’t been updated to match the terminology of Channels. They both still use Branch. Configure Office 3.
Click- to- Run Package. Extract the files to a drive on your computer. You’ll end up with 2 files – Setup. Configuration. xml.
Edit the Configuration. Change the Branch and Office. Mgmt. COM value to Validation and True respectively. Update : 2. 01. 6- 0.
New screen shot to reflect the new naming convention of Channel in the configuration. Editing the Configuration.
Download and install Office 3. First Release for Deferred Channel. Channel=”First. Release. Deferred”Enable Office to be managed by SCCMUpdate : 2. With the change to Channel, the latest OCT needs to have the new values for Channel instead of Branch. The possible values are : Current.
Deferred. First. Release. Deferred. First. Release. Current. Launch the Office 3.
Setup. exe /configure Configuration. All details about Office Deployment tool can be found on Technet.
Configure Office 3. Update using Group Policy (GPO)Using this method will override configurations made by Configuration. You could use both if you want in order to support already installed Office 3.
Download the Office 3. ADML/ADMXImport ADML/ADMX in your GPO repository. Create an Office 3.
GPO and edit it. Go to Computer Configuration / Policies / Administrative Templates / Microsoft Office 2. Updates. 2 settings must be configured : Office 3. Client Managment. Set this setting to Enabled – This allow SCCM to manage update for Office 3. Update Channel. Set this setting to Enabled. In the Channel Identifier field, enter Validation for First Release for Deferred Channel – (Refer to Technet documentation for Branch Configuration Names – Current, Business, Validation)Update : 2.
As per our testing, the GPO as no impact to change the Channel for Office 3. SCCM. When SCCM manage the updates, it will support only the Channel specified at the installation time.
Example : You install Office 3. Current Channel. You have a GPO setting Channel to Deferred.
You deploy release updates with SCCM for Current and Deferred Channel, the client will only see the update for Current as necessary. Deferred will never be applied.
Configure Hide option to enable or disable updates to ensure user don’t disable updates. Here’s the results in Office when setting is set to Not Configured or Disabled Here’s the result in Office when setting is set to Enabled. Update 2. 01. 6- 0. The Update Enabled element in the configuration.
GPO should be set to TRUE/Enabled. Quote technet : “Also, we recommend that you set the value of the Enabled attribute to True in the Updates element. If you set the value of the Enabled attribute to False, Office 3. Configuration Manager. But, users won’t see any notifications when updates are pending”NOTE: even with this from the Tech. Net Documentation, we can’t say the real impact with SCCM managing the update. We have tested with True and False.
Both times, updates were available within the Software Center as excepted. It might only affect this warning, when updates comes straight from the web without SCCM involved. Configuring Enable Automatic Updates, is also a good idea to prevent clients from updating automatically.
Here’s the results in Office if setting is Not Configured or Enabled. Here’s the results in Office if setting is Disabled. Configure SCCM 1. Later. Software Update Point.
Ensure that you are running SCCM 1. How to verify)Go to Administration / Site Configuration, select Configure Site Components / Software Update Point on the top ribbon. On the Products tab, select Office 3. Client. Update : 2. Warning : Microsoft as gone crazy with the numbers of release for each Channel. You might want to reconsider the way you manage Superseded updates. For example, Current Channel had 4 releases within a month!
Initiate a synchronization by clicking Synchronize Software Updates on the top ribbon. Once the synchronization is completed, Office 3. Software Library / Software Updates / All Software Update. They can be managed just as any other updates. Software Update Group.
Go to Software Library / Software Updates / Software Update Groups. Create a new Software Update Group. Download the update to a new Deployment Package. Be sure to select the needed languages for your environment. Each updates will take more than 1. GB of disk space. Take that in consideration when downloading your updates.
Client Side. Before updating, the Office 3. SCCMInitiate a Software Update Scan Cycle and Software Update Deployment Evaluation cycle on your client. The update will be available to the client. Compared to standard Software Update, the Office 3. Update is not downloaded in your SCCM Cache folder (By default – C: \Windows\CCMCache)Instead, the update will be downloaded in C: \Program Files (x.
Microsoft Office\Updates\Download. The update will automatically clean itself after rebooting. Interaction in Software Center is exactly the same as any other Software Update. Even with all Office products opened during updating, we encounter no problem for the installation, without user interaction.
Once computer is restarted, Office as been updated. SCCM Office 3. 65 Software Update Reports. Related SCCM reports that give you detailed information about Office 3. Software Updates. Contributor of System Center Dudes.
Based in Montreal, Canada, Senior Microsoft SCCM consultant, working in the industry for more than 1. He developed a strong knowledge of SCCM and MDT to build automated OS deployment solution for clients, managed large and complexe environment, including Point of Sale (POS) related projects. Managing Office 3. Updates with SCCM5 - 5 votes.