Microsoft has recently announced the release of SCCM 2012 SP2 and SCCM 2012 R2 SP1. Before performing an SCCM 2012 R2 SP1 upgrade, we recommend that you read carefully all the available resources and carefully plan the upgrade process throughout your SCCM 2012 R2 hierarchy. The good news is that our SCCM 2012 R2 SP1 Upgrade Guide will list everything you need to know before applying this major upgrade to your existing SCCM 2012 installation. We’ve got you covered !
What’s new
The main reason you’ll want to upgrade to SCCM 2012 R2 SP1 is probably for Windows 10 support. No plan for Windows 10 deployment in your organisation? 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 2012 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 2012. (SCCM 2012 RTM, SCCM 2012 SP1, SCCM 2012 R2)
- If you’re running SCCM 2012 SP1 (non-R2) the upgrade process will bring your site to SCCM 2012 SP2
- If you want to upgrade to SCCM 2012 R2 SP1 afterward, you’ll need to run another executable which will enable the R2 features
- If you’re already running SCCM 2012 R2, the upgrade process will bring your site to SCCM 2012 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 2012 R2 Primary Site to SCCM R2 SP1. This post is not covering all the requirements and checklist steps needed if you’re running SCCM 2012 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 2012 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 OK
- Connect 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 TestUpgrade
- 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:\ConfigMgrSetup.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 ConfigMgrAdminUISetup.log.
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 27th. 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 SC2012_SP2_Configmgr_SCEP.exe to a folder and execute 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 30 to 45 minutes depending of your server specifications
- You can follow the progress by clicking the View Log button or open the ConfigMgrSetup.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:\ConfigMgrSetup.log – 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.00.8239.1000
Clients
The site server client version will be upgraded to 5.00.8239.1000. 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 .\ConfigMgrInstallationFolder\tools\ConsoleSetup and execute ConsoleSetup.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 installed
[pastacode lang=”sql” message=”” highlight=”” provider=”manual” manual=”select%20SMS_R_SYSTEM.ResourceID%2CSMS_R_SYSTEM.ResourceType%2CSMS_R_SYSTEM.Name%2CSMS_R_SYSTEM.SMSUniqueIdentifier%2CSMS_R_SYSTEM.ResourceDomainORWorkgroup%2CSMS_R_SYSTEM.Client%20from%20SMS_R_System%20inner%20join%20SMS_G_System_ADD_REMOVE_PROGRAMS%20on%20SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceID%20%3D%20SMS_R_System.ResourceId%20where%20SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName%20%3D%20’System%20Center%202012%20R2%20Configuration%20Manager%20Console'”/]Clients
To upgrade the clients, you have various options.
Automatic Client Upgrade
Using the Automatic Client Upgrade option, your client will be upgraded automatically within x days using the value specified
- Go to Administration / Site Configuration / Sites
- Click on the Hierarchy Settings button on the top ribbon
- Check the Upgrade client automatically when new client updates are available
- Select the desired number of days you want your upgrade to be run
- A schedule task will be created on the clients and run within the specified number of days
Client Push
Create manual collection and use the client push function to deploy your clients. This method gives you more control on the group of computer you are upgrading.
I like to create a collection that targets clients without the latest SCCM 2012 R2 SP1 version. I use it to monitor which client haven’t been upgraded yet.
Here’s the query to achieve this: (You can also refer to our Set of Operational Collection Powershell Script which contain this query)
[pastacode lang=”sql” message=”” highlight=”” provider=”manual” manual=”select%20SMS_R_SYSTEM.ResourceID%2CSMS_R_SYSTEM.ResourceType%2CSMS_R_SYSTEM.Name%2CSMS_R_SYSTEM.SMSUniqueIdentifier%2CSMS_R_SYSTEM.ResourceDomainORWorkgroup%2CSMS_R_SYSTEM.Client%20from%20SMS_R_System%20where%20SMS_R_System.ClientVersion%20!%3D%20’5.00.8239.1000′”/]Report
You can run our Client Health Check custom report to track your client versions.
Additional reference
Microsoft SCCM 2012 R2 SP1 FAQ
Happy updating ! 🙂
165 Comments on “Step-by-Step SCCM 2012 R2 SP1 Upgrade Guide”
Excellent blog post. I absolutely love thiis website.
Contknue the good work!
I gotta say from many different sites for SSCM you can get a quick step by step documentation, but you have basically convert this into baby steps literally speaking ?? Dude you rock!
http://dhjsdhv2667226ll.com
P050WbNuItpNXUs0NHJJ
Hi Great tutorial!
I did the install with no problem in my lab. however, when I tried to do this in production I’m getting an error right after I click on next on the Before you Begin window. it says “The SELECT permission was denied on the object ‘Setupinfo’ database” from what I’ve read its because I didnt run this with the original installer account.
is there a way of finding out what account installed sccm the first time? I’ve inherited the system from a previous sys admin.
THANK YOU
Pingback: Sccm 2012 User Guide | Chornsovanareach
First off, thanks for a great post for upgrading sccm 2012 r2 to 2012 r2 sp1
I have a primary sccm 2012 R2 server, a separate SQL 2012 server, 2 secondary site servers, 6 DP servers, and 3 WSUS servers. All of these are connected by fast connections. Besides making a back up the database, taking vm snapshots of the primary server, database server, and secondary servers, do I need to make a backup of the wsus servers? wsus 1 pulls down updates from MS and replicates to wsus 2 and wsus 3. Is the wsus sql express database effected by the upgrade? Do I need to back this DB up too? Is a reboot required on any of these servers, during the reboot process? If so, what is the order to shutdown the servers and bring them up? Sorry for all of the questions, a lot riding on this upgrade.
Thanks so much,
Mark
VMSnapshots are not even supported.
Hi All,
Can anyone tell me where to run the query to create the Non R2 SP1 collection? I tried to copy/paste the query in the query statement properties but its got syntax errors, I also tried to run it in powershell with the same syntax errors. Can you please advise? THank you
Hi Manueles,
I probably do it in amateur style but nevertheless I managed to adapt this query. Here is it:
select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.ClientVersion != ‘5.00.8239.1000’
Look at it carefully and you will see that I removed all this stuff like and all the other parts within . Then it became usable and perfectly working. Copy and paste it when create a query in Configuration Manager console.
Hi Benoit Lecours
Our system was very slow when installing applications from Task sequences. To finish a Task sequence, we have spent for 10 hours. Our task sequences included tasks : format disk, apply os, windows settings, network settings, device drivers, install power point, active office, active windows….ect…
We saw Install Power point take for 5 hours to finish. We didn’t know how to solve the issue.
We updated to SCCM 2012 R2 SP1 CU3 but didn’t solve the issue.
Hope to receive help from you.
Thanks and Best Regards,
Quang Trieu Minh
Hi everybody,
i have upgraded to SCCM 2012 R2 SP1 from SCCM 2012 R2. However had a error fail update to boot image (x86 and x64) and I repaired boot image (https://www.niallbrady.com/2013/03/20/pxe-boot-failure-after-upgrading-to-system-center-2012-configuration-manager-service-pack-1/). Then my system was good for now.
The reason which I decided to upgrade was slow downloading when clients were downloading from software center. I didn’t know slow downloading will be resolved or not ?
Thanks and Best Regards,
Quang Trieu
We are using a remote SQL 2008 R2 for our SCCM 2012 R2 environment. I’ve upgraded the primary site successfully (and it has pushed out the client updates, etc.). Thing is, our remote SQL server has the following SCCM roles installed (site system, site database, component server and reporting server). When I try to install CU3 on the remote SQL server, it tells me that SCCM is not installed. Do I need to install CU3 on the remote SQL server that hosts the SCCM database?
Thanks
Hi everybody,
i have upgraded to SCCM 2012 R2 SP1 from SCCM 2012 R2. However had a error fail update to boot image (x86 and x64) and I repaired boot image (https://www.niallbrady.com/2013/03/20/pxe-boot-failure-after-upgrading-to-system-center-2012-configuration-manager-service-pack-1/). Then my system was good for now.
The reason which I decided to upgrade was slow downloading when clients were downloading from software center. I didn’t know slow downloading will be resolved or not ?
Thanks and Best Regards,
Quang Trieu
Hi Benoit Lecours
Our system was very slow when installing applications from Task sequences. To finish a Task sequence, we have spent for 10 hours. Our task sequences included tasks : format disk, apply os, windows settings, network settings, device drivers, install power point, active office, active windows….ect…
We saw Install Power point take for 5 hours to finish. We didn’t know how to solve the issue.
We updated to SCCM 2012 R2 SP1 CU3 but didn’t solve the issue.
Hope to receive help from you.
Thanks and Best Regards,
Quang Trieu Minh
Hi,
What are the impacts if we upgraded the server to 2012 R2 SP1 but left the clients at 2012 RTM, no SP installed?
Regards,
Craig
thanks in advance for your response !
I’ve install sp1 on my 2012 R2 environment starting with our primary site. When i went to install it on a secondary through the console, it ran the prerequisite checker and failed. It still says in the state “upgrade” but if you look at the installation status it clearly says failed. There is no Option to click upgrade again to im assuming start the prerequsite check again. I had an old version of sql express 2008r2 sp1 cu4 on there which didnt mean requirements. Since i’ve installed sql 2012 cu2. How can i start it again?
Thanks!
Hello, I run the update without problem.
Client version is 5.00.8239.1301, but I have the problem now with the Remote Tools Agent, it is Disabled.
I check the client settings in SCCM and “Enable Remote Control on clients” is Enabled.
Any Idea.
Hoping you still check this….
Our Primary site is running SQL 2008 R2 for the SQL Server. I was wondering if this would cause any issues during the upgrade? Currently we are at SCCM 2012 R2 RTM, and want to move to R2 SP1 (whatever the current CU is). I saw some mention of SQL Server 2012 Express so that’s why this concerned me a bit. Thanks in advance!
Hi Matthew,
you are good with SQL 2008 R2. Simply validate the SP and CU level.
You have the list here of supported SQL version : https://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SupConfigSQLDBconfig
Jonathan
We’re on version 10.52.4000.0 which I believe, after researching SQL versioning is 2008 R2 SP2. So yay. I’m a newb to updating, but will the update process still work w/o issue? It won’t try and install 2012 express and mount our DB in that will it?
To be aware of the mismatch in filenames when downloading til upgrade files: read this article:
http://blog.configmgrftw.com/service-pack-madness/
Hi
It’s really helpful post.I have upgraded my R2 to Sp1 and also update CU but after up gradation I am facing problem in OSD machines are not joining to the domain before upgrade it was working fine
Benoit, in my environment I have one stand alone primary site, one server hosting SQL database and 14 DPs, I have upgraded the primary site to SP1 successfully, but now I am not able to distribute the software packages on to other DPs. Do I need to upgrade the DPs too to SP1, if so what are the steps for upgrading the DPs?
Also do you have any blogs or links on how to manage endpoint protection on windows 10, I believe Windows 10 comes natively with Windows Defender. Instead of Endpoint Protection, how to manage the default anti-malware on windows 10 by SCCM 2012? Your valuable replies are appreciated.
Thank you for this very informative guide! I had success with the installation process. However I have two oddities after the installation. 1 – when looking at devices, I did a push installation to a handful of clients. They successfully updated to the 5.00.8239.1000 client however “client version” in Config Mgr Console still shows their previous version 5.00.7958.1000 (also the “general information” is not up to date, for example last logon time does not reflect the logons that have occurred). 2 – In Site Components “SMS Provided” shows green/OK but is listed as both TYPE and AVAILABILITY = UNKNOWN. Additionally, SMS_SITE_COMPONENT_MANAGER shows green/OK but is listed as TYPE = Component not installed by Site Component Manager AVAILABILITY = ONLINE.
I was thinking I should do CU1 or CU2.
Thank you again!
Benoit, very nice guide, which I have followed and achieved great success.
I do have a question related to the client upgrade process, however.
We have upgraded our 2012 r2 install to r2 sp1, successfully, and didn’t roll our the client to any machines yet, but some started getting it. We tracked this down to the GPO used to enforce installation (It runs the ConfigMgr Client Setup Bootstrap ccmsetup.msi file). Some of the clients, when processing this policy, reach out to the SCCM hierarchy and verify the site version, and when they compare it to their current client version, and discover a difference, they ask for an upgrade. However we have a large group of clients that do not do this.
We are trying to find out how to control this behavior, as we clearly don’t want half of our environment trying to upgrade at the same time or anything.
Do you have any kind of knowledge of this behavior, or how to change it?
Thanks!
Very good info. Lucky me I came across you website bby chance (stumbleupon).
I have book-marked it for later!
Thanks
The upgrade went smooth and I am able to launch the new Configuration Manager, but I am having an issue when trying to PXE new machines. I am getting a blue recovery screen with an error code that reads:
The Boot Configuration Data for your PC is missing or contains errors
File:\boot\bcd
Error code:0xc000000f
I have tried the simple solutions of unchecking the PXE option, removing the remoteinstall folder, restarting, checking the PXE option, but am still having the issue.
Hi,
Was there an answer to this issue?
I’m currently getting it myself and I’m not having a lot of luck getting around it.
Thanks!
Thanks, this worked great. Thanks for all the explanations and details.
Benoit-
This morning we enabled the automatic client upgrade in our hierarchy and selected the option to ‘do not update servers’ but somehow a few ‘servers’ got the upgrade/created a false positive heartbeat failure in SCOM during the upgrade. Is there an issue w/ the ‘do not update servers’ option? We are running SCCM R2 SP1 CU1 in our environment. Does the CU2 ‘fix’ this issue?
There’s no problem as I’m aware, first time I hear that one. Are you able to see some similarities on the servers that we upgrade ? I would like to submit the case to the product group if you can elaborate a bit
Due to constraints on our network we are unable to perform downloads through installers so I am stuck on the part where you designate the path to install the pre-requisite files. Snippet from logs:
ERROR: Download() failed with 0x80004005 $$
ERROR: Failed to download language pack manifest (0x80004005) $$
Is there a way to gather these installs separately and placing them in the directory in order to utilize the second option “Use previously downloaded files”? Setupdl.exe also fails.
Thanks for the guide!
Hello,
I run SCCM 2012 SP1, one physicall server to run DPM, one virtual with Orchestrator and Config Manager, and one virtual with VMM…
can I upgrade just virtual machine with Orchestrator and Config Manager to 2012 R2 SP1 (Windows 10 client support) and leave DPM and VMM as they are?
DPM is notorious for upgradeing problems, and I don’t have 100% secondary backup site ( few critical databases are on Azure), and I do not want to touch it as long as I can, just let it work…
I know this probably isn’t the right place to ask this but I can’t seem to find a clear answer anywhere ( or i’m just looking in the wrong place):
I know to support windows 10, WSUS needs to be on Windows Server 2012 R2 ( 4.0), but does anyone know the minimum domain and forest functional level you need to be at? i’m thinking ( or wishfully thinking) 2008 for both…Thanks for the help and off-topic advice.
Good afternoon! I have just upgraded my CAS server to CM 2012 R2 SP1 (Still have two primary sites). after taking a look at the console, I realized that the primary sites didnt get upgraded automatically. My question is: Should I ran the SP1 Installation wizard on the primary sites as well? (As we normally do for any CU (Cumulative Update)?
Thank you in advance.
Eden
Hi,
This was a great step by step and most of it went smooth.
I am still dealing with an issue with my configuration manager client and upgrade package failing to update the distribution points. has anyone else had issues with this?
It’s basically telling me there is an access issue or permissions issue. I have 3 new DP’s I brought into the hierarchy after the upgrade and those transferred just fine.
Hi Benoite,
Thanks for sharing step by step information related to SCCM 2012 Upgraded. I followed the steps as well. Everything goes smooth except that:
1- The console setup is showing an error: There is not enough available disk space on to complete this operation. Installation requires at least 20MB free disk space.
2- OSD stopped working.
Do you have any idea regarding the OSD, which is failing with an error:
Operation aborted (Error: 80004004; Source: Windows) TSManager
Failed to run the last action: Apply Operating System. Execution of task sequence failed.
The system cannot find the file specified. (Error: 80070002; Source: Windows) TSManager
Hasnain.
The error is stating that your WIM file referenced in your TS can’t be located. If you open your TS, go to the Apply OS step and check that the WIM package can be accessed.
Hi
After the upgrade to R2 SP1 will all my MDT integrated boot images also be upgraded and automatically distributed to my distribution point? or do I still have to re-generate these and distribute them again?
Thanks
K
Something worth a note when running the /testdbupgrade is that, for me at least, it restarted the SQL service. If this is a test SQL server you are running this test on that has ‘other’ databases in use at the time you might be in for a nasty shock!
True ! and that’s why my article mentionned doing this on a copy of the DB.
Has anyone started having OSD issues after upgrading to SP1/CU1? After the upgrade OSD fail on the “Setup Windows and Configuration Manager” step. The error is “The system cannot find the file specified”, the file it is referring to is the Configuration Manager Client Package, however it is distributed to the DP.
You need to run ccmsetup.exe first and then cu1 package or else client upgrade won’t happen
Can you post a screenshot of your TS on the client step ?
Hi,
I’ve completed the upgrade, but it seems the clients are not upgrading. Even the client on the server hasn’t been upgraded. The clients are still set to 5.00.7958.1000. I have automatic client upgrade enabled and set to 1 day, and it’s showing the correct updated client version in the automatic client upgrade window (5.00.8239.1000). I’ve tried a manual client push on some machines and that appears to be failing as well. The site version and build number are correct in the console. And I’ve been able to update console on workstations without any issues. It’s only the clients giving me issues.
Can anyone assist?
What’s the error you are getting while upgrading client? Did u tried making client package available in software center and tried installing from there. Post error code as well
I’m not seeing anything in the event logs. Is there some other log that I can review to see an error code? I’m not seeing any actual error windows pop-up during the installation. The installation just isn’t happening.
I’ll try deploying the client upgrade as a package. I notice there is already a Configuration Manager Client Packager listed under packages but all the properties are grayed out and I’m unable to deploy it.
I would suggest that you refer to the SP1 installation log to see if the Client Package had errors during creation.
Thanks for posting the article, it would help to achieve the upgrade process in our environment,
Well, just wanted to know, once the site is upgraded to SP1, can we use Automatic site wise Client push method to install and upgrade the client version to the latest 5.00.8239.1000.
And if some of the clients didn’t upgrade, will SCCM 2012 R2 SP1 still manage the systems with older client version 5.00.7958.1000?
Yes, automatic client upgrade is the easiest method to upgrade.
Your SP1 site can manage older version without problem. I would create a colleciton with the outdated client and try a deployment of the client using Client Push or the package.
You can refer to my collections script for that (the collection is included in the script) : https://gallery.technet.microsoft.com/Set-of-Operational-SCCM-19fa8178
Thanks For your Reply Benoit! However my next query is, after the site is up graded to SP1, Will the client setup up in the client folder of SCCM installation directory (\client)and SCEP setup files (I,e ccmsetup.exe and scepinstall.exe) both be upgraded and can we use those setups as a standalone install for creating our new Windows 10 Image? Will it support?
Thanks
Great post, Thanks.
I was wondering roughly how much time should be alloted to go from 2012 R2 to SP1 CU1? Including test and Prod?
Thanks again
That’s really depend of your environment and risk you’re willing to take. I’ve updated thousands of clients without major issues.
I have SCCM 2012 R2 issues after upgrade to R2 SP1, the SMS Agent Host service restarts and stops
Any idea?
Thks, Regards
Check the ccmexec.log on the client
Great article Benoit.
One question on the updated configuration manager client package, do i have right click on the package and select the option to update distribution points after upgrading SCCM 2012 R2 to SP1 or will the option “Automatic Client Upgrade” enabled be enough?
The default package should update automaticaly, check the distribution date. It should match your SP1 installation date.
Question: We are about to introduce Win10 clients into our environment. Is R2 SP 1 needed to manage these clients? Specifically to client push and so SCEP installations?
Right now, none of our Win 10 clients are getting the SCCM client or Antivirus. They are generating various errors but I think the issue is that the environment needs updating. I just want to confirm that.
We are on SCCM 2012 R2.
Thanks for your help!
Yes, you need to update to R2 SP1 to manage Windows 10 client. Check our post on Windows 10 and SCCM 2012
Thank you for your response. I have one additional question. our WSUS (3.2) is on the same server… do we need to do anything with it certificate or upgrade-wise, or will it work out of the box with this update no problems?
Appreciate the help!
David
You don’t have to do anything else for WSUS.
How we can upgrade the secondary sites with SP1. we can run the same setup using for primary site
Use the console to update secondary site. Click your Secondary site in the Administration node and use the ribbon function to upgrade
Hi Benoit,
thanks for your post.
I’m just wondering about this sentence:
“In our case, the site is already R2 so we extract the SC2012_SP2_Configmgr_SCEP.exe to a folder and execute Splash.hta”
If you are already at R2 stage, do you not need to use the R2 Upgrade?
Cheers, Christian
If you’re already running R2, just run the SP2.exe
HI,
1. I am on SCCM 2012 R2 CU2 , do i need to go on CU5 first before upgrading to Sccm 2012 R2 Sp1. This Question is raised because (https://technet.microsoft.com/en-us/library/dn973021.aspx , After you upgrade a central administration site to System Center 2012 R2 Configuration Manager SP1, replication between sites fails)
2. I have ADK 8.1 installed accross my org, is there any new version or can continue with it ) and also when has this to be done before running R2 SP1 or after upgrade
3. Also MDT 2013 is installed in my ORG do i need to install the MDT 2013 Update 1 version as well.
PLease reply.
1. You can go directly to SP1, no need to apply Cu5 first.
2. You don’t need to upgrade your ADK except if you need to deploy Win10. See my Win10 post for this. http://www.systemcenterdudes.com/managing-windows-10-with-sccm-2012/
3. MDT, same as #2.
what about the Existing Remote site Management point and Distribution point upgrade roles from SCCM 2012 R2 to Sccm 2012 R2 SP1 upgarde?
You don’t need to update remote MP and DP. Only site servers (CAS,Pri,Sec) and computer running SMS Providers.
Hi
I am planing to upgrade sccm 2012 R2 to Sccm2012 R2 SP1.This site really helps a lot.
could you please suggest me How can i upgrade the existing remote site sytem roles for Management point and Distribution point which are configured on sccm 2012 R2.
Regards,
Satish Thota.
You don’t need to update remote MP and DP. Only site servers (CAS,Pri,Sec) and computer running SMS Providers.
Questions about the Database Replication section. We had a Database replica at one point but that has been turned off for sometime in the SCCM Console. On the SCCM server that was hosting the replica I see there is nothing under Local Publications but there is still a Local Subscription. Under Subscription Properties the Status of Last Synchronization is the current date and time. Can it just be deleted? You say, Right click the publisher database and select Delete. Is this referring to the Replication/Local Publications? – as shown in the screenshot. The first screenshot you have is more or less what I am seeing on the SQL Server hosting the Site Database not the server hosting the replica.
How would one go about changing the underlying OS that the current SCCM 2012 R2 CU5 environment runs on from a 2008 R2 to 2012 R2 (OS) versions?
Server 1: Primary site only, MP, DP, SUP, Application Catalog web service/website point
WSUS/SCUP 2011 (using Enterprise PKI based certs on the same OS where SCCM) – but we’re not using SSL to communicate with the sccm agents.
While this server has MDT installed on it we don’t use it…
Server 2: Site db role/reporting services point w. SQL (would like to upgrade that to 2012 R2 OS and 2012 R2 SQL as well.)
+ about 35 other DPs wit PXE boot (2008 R2) – we can’t change these OS’
Proposed idea:
Pause/Stop all deployments; backup SCCM & Backup SQL SCCM DB
Make a note of the SCCM services and Set them to Manual then Turn off SCCM primary servers (this would aid in recovery/undo steps if needed later)
Build two new VMs with 2012 R2 OS with the same name(?) – Reset AD account and the join new Server(s) to inherit the same SID.
Installl SQL 2012 R2 Standard OS w SQL 2012 R2 on server
Restore DB & permissions (local admin groups & SQL DB permissions)
On SCCM 2012 R2 Standard OS Server – similar specs & drive layout/partitions etc.
Restore all “source” files & shares to the same paths as on the previous OS
Install software/patch prereqs
Install WSUS prereqs (not sure on order?)
Run the SCCM 2012 R2 SP1 setup and choose to recover site
Install SCUP 2011 (?) – This may have to be done on another box due to WSUS/SCUP issues (suggestions?)
I am currently running SCCM 2012 R2 and planning to upgrade to R2 SP1. The “Backup and TestUpgrade ” process is mandatory because my database is configured on a different server where I don’t have proper access to that. Can I run SC2012_SP2_Configmgr_SCEP.exe as it is?
It’s strongly recommended but not mandatory, it will let you know if the upgrade will work or not.
Question about the testupgrade.
I’m assuming you run the testupgrade against the backup copy of the database?
Yes, you have to mount your CM DB on a separate server to do the TESTUPGRADE procedure.
Hi Benoit,
We are currently on CM2012 R2 CU4 and planning for SP2 and then to CU1. Can we directly update the clients from R2 to sp2 CU1 or first it needs to be updated to SP2 and then CU1?
I haven’t test this scenario but I think you should be fine to go directly to SP1 CU1. I can’t find any technet documentation concerning that scenario
Thanks! You helped me upgrade our enterprise environment at our College District! 🙂
Have you ever seen this upgrade break a Distribution Point on a Windows Server 2008 SP1 Enterprise edition? After the upgrade, our primary site has been unable to send or update any deployment package anymore. I looked at the Configuration Manager Status message and it give me this message for all deployment packages that it’s trying to deploy to it. The rest of my DP’s are Windows Server 2012 R2 Standard and did not experience this issue. Would it be possible that Windows Server 2008 SP1 edition is not supported anymore by SCCM 2012 R2 SP1 update? I also upgraded our environment to CU1 and still same issue.
Distribution Manager failed to process package “Configuration Manager Client Package” (package ID = CAS00002).
Possible cause: Distribution Manager does not have access to either the package source directory or the distribution point.
Solution: Verify that distribution manager can access the package source directory/distribution point.
Possible cause: The package source directory contains files with long file names and the total length of the path exceeds the maximum length supported by the operating system.
Solution: Reduce the number of folders defined for the package, shorten the filename, or consider bundling the files using a compression utility.
Yes, I’ve already seen this issue but with SP1 (the first SP1, non R2).
Take a look at this thread and let me know if it works for you :
https://social.technet.microsoft.com/Forums/en-US/8e860651-4288-42c1-b04f-c6ac72dd02f1/help-big-issue-with-primary-dp-after-updating-to-sp1?forum=configmanagergeneral
Thank you for this! It was very helpful and worked a charm. Have you heard of anyone having OSD issues with installs from OS Upgrade Packages post 2012 R2 SP1 CU1 their upgrade?
All of a sudden our OSD installs that use workgroup VMs start trying to talk to the MP designated with ccmsetup using /ccm_system_altauth as the request path during the client install. Which is odd for us, we need our workgroup installs to talk to an HTTP only MP which does not have that altauth app installed. Just curious if you have heard of anyone with a similar issue?
No sorry, never heard of that.
Are you using any PATCH parameter in your client deployment ?
Thanks for the reply! As it turns out our issue was with not pointing to the right MP to start with using the SMSMP parameter.
I was pointing our Build and Capture task sequence to the HTTP MP direct and it would fail to hit the /ccm_system_altauth URL (which doesn’t exist on that MP). After ensuring the HTTP MP was published in DNS (originally it wasn’t) I was able to point the task sequence “Setup Windows and ConfigMgr” step to the primary MP (which is HTTP & HTTPS).
Voila, the ccmclient during the Build and Capture TS is now able to talk to the MPs and gets directed to the HTTP MP even though the SMSMP parameter on ccmsetup is pointing to the HTTPS MP.
The story has not yet ended though. We have B&Cs for Win7/8.1 & 10. The Windows 7 B&C successfully runs right through, it installs all applications (Office 2013, Adobe Reader etc) and captures. The Windows 7 installer is also an offline serviced install.wim with Windows Updates up to August all folded in. Works a charm.
The Windows 8.1 image also has a bunch of updates folded in. It chokes installing the Applications though, so does the Windows 10 image and they do so in the same manner. Basically they try to pull the policy for the application install and they die, they die because they try and talk to the HTTPS MP (as far as I can see).. which of course they shouldn’t they should talk to the HTTP MP and they do for everything else. Sigh. Google says that this is pretty common and people choose to install their apps by packages etc.
It is just odd though, the same TS worked prior to our upgrade. Also to make it a little more odd and maybe annoying.. it does work for the Windows 8.1 B&C if we use the default ISO as the installer. So maybe it is a Windows Update somewhere that is now folded into Windows 10 by default. Ahhhh well. I give up, unless anyone has hints??
I think we might just move the applications into our final “Live” task sequences for deployment.
Hi,
How do SUP work between CAS and the primary sites? Does it work if only WSUS and SUP is install on CAS server and just SUP install for the rest of the primary sites and it will sync across the main catalog from the CAS? Or rather need to install WSUS and SUP individually for each primary sites to work for the synchronization of the catalogs? Does the replication between the SUP using sql replication via the sql broker and sql instance port?
Thanks.
Hi,
I think this sentence should be updated.
In our case, the site is already R2 so we extract the SC2012_SP2_Configmgr_SCEP.exe to a folder and execute Splash.hta
Since we’ve got R2 already, the upgrade path for us would be R2 SP1, not SP2.
Thanks!
Hi Stephen,
Thanks for the comment. Even if you have R2, you need to use the SP2 bits to upgrade. The site will be R2 SP1 after the installation.
This is well explained at the start of the article. Sorry if I misunderstand you 🙂
Ive upgraded my site to 2012 R2 SP1 + CU1. With automatic update enabled.
My workstations clients are slowly updating to the newest version, except any of the servers.
The options under automatic update clients is de-selected so that should be ok, but somehow the servers are not getting the nesessary task.
How many days did you selected ?
7 days.
Also when i start several tasks cycle it wont create any task scheduler tasks.. (servers)
Any maintenance windows applied to your serers ? If you enable Automatic Client Upgrade and have maintenance windows applied to your clients, the clients will adhere to the maintenance windows regardless of the Automatic Client Upgrade checkbox. Therefore, if the clients are not in a maintenance window when the scheduled task runs, the automatic upgrade will not take place.
Yes the servers have maintenance windows. I had an idea that could effect this… So what’s the best approach for updating the server clients? Re-run Install client task?
I would use client push as you have more control on it. (Create a collection of the target systems and deploy)
Hi
I am trying to run the SC2012_SP2_Configmgr_SCEP splash, I click install but the upgrade option is greyed out. the only option I have is to uninstall.
I have SCCM 2012 R2 version 5.0.7958.1000 installed at the moment.
do I have to run another update before I can upgrade?
thanks for helping
Jason
I’ve updated to CU5 but the upgrade option is greyed out still.
Found this fix. upgrade option is available now. gonna try and upgrade.
To Fix:
– In the registry, under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Setup\Phase
– Change 7 (Decimal) to 255 (Decimal)
– Rerun the “Configuration Manager 2012 SP1 Setup Wizard”. You will now have these options:
+ Upgrade this Configuration Manager site
+ Recover a site
+ Uninstall this Configuration Manager site
Hi Jason,
First time I heard about this. Where did you find the solution to this ? Is is documented ? I would like to try to replicate this in my lab. Thanks.
Hi
I think when I originally installed SCCM there might have been an issue I was unaware of and that’s why it was grayed out. I found the fix here.
https://social.technet.microsoft.com/Forums/en-US/91e7c82d-f32b-419d-bbb9-3a2518aef086/install-option-to-upgrade-this-configuration-manager-site-to-sccm-2012-sp1-is-not-available?forum=configmanagerdeployment
I have now successfully upgraded and have deployed the client, all thanks to your instructions. Thanks
I ran the testdbupgrade successfully and moved on to running the upgrade on my development SCCM2012 server. It failed with below error message.
ERROR: SQL Server error: [42000][4929][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot alter the table ‘MeterData’ because it is being published for replication. Configuration Manager Setup 8/25/2015 2:39:32 PM 4184 (0x1058)
*** declare @VarName nvarchar(128) ~declare @VarSql nvarchar(400) ~select @VarName = OBJECT_NAME(parent_object_id) from sys.objects where object_id = OBJECT_ID(N’meterdata_pk’) ~IF @VarName IS NOT NULL ~begin ~ SET @VarSql = N’ALTER TABLE ‘ + @VarName + N’ DROP CONSTRAINT [meterdata_pk] ‘ ~ execute(@VarSql) ~end Configuration Manager Setup 8/25/2015 2:39:32 PM 4184 (0x1058)
*** [42000][3727][Microsoft][SQL Server Native Client 11.0][SQL Server]Could not drop constraint. See previous errors. Configuration Manager Setup 8/25/2015 2:39:32 PM 4184 (0x1058)
ERROR: SQL Server error: [42000][3727][Microsoft][SQL Server Native Client 11.0][SQL Server]Could not drop constraint. See previous errors. Configuration Manager Setup 8/25/2015 2:39:32 PM 4184 (0x1058)
INFO: Executing SQL Server command: Configuration Manager Setup 8/25/2015 2:39:32 PM 4184 (0x1058)
ERROR: Failed to execute SQL Server command: Configuration Manager Setup 8/25/2015 2:39:32 PM 4184 (0x1058)
ERROR: Failed to clean up SqlKeys array. Configuration Manager Setup 8/25/2015 2:39:33 PM 4184 (0x1058)
~===================== Failed Configuration Manager 2012 Server Setup – Upgrade ===================== Configuration Manager Setup 8/25/2015 2:39:33 PM 4184 (0x1058)
I verified beforehand that Management Point Database was not using database replica. I’m at a loss.
So I figured out how to remove the replication from http://blog.extreme-advice.com/2012/11/06/remove-replication-from-sql-server-2012/.
ERROR: SQL Server error: [42S02][208][Microsoft][SQL Server Native Client 11.0][SQL Server]Invalid object name ‘dbo.fn_SplitString’. : MDM_ProcessUserAssignmentForApp Configuration Manager Setup 8/25/2015 3:21:30 PM 4600 (0x11F8)
~===================== Failed Configuration Manager 2012 Server Setup – Upgrade ===================== Configuration Manager Setup 8/25/2015 3:21:30 PM 4600 (0x11F8)
How to disable replication was available in our procedure. Was it missing something ? Just to know if I need to update it.
Have you try a complete server reboot after disabling the replicas ?
When I started I verified that Management Point Database replication was disabled. This is a single site. It appears my predecessor must have enabled it at one time. When I removed replication via SQL studio and restarted the upgrade that’s when I got the other error ERROR: SQL Server error: [42S02][208][Microsoft][SQL Server Native Client 11.0][SQL Server]Invalid object name ‘dbo.fn_SplitString’. : MDM_ProcessUserAssignmentForApp Configuration Manager Setup 8/25/2015 3:21:30 PM 4600 (0x11F8).
I restored both the site server and database server from a vm snapshot and I’m starting again. Removing and disabling replication from SQL first.
After making sure to remove and disable replication via SQL studio I was able to complete the upgrade. Just one critical error left to resolve.
Hi,
I have a query on software patching of CAS and its remote SQL server.
If CAS cannot manage client and there is no DP and MP, how do I do software update on the CAS server and its remote SQL server?
Is it better to upgrade from primary sites to CAS rather than freshly installed CAS as the standalone primary site will be converted to a child primary site and therefore able to manage and do software update on itself and the remote SQL server?
Thanks in advance.
I recently thinking of managing my 3 environment with SCCM. This is one of the considerations being inquired too. Hope can get some help too.
Hi
sorry but my english is poor.
I upgraded today my infrastructure TEST (not in production) of sccm 2012 R2 to SP1 with successfully. thanks for your guide :-).
I have on primary server and 2 servers distribution point.
In the console, I see a new package named : “configuration manager client upgrade package “. is it normal ?
because, the package (Configuration Manager Client Package) is already present and is up to date and copied on server DP.
however, the new package “the configuration manager client upgrade package ” is bloked. update content on distribution point doesn’t work.
can you help me ?
thanks in advance
Bonjour,
Je vous suggère de lire cet article qui explique bien les 2 packages. Tout est normal dans ce que vous décrivez.
http://www.vansurksum.com/configmgr-2012-what-to-do-when-the-configuration-manager-client-upgrade-package-is-deleted-somehow/
Hi thnx for this guide. Im planning to install SP1, but im questioning myself if i have to install CU1 right after it and then update the local clients…
Or should i install SP1 first then wait for all the clients to be updated?
Hi Rogier,
If you’re planning to install CU1 after the setup, go directly to the CU1 version. You could then use the new automatic upgrade feature to ease the work.
Don’t bother updating twice your clients.
Hi Benoit,
So if im clear: i can install SP1 and after that i can install CU1 and then focus on (auto) deploying the CU1 version?
Yes
Anyone know how to create an application or package to push the R2 SP1 admin console out as an upgrade or new installation?
I’ve tried building one with AdminConsole.msi and ConsoleSetup.exe. I’ve tried /q with parameters and I tried it without /q and no parameters. Nothing seems to work. Always fails.
i would like to learn about a proper way of creating package for the console push out too! thanks!
Hi Mark,
Have you try to use an application to install the console instead of package?
You can follow the guide.
Thanks
I did get this to work creating an application. My problem was that I was leaving off the TargetDir switch when using /q. I did not know that was a required switch with /q. Thank you for helping!
Pingback: SCCM 2012 R2 SP1: Boot Image issue | IT Consultant Everyday Notes
I’m on a test CM12 VM now. It has not been moved into production. Can I take a snapshot and run the Testdbupgrade with out having to copy over to another SQL box?
You could try but that is unsupported.
Hi,
Can any tell me how i can upgrade SCCM2012 R2 SP1 as I think it is RTM version. I installed SCCM2012 R2 SP1 successfully but when i clicked on Software Library then i cannot see the “Operating system Installer” link. Please guide me how i can get this link as SCCM console shows me “Operating System Images” link. Thanks, Adnan
It has been renamed to : Operating System Images and Operating System Upgrade Packages due to some confusion in the naming.
Use Operating System Images for your custom WIM
Use Operating System Upgrade Packages for full media
Thanks a lot for this great article. I just completed my upgrade and everything looks fine.
Thanks for the comment !
Hello,
I followed your article and my server updated just fine. here’s my issue that I hope you can help with. I run the SCCM console on my local machine after I upgraded the server to SP1 following this article I can open the console on my server but I can’t open it on my local machine anymore. I get a screen telling me “Configuration manager cannot connect to the site (site name here)” I have a “connect to site” button which when I click it has my servers name in there but still wont connect.
what do I do now???
I also have 12 more users that have the console on their local machines too with the same issue
Hi Michael,
Have you updated the console on your machines also ? Each console needs to be updated. See our “Updating the Clients and Consoles” section to know how to proceed.
I’ve same situation. It’s very weird, but after sucessfull upgrade I can connect to Site via old console. Upgraded console doesn’t work.
Maybe I should wait for finished background tasks after upgrade? I found great article that after upgrade Site is not fully operated:
http://henkhoogendoorn.blogspot.com/2015/05/doing-configmgr-2012-r2-sp1-upgrade.html
When I tried to upgrade first time, after success info I’ve the similar issues like he described – no info about component status, client agent still not updated etc. Unfortunately I wasn’t wait and revert my Primary site and database site to 2012 R2 state 🙂
Now I’m going to be more patient 🙂
The file I used was SW_DVD5_Sys_Ctr_ConfigMgr_and_Endpnt_Prtctn_2012w_SP2_MultiLang_MLF_X20-21849.ISO
This was going from 2012 R2 to 2012 R2 SP1 BTW
i see that you used volume lic to grab the file. how did you go with this iso? as far as i know we should use different files for the upgrade, unless im wrong, thanks.
Hello Benoit,
My question is also regarding the confusing file names.
Our boss downloaded an .iso file from Microsoft Volume Licensing website and I want to make sure we are using the right one.
We are currently on SCCM 2012 R2 CU2. We want to go to SCCM 2012 R2 SP1. The file that was downloaded for us to use is the following: SW_DVD5_Sys_Ctr_ConfigMgrClt_ML_2012_R2w_SP1_MultiLang_ConfMgr2_MLF_X20-21853.iso.
When I extracted it, the only msi i found in there is the following:
Configmgr2012R2SP1.msi
When I run the splash screen clearly states the following:
System Center 2012 R2 Configuration Manager SP1
and there is only Upgrade not Install option.
Is this the right file for our environment???
Thanks in advance,
Jose
Jose,
Just last night I upgraded our environment from R2 CU5 to R2 SP1. You definitely need to use SC2012_SP2_Configmgr_SCEP.exe, the size of which is 780,310 KB. Your boss can download it from the MVLS site.
Jose,
My bad. I was misinformed about the source of the file. We downloaded it from the TechNet evaluation site. Since we’re already licensed it applied just fine:
https://www.microsoft.com/en-us/evalcenter/evaluate-system-center-2012-r2-configuration-manager-and-endpoint-protection
Right so since we are not getting it from the TechNet evaluation site, I wonder if the file is named differently on the MVLS site?
Jose, there is no such as file available on MVLS, checked that multiple times and no luck, M$, it’s a shame!
Benoit
Do you have any insight on how to create a package\program to upgrade the clients instead of the automatic option?
-Tony
Hi Tony,
The default client package will be automatically created with the SP1 bits.
Hi Benoit, great post thx!
how long it takes to create the packages, AFAIR with CU4 update i got straight away.
i understand they should show under packages?
thanks
The SP1 packages are not “separate” package as the CU one. It will update the default Configuration Manager Client Package.
Pingback: Upgrading SCCM 2012 to R2 SP1 | Adam Akers Blog
Thanks Benoit, very helpful.
Had a new install of ConfigMgr 2012 R2 up and running, getting ready for migration from 2007. Went through the step by step to get the new server updated, no issues.
Thanks !
Links to the Jason Sandys articles appear to be broken.
On our side, the link is working. Are you talking about this one?
http://blog.configmgrftw.com/service-pack-madness/
Thanks
Interesting. Wasn’t working yesterday but it’s working now. Thanks.
Hi Benoit, thanks for the guide. The update went fine, however I have a couple of issues, post-upgrade. The boot image aren’t showing the update date as their “Last Update” and the client (only have 1 in the dev environment) isn’t being updated, even though I have the server set to automatically update the clients.
Under Packages, the Configuration Manager Client Package was updated, but under the sub-folder Configuration Manager Updates, where previous (CU1, CU2, etc) client updates are, there’s no SP1.
Thanks in advance,
Dan
Hi Dan,
For your installation error I suggest that you review the installation log.
For your packages, SP1 doesn’t create a specific client package as CU does. The default “Configuration Manager Client Package” is updated to the SP1 version.
Hope it helps.
Hi Benoit, thanks for your reply.
The boot images I’m not too worried about, since I’m not using the Dev environment (nor the Live one for now) for OS deployment. Odd though, the log says SCCM is unable to automatically update customized boot images, though I don’t remember changing.
As for the client update, I managed to get past a few issues and while it’s still not working, at least SCCM _is_ trying 🙂 The ccm.log shows the error “Execute query exec [sp_CP_SetLastErrorCode] 16777219, 0” after which it closes the request.
On the client side, the ccmsetup log shows this:
<![LOG[]LOG]!>
It’s odd that it says the site’s version is 5.00.7958.1000 since it clearly isn’t…
Any thoughts?
Dan
Sorry, don’t know why the log text was cut from my reply, I’ll try again:
<![LOG[]LOG]!>
And again… this time without the opening and closing tags:
Retrieved client version ‘5.00.8239.1000’ and minimum assignable site version ‘5.00.8200.1000’ from client package]LOG]!>]LOG]!><time="11:58:51.721-60" date="06-18-2015" component="ccmsetup" context="" type="1" thread="2644" file="ccmsetup.cpp:10802"
Benoit,
Great guide btw, I have 2 questions.
1. you said I don’t need to create client package as CU, which I did for CU5. How does the existing CU5 clients gets updated to SP1? How do I manually upgrade them, with what package?
2. I had the same issue with SP1 not updating my boot image, saying it was customized. Do I need to update it? What is the boot image version for SP1?
1. The default Configuration Manager Client Package will be updated with SP1. To update your clients, use the methods provided in the guide
2. The boot image version is 6.3.9600.16384
6.3.9600.16384 – is that the updated version?
i can see this version but date created points to the time i applied CU4, any clue please?
thanks
So no need to upgrade the secondary sites? We have a single primary with 3 secondaries.
Thanks.
Thanks for pointing that out, i’ll update the article for secondary site.
Yes, secondary sites must be upgraded to SP1.
Go to : Administration / Site Configuration / Sites
Check your secondary site version (add the column if necessary)
Select your Secondary site and click Upgrade on the top ribbon
Important consideration from Technet :
When you plan to upgrade a secondary site that uses SQL Server 2012 Express with no service pack it is recommended to must first apply cumulative update 2 to the SQL Server 2012 Express installation on the secondary site server.
This is because, when Configuration Manager installs SQL Server Express as part of a new secondary site installation, it installs SQL Server 2012 Express with no service pack and is unable to install the required cumulative update 2 as part of the installation. When you direct Configuration Manager to install SQL Server Express as part of a new site, the prerequisite check does not detect an existing installation of SQL Server Express, and then installs SQL Server Express as part of the site installation.
Thanks for the info! Do you know if this Upgrade process forces all content (packages, applications, etc) to be redistributed from the primary site to the secondary site? The warning that you receive about needing to remove and re-install all site server components makes it seem as if the DP role would be removed.
No, content should not replicate after the upgrade
Hello. Thanks for the tutorial.
But I stuck on step “System Center Configuration Manger Setup Wizard”, “Upgrade this Configuration Manager Site” radio button is grayed out, and unavailable. What might that be? Thanks in advance.
Which options are available ? Are you running the wizard on the server ? It must not be launch from your workstation.
Thanks for reply. But i already resolved the issue by myself. I had this issue
http://larslohmann.blogspot.ru/2014/06/sccm-2012-r2-testdbupgrade.html
and edited the registry. I restored the registry and this helped to me. Thanks again.
Pingback: Our favorite SCCM 2012 R2 SP1 New features « Li Min's Site
Wow that is very confusing. Thanks for the explanation and keep up the great articles!
Thanks !
Hello,
As always a very informative how-to.
I am a little confused by “In our case, the site is already R2 so we extract the SC2012_SP2_Configmgr_SCEP.exe to a folder and execute Splash.hta”. If you are already on SCCM 2012 R2, wouldn’t you want to run the SC2012_R2_SP1_Configmgr?
No, if you’re on R2 you have to run SC2012_SP2_Configmgr_SCEP.exe… It’s not an error. This is why we created the Naming Confusion section. 🙂
The smaller .exe is just to enbale the R2 features which you don’t need since you’re already R2.