KB2905002 Installation and Useful Information

Benoit LecoursSCCM15 Comments

The first hotfix for SCCM 2012 R2 is out and it’s time to install it.

I’ll document a step-by-step installation and gives some useful information.

For those of you that are used to update SCCM, you won’t be disorientated.

The first thing you need to know is that this hotfix will update the sites servers, the consoles and the clients. This mean that you’ll need to update those after the hotfix installation. Rest assured, the hotfix will create 3 updates packages for you during the installation.

Start with the higher site in your hierarchy. You can use the update package that will be created for the other site systems or manually rerun this setup on all site systems.

I see the update process in 3 distinct phases : Installation, review, component update

Step 1 – Installation

Once downloaded, extract the installation package to a local directory, close your console and run “CM12-R2RTM-QFE-KB2905002-X64-ENU”.

The rest of the setup is fairly simple :

r2install-1

r2install-2

r2install-3

r2install-4

Decide if you want the setup to create the update package for you.

r2install-5

Follow the installation :

r2install-8

r2install-9

r2install-10

Step 2 – Review

After the hotfix installation you’ll notice the following changes :

You’ll have 3 new packages in the SCCM console :

hotfix-packages

The console version has not changed.

Console version : 5.0.7958.1000

ConsoleVersion

The client version after update will be 5.0.7958.1101

On the component list of the SCCM client, you’ll notice that only the “Task Sequence Components” are updated to 5.0.7958.1101. (Which is normal since the hotfix target to fix OSD issues)

Client-Components

Step 3 – Component update

Now the “hard” part is to plan your site server, console and client upgrade.

My recommendation is to create a set of collection to target the systems you want to update :

#1- Site Server

Create a direct membership rules and add your SCCM server.

Tip : You can query SQL to list all your “SMS Site Server” :

Select SiteCode, RoleName, ServerName from SysResList where RoleName = ‘SMS Site Server’

#2 – Console

Create a query rule using this WQL Query and deploy the console update to the targeted systems

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 inner join SMS_G_System_ADD_REMOVE_PROGRAMS on SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceId = SMS_R_System.ResourceId where SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName = “System Center 2012 R2 Configuration Manager Console”

#3- Clients

There’s a separate .msp for x86 and for x64 clients so you’ll need to create different collections One for x86 and one for x64 systems

Select * from SMS_R_System inner join SMS_G_System_SYSTEM on SMS_G_System_SYSTEM.ResourceID = SMS_R_System.ResourceId where SMS_G_System_SYSTEM.SystemType = “X64-based PC”

Select * from SMS_R_System inner join SMS_G_System_SYSTEM on SMS_G_System_SYSTEM.ResourceID = SMS_R_System.ResourceId where SMS_G_System_SYSTEM.SystemType = “X86-based PC”

I like to limit my collection to systems that are not updated to the latest version:

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.7958.1101″

The count on this collection will decrease during your deployment process. It’s a good way to keep track of your progress.

Once your actual clients are migrated, you’ll need a strategy to update your future clients. (You have to understand that the previous efforts was for existing clients)… and don’t forget OSD !

There’s a great post on the methods you can use for that. http://blogs.technet.com/b/configmonkey/archive/2013/11/13/deploying-configmgr-hotfixes.aspx

Last step is to update your operating system boot images.

  1. In the Configuration Manager console, click Software Library.
  2. In the Software Library workspace, expand Operating Systems, and then click Boot Images.
  3. Select the boot image that you want to update.
  4. Right-click and then select the Update Distribution Points action.
  5. Repeat steps 3 and 4 for all boot images that have previously been distributed.
  6. All existing media (such as stand-alone, boot, or prestaged) that use existing boot images (default or custom) will have to be re-created.

Happy upgrading !

15 Comments on “KB2905002 Installation and Useful Information”

  1. Hi buddy,

    I’m having a issue with application deployment to distribution points -> machines to diffrent locations, they are really really slow.

    Do you think there is a similar solution between these problems, and that hotfix would fix my problem?

    I’m a new adm of SCCM and i’m in deeply trouble with this slowness, i’ve been seeking for help and a solution about this case for around a month, and by far, that solution seems the right one till now.

    1. And right now i’m trying to create the: “direct membership rules and add your SCCM server.” But for some reason, it isn’t recognizing the query: Select SiteCode, RoleName, ServerName from SysResList where RoleName = ‘SMS Site Server’

      :/ damn im going insane with this thing

        1. Do you have an IM that we’re able to contact each other? I’m truly lost here. I would appreciate your help if you’re with time. Skype, Facebook, anything .

          1. Ok,

            Many thanks.

            You have no idea how desperate i’m.

            I’m really new to system center, and my company enviroment is currently a mess 🙁

          2. You have asked which version is my enviroment, currently at 2012 R2, soon i’ll upgrade it to SP1 with your guilde, but yet i’ll try fix the slowness problem with the hotfixes and your help.

          3. Hi Benoit,

            How’s going?

            I upgraded my environment to R2 SP1, however, the slowness remains.

            I still waiting for your e-mail.

            Regards.

      1. Passa nu på att önska låter till det stora önskevinter specialen vi kommer hålla den 20 Dec! Inte bara kan ni få just er låt spelad i programmet utan även den bästa, sämsta, roligaste, tuffaste, konstigaste, snyggaste, coolaste eller kanske hårigaste låten kommer även vinna en super snygg Speklassiker Musik feat. GamingGrannar t-shirt!

  2. Thanks very much for this info, has helped me trying to resolve our slow image download in WinPE issue. However, when I try to copy any of your WQL queries into the query designer for each collection I get syntax errors for all of them, is there something I might be doing wrong? I’ve tried to copy them to a text editor first and then to the query designer in SCCM

    1. Hi Jez,

      The first query is a SQL query, it won’t work in a collection query which is WQL.

      I found the error with the other query. The quote sign must be (“) instead of (‘). I’ve made the modification on the post.

      Thanks for pointing that out.

      1. Thanks for the quick response, everything working great now, I still had syntax issues copying and pasting from your blog but once I deleted and re-typed the ” marks there were no more syntax errors, Cheers

Leave a Reply

Your email address will not be published. Required fields are marked *