Monday, 25 November 2013

Config Mgr (SCCM) 2012 R2 Hotfix installation

Back to ConfigMgr main menu

 The release of ConfigMgr 2012 R2 caused some issues with Operating System Deployment when a PXE enabled Distribution Point was co-located with Site Servers.

 1. WDS crashing
2. Very slow download speeds for OSD files

 The official descriptions are as follows:

Issue 1
After you enable the PXE Service Point role on an instance of a specific distribution point, or you select the Deploy this boot image from the PXE-enabled distribution point property of a boot image, the Windows Deployment Service (WDS) stops running.
Note: This problem affects only distribution points that are installed on site servers.
Issue 2
When operating system image files are downloaded to Configuration Manager 2012 R2 clients, you may find that the download takes longer than it did in previous versions of Configuration Manager 2012 clients. You may see this behavior when the target client is running Windows PE or a full Windows operating system.

 These issues were resolved with Hotfix KB2905002. The Hotfix can be downloaded here

 http://support.microsoft.com/kb/2905002/en-us?sd=rss&spid=1060

 You can also find installation information on this page.

 Download and extract the Hotfix files.

Launch the executable.

See the "Welcome Screen". It gives information on how KB2905002 should be applied. Click Next.


Accept the License Terms and click Next.


The prerequisite check begins. See the Warning.


 A pending restart has been detected. Close and restart the server.

After the restart the prerequisite check passes.


Choose to install the update for the console.


Choose all the options.


Enter your preferred names and source for the Server package.


Enter your preferred names and source for the Console package.


Enter your preferred names and source for the client package.


Review the summary and click to install.


Update installation has completed successfully. Review the log file and click Next.


Click Finish to close the wizard.

 Now deploy the server, console and client packages. Create x86 and x64 collections to deploy the correct client package.

Don't forget you HAVE to update all boot images on your Distribution Points.
Posted by at
Labels: , , , ,

18 comments:

  1. Anonymous10 December 2013 at 04:17

    I had an issue applying this update during the "stop services" action. I was guessing that it was just a timeout issue so, I ran the patch again immediately and it patched without issue.

    ReplyDelete
  2. Anonymous4 April 2014 at 20:18

    I had the same issue with "Stop services". The problem was the service tmlisten of Trend Micro antivirus. Once the antivirus is disabled everything installed fine.

    ReplyDelete
  3. Anonymous21 April 2014 at 00:42

    2012R2 CU1 includes this hotfix as well as the SCEP update from November.
    http://support.microsoft.com/kb/2938441

    ReplyDelete
  4. Eilz23 May 2014 at 14:04

    It was stuck for a long time on 'stop services' so I opened cmd and ran "net stop winmgmt" and the hotfix then ran fine afterwards.

    ReplyDelete
    Replies
    1. Gerry Hampson23 May 2014 at 14:10

      Yes, I've had to do that a couple of times also. It doesn't always happen.

      Delete
  5. Unknown23 May 2014 at 16:28

    I am new to SCCM, I am stuck on the last couple of steps. How do you deploy the server, console and client packages? And create x86 and x64 collections to deploy the correct client package? Also how do you update all boot images on your Distribution Points. Thanks.


    ReplyDelete
    Replies
    1. Gerry Hampson26 May 2014 at 10:22

      1. You deploy these packages in the same way that you would deploy any other. Right click > Choose Deploy > Complete the wizard (choosing the collection you require).
      2. You should deploy the x86 package to x86 clients and the x64 package to x64 clients. You do this by creating collections containing x86 and x64 clients using the following queries.

      select distinct 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_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceID = SMS_R_System.ResourceId where SMS_G_System_COMPUTER_SYSTEM.SystemType = "x86-based PC"

      select distinct 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_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceID = SMS_R_System.ResourceId where SMS_G_System_COMPUTER_SYSTEM.SystemType = "x64-based PC"

      3. Right click on your boot images and choose "Update Distribution Points".

      Delete
    2. Gerry Hampson26 May 2014 at 10:25

      Be careful with the formatting above - the query doesn't copy very well to Blogger.

      Delete
  6. Unknown8 June 2014 at 15:15

    Hi Gerry,
    I have just a query,. Why do we need to deploy the server, console and client packages.
    Client packages I think is used when performing Client Push installation right?
    But why server and console packages??

    Thanks in advance
    Jose

    ReplyDelete
    Replies
    1. Gerry Hampson9 June 2014 at 15:40

      You should deploy the server package to any other ConfigMgr Site Systems that you have (if you have only one then you don't need this).
      You should deploy the console package to any computer than runs the console (this can be installed separately). If you are only using the console that is installed on the Primary site server then you don't need this.

      Delete
  7. Unknown8 June 2014 at 15:52

    Hi Gerry,
    I have ran into a problem. Installed the Hotfix but still when I enabled PXE, the WDS services are stuck on status starting and it does seem to change. When I tried starting from WDS console, it gives a error message that a instance is already running..
    How should i continue now. won't it create a problem in OSD in next configuration.
    Please guide me at earliest.
    Thanks in advance
    Jose

    ReplyDelete
    Replies
    1. Gerry Hampson9 June 2014 at 15:41

      Yes it will. You need to ensure that the WDS service is started. Don't launch WDS console. You should never have to use it.

      Delete
  8. Sandeep25 January 2015 at 18:17

    Hi Gerry, If its a fresh SCCM 2012 R2 setup do I need to implement last couple of steps i.e. install console and client packages? Mine is fresh setup, so have not rolled out any clients or Console packages yet. Does the Hotfix, integrate the changes into the Client Package that gets installed by default into SCCM.

    ReplyDelete
    Replies
    1. Gerry Hampson26 January 2015 at 13:26

      At this stage you should be installing the latest Cumulative Update (which will include previous hotfixes). Yes, you will still need to deploy the CU package to your consoles and clients.

      Delete
  9. Sandeep27 January 2015 at 10:27

    Hi Gerry - Thanks a lot of Quickly replying to this and 2 other queries I had posted on different posts of your blog..

    ReplyDelete
  10. Unknown29 April 2015 at 14:14

    Hi Gerry,

    Since applying the updates, I have lost access to my SMS provider, this has been resolved by adding second one. The new issue is the Log files in config manager install location do not look like they are logging anything after the CU's. Any advise??

    Regrads
    Richard Booth

    ReplyDelete
    Replies
    1. Gerry Hampson30 April 2015 at 12:59

      Note that you have to update the SMS Provider and ALL consoles also Richard.

      Delete

Subscribe to: Post Comments (Atom)