NOTE: the KB has been updated with a workaround for this issue
Lovely weekend, upgraded from SCCM 2012 R2 SP1 CU2 to 1511, then 1602, then hotfix KB3155482. At the end, we end up exectly like this, Client Upgrade shows old client version numbers, and SCCM Client package is not updated.
Big thanks for ‘s windows-noob Facebook group, point me out technet forum has same discussion of this matter, –Marc– has reported as bug to MS. https://connect.microsoft.com/ConfigurationManagervnext/feedback/details/2803952
So if you don’t wanna end up like me, please remember promote automatic client upgrade to production before you install this hotfix to your site system.
Here is the fix, Wrex mentioned it in technet forums:
- If you have another test envirment what is upgraded sucessfully, copy all the files from CMUClient from that server to your CMUClient folder, go to step 3.
- If you don’t have another test envirment you can copy those files from, do this:
Go to EasySetupPayload folder, you will find two folders inside it. Sort them with time stamp, the older one is 1602 installation media, new one is hotfix KB31554821) Open the 1602 folder:
1.1) copy all files from “SMSSETUPCLIENT” to “your SCCM installation pathCMUClient”
1.2) copy msrdcoob_amd64.exe, wic_x64_enu.exe and WindowsUpdateAgent30-x64.exe from “redist” to “your SCCM installation pathCMUClientx64”
3)copy ndp452-kb2901907-x86-x64-allos-enu.exe, msrdcoob_x86.exe, silverlight.exe, wic_x86_enu.exe, windowsupdateagent30-x86.exe from “redist” to “”your SCCM installation pathCMUClienti386”
(Optional) If you have choose multiple language in your site, copy also language pack from “redistLanguagePackClient”
Example. Finnish launguage, choose FIN folder, copy “redistLanguagePackClientFINsmssetupClient” to “your SCCM installation pathCMUClient”
2) Open the hotfix folder:
copy all files from “SMSSETUPCLIENT” to “your SCCM installation pathCMUClient”, overwrite older files.
- Open “SQL Manangement Studio”, choose your CM site database, right click, create “new query”, excute this:
select * from ClientBaseline
select * from ClientDeploymentSettingsYou will see version are “5.00.8325.1000”
then excute this:UPDATE ClientDeploymentSettings SET UpgradeVersion = ‘5.00.8355.1306’ WHERE UpgradeProgramName = ‘Configuration Manager Client Upgrade Program’
UPDATE ClientBaseline SET Version = ‘5.00.8355.1306’ WHERE Name = ‘Staging Baseline’
select * from ClientBaseline
select * from ClientDeploymentSettings
You will now see Staging Baseline version is “5.00.8355.1306”
- Update “Configuration Manager Client Piloting Package” package. Open Admin console, go to Applications-Packages, Choose “Configuration Manager Client Piloting Package”, Click update distribution points.Wait until if finished. If you don’t see “Configuration Manager Client Piloting Package”, close Admin console and reopen Admin console as Administrator.
- Check your site hierarchy settings, Client upgrade tab. Pre-production client version should be “5.00.8355.1306”. Uncheck “Upgrade all clients in the hierachy using production client”, if it was checked..
- Now you should able to choose Client Update Options again.
- Choose “I am ready to make pre-production client version available to production”, then OK.
- Check your site hierarchy settings, Client upgrade tab. Production client version should be updated as “5.00.8355.1306”. Check the “Upgrade all clients in the hierachy using production client” check box. then click OK.
- Check you SMSClient folder, those files should be updated themself now, and the “Configuration Manager Client Package” should be automatic updated to distribution points.
Hope this helped you!
If you are still using Configuration Manager 2012, you can run the setup.exe from the installation media folder.
If you are using Current Branch, you should run the setup.exe from “your site backup folder\CD.Latest\SMSSETUP\BIN\X64”
Rest of those are just next next next, you can find other post about it , just use your favor search engine. use key word “SCCM recovery step by step”. I personally recommended Nickolaj Andersen Recover a Site Database in ConfigMgr 2012 R2
Once again, I just wanna marked down the important notes:
- Hope you do find your backup folder, and there are newest backups in it. 🙂
- Go do something else when the recovery starts running, it might take an hour, you will have heart attack by watching it.
- Remember “The Post-recovery actions are now presented to you, and it’s recommended that you take those actions”, just like what Nick said.
Install the missing updates, hotfix.
Input back those service account password in the Admin Console.
Restart your server after recovery is done. 😀
I don’t actually know how should I write this Part 1, I recommended you read first System Center 2012 Configuration Manager R2 – Disaster Recovery for Entire Hierarchy and Standalone Primary Site recovery scenarios
There are almost everything you need, yes I said almost. 🙂
I marked down only few steps what I remembered, not step by step installation
- Install Windows Server
- Install Security updates to your sever
- If you are doing an automatic recovery, you should use same sever name, and exactly same partitions as your old SCCM server.
- Put NO_SMS_ON_DRIVE.SMS file to those partitions to root folder of any drive that you want to prevent Configuration Manager from installing files on
- Install Prerequisites that are related to install SCCM, example Windows roles and Feature. You can use powershell to do that.
Add-WindowsFeature Web-Windows-Auth,Web-ISAPI-Ext,Web-Metabase,Web-WMI,BITS,RDC,NET-Framework-Features,Web-Asp-Net,Web-Asp-Net45,NET-HTTP-Activation,NET-Non-HTTP-Activ,Web-Static-Content,Web-Default-Doc,Web-Dir-Browsing,Web-Http-Errors,Web-Http-Redirect,Web-App-Dev,Web-Net-Ext,Web-Net-Ext45,Web-ISAPI-Filter,Web-Health,Web-Http-Logging,Web-Log-Libraries,Web-Request-Monitor,Web-HTTP-Tracing,Web-Security,Web-Filtering,Web-Performance,Web-Stat-Compression,Web-Mgmt-Console,Web-Scripting-Tools,Web-Mgmt-Compat –Restart -Source :\sources\sxs
- Install SQL, cumulative updates.
If you still have the SQL Configuration file saved in some place, you can just use it. (I will write another post about it later and link it here. )
- Make more tempDB files.
- Install ADK, if you use SCCM to deploy OS
- Install MDT, if you use SCCM to deploy OS
- Install WSUS, if you use the primary server to sync Windows Updates.
Matter of fact, you just need to install everything same as the first time when you setup your SCCM server, so I really hope you have wrotten an documention of that.
Why do I mention 4 and 5 ? I am sure you already knew these basics things, but I have met people whom forgot these basic steps when they did SCCM recovery, perhaps people were in a hurry to recovery their SCCM, time is running out, isn’t it?! Well guess what happened when you didn’t do the basic things, will SCCM works after recovery? Of course NOT!
So, take a deep breath, calm down, clear your mind, go for a run, go Sauna..relax.. Then you start do the SCCM recovery.
Why? Why? Why?
I was in one week holidays, guessed what happened when I came back to work. I found out that our backup disk was full, so SCCM refuse to do site backup, SQL refuse to do SQL full backup. Although I should have SCCM alert if site backup failed, but I do not know why I haven’t received a single email from SCCM monitoring alert. So I decided make SQL backup notification alert.
I believe there are many ways how you setup the SQL Alert, I am not specialist of SQL, so I am just telling how I did it, may not be the best, but it worked. 🙂
- Setup database mail. There is already some other post related to that. Example Pinal Dave wrote an article how to make it in SQL Server 2008, it is same in SQL Server 2012 or 2014. Of course, you should put your own information on those step, like smtp server name. I only use Step 1) Create Profile and Account from the article, and sent test email to myself, confirmed it works.
SQL SERVER – 2008 – Configure Database Mail – Send Email From SQL Database
- How ever, I made small chages in the “manage Profile Security” step. I put the Profile as Public, and I choose “Default Profile”–> Yes.
- Choose “SQL Serve Agent”, right-click “Operators”–>”New Operator…”
Name: Send Email to myself
E-mail name: firstname.lastname@example.org (put the email address of the person who actually reads emails)
Why do we need site backup, and also need SQL Full back..because double backup for safety reason? 🙂 Site backup only backup the site database, that’s why it call “site backup”. If you use custom reports, or if you have any other database on the same server, you should run a SQL full backup, and of course do also the site database SQL full backup.
Again, we use google, search key word “SCCM sql full backup”, you will find probably the first link written by Steve Thompson [MVP] SQL Server Backup Recommendations for Configuration Manager , just remember select all the database you needed, site database, ReportServer database, ReportServer temp database, MDT database.
- Select Report Options Step, I choose “E-mail report”, and choose your Email Operator from the drop-down lista, the one your created from my earlier post in Step 3
If you use reporting server, I would also suggest change the ReportServer Database recovery mode –> “Simple“, before you do the backup maintanece plan.
After I create the Backup Maintanace plan, I add two more step in it.
- Open your Backup Maintanace plan, choose Toolbox from the right panel, add two “Notify Operator Task” in your maintanace plan
- one is for susseced notification, another one is for failed notification
You must remember backup the ReportServer database encryption key if you are using SCCM reports.
- Open Reporting Services Configuration Manager.
- From the left panel, choose “Encryption Keys”
- From the right panel, choose “Backup”
- Then choose where do you want to save the file.
- Put a password there, then save the file.
- Forget the password. (Just joking, hope you remember the password later.)
Well, you alwasy need to backup your SCCM, because…you never know when the sky will fall. Just like me, I never thought our SCCM server never boot up again, it when to a loop just after X-mas, it was not funny at all.
After you setup you SCCM, please go to Site Maintenace, and set up your site backup Schedule. I am not going to write a step by step instruction here, because you can just google it. 🙂
Prajwal Desai already write a blog about it. read it yourself. 🙂
How To Backup SCCM 2012 R2 Server
Has been long time since I wrote my last blog, I thought I will never blog again, well never say never. Took me an hour tried to figured it out what is the name of this blog, something related to SCCM, workstations, Windows 10, powershell, Kids, dog, cat, man? 😀
All other names I tried are reserved, so “The SCCM” that is it. 🙂
Why do I start write blog again? Maybe I tell you later. 😉