locked
CM 2012 SP2 CU4 client upgrade fails with error 1642 RRS feed

  • Question

  • Hi all

    We just upgraded our CM 2012 SP1 CU2 primary site to 2012 SP2, and then installed CU4 (unfortunately we currently are not able to go to 2012 R2 or higher).

    I tested deployment of the CU4 x64 upgrade package, and it failed with error 1642, which I now know means "The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program. Verify that the program to be upgraded exists on your computer an d that you have the correct upgrade patch."

    Did I miss a trick here?  Do I need to get the clients to SP2 first?  Is SP1 to SP2 an upgrade (as opposed to an update)?

    Thanks in advance for any advice.

    Saturday, December 10, 2016 12:54 PM

Answers

  • The CU4 you installed is SP2 specific, you cannot install it on clients still running 2012 SP1. So yes, the CM clients need to be a SP2 before being able to apply this patch. You can upgrade your clients directly to SP2 CU4 by integrating the CU4 patch with the 2012 SP2 client package.

    • Marked as answer by ep1971 Saturday, December 10, 2016 10:11 PM
    Saturday, December 10, 2016 2:41 PM
  • You do still need to specify PATCH during task sequences. For normal client push, it's taken care of for you post 2012 SP2 CU1 and 2012 R2 SP1 CU1. See https://blogs.technet.microsoft.com/enterprisemobility/2015/08/04/automatically-updating-the-configuration-manager-client/

    Jason | http://blog.configmgrftw.com | @jasonsandys

    • Marked as answer by ep1971 Saturday, December 10, 2016 10:11 PM
    Saturday, December 10, 2016 10:09 PM

All replies

  • The CU4 you installed is SP2 specific, you cannot install it on clients still running 2012 SP1. So yes, the CM clients need to be a SP2 before being able to apply this patch. You can upgrade your clients directly to SP2 CU4 by integrating the CU4 patch with the 2012 SP2 client package.

    • Marked as answer by ep1971 Saturday, December 10, 2016 10:11 PM
    Saturday, December 10, 2016 2:41 PM
  • Hi Emmanuel

    Thanks for the reply.

    So to integrate the CU4 patch I guess I just need to:

    • Enable automatic client upgrade in Hierarchy Settings (currently disabled)
    • Add a 'hotfix\KB3195483' folder to 'SMS_sitename\Client\x64 & i386'?  Like I do in order to use the PATCH parameter during OSD?

    If so, how does the SP2 upgrade know to apply the patch, since I cannot specify a PATCH parameter for client upgrade?


     

    Saturday, December 10, 2016 2:52 PM
  • I remember not needing to specify PATCH to get the hotfix to install as part of setup, just adding it to xxx\hotfix\ is sufficient. As for deploying it, it's your choice really, automatic client upgrade, a deployed client package, scripted, etc... Any method works.
    Saturday, December 10, 2016 3:14 PM
  • You do still need to specify PATCH during task sequences. For normal client push, it's taken care of for you post 2012 SP2 CU1 and 2012 R2 SP1 CU1. See https://blogs.technet.microsoft.com/enterprisemobility/2015/08/04/automatically-updating-the-configuration-manager-client/

    Jason | http://blog.configmgrftw.com | @jasonsandys

    • Marked as answer by ep1971 Saturday, December 10, 2016 10:11 PM
    Saturday, December 10, 2016 10:09 PM
  • Great stuff.  Thanks Emmanuel and thanks Jason.
    Saturday, December 10, 2016 10:11 PM