locked
Version differences RRS feed

Answers

  • The version is 5.00.7958.

    1000 and 1604 are just tho hotfixes. This value will only change if there is a hotfix for the particular binary.

    • Proposed as answer by Frank Dong Monday, August 29, 2016 10:25 AM
    • Marked as answer by Frank Dong Wednesday, September 7, 2016 1:16 PM
    Friday, August 26, 2016 8:03 PM

All replies

  • The version is 5.00.7958.

    1000 and 1604 are just tho hotfixes. This value will only change if there is a hotfix for the particular binary.

    • Proposed as answer by Frank Dong Monday, August 29, 2016 10:25 AM
    • Marked as answer by Frank Dong Wednesday, September 7, 2016 1:16 PM
    Friday, August 26, 2016 8:03 PM
  • Before 2012 R2 SP1 CU1, there was no way to auto-deploy hotfixes to the client agent. Thus, you command-line above simply installs the 2012 R2 client agent and unless you are manually deploying the 2012 R2 CU5 hotfix, there's no way for them to get it.

    You really should just upgrade to 2012 R2 SP1 and then apply 2012 R2 SP1 CU3. Alternatively, you should upgrade to ConfigMgr Current Branch.


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

    • Proposed as answer by Frank Dong Monday, August 29, 2016 10:26 AM
    • Marked as answer by Frank Dong Wednesday, September 7, 2016 1:16 PM
    • Unmarked as answer by Wasisname Wednesday, September 7, 2016 1:22 PM
    • Unproposed as answer by Wasisname Wednesday, September 7, 2016 1:22 PM
    Saturday, August 27, 2016 4:10 PM
  • Can you tell me what the hotfixe are? Is/are there KB####'s for them, & what would they be?

    # When I wrote this script only God and I knew what I was doing. # Now, only God Knows!

    Wednesday, September 7, 2016 1:21 PM
  • I'm sorry, but upgrading again at this point is not an option for me.  Either way I should still be able to upgrade the client to the proper version in some fashion.

    # When I wrote this script only God and I knew what I was doing. # Now, only God Knows!

    Wednesday, September 7, 2016 1:23 PM
  • So you want to be on a *years* old version that has many, many issues fixed in newer versions that also have many new features and functions and doesn't even support Windows 10?

    Yes, you can upgrade the client to the matching site version. During the CU installation, you should have been prompted whether you wanted the installer to create the update packages for you. You can use these or SCUP. This is detailed at https://technet.microsoft.com/en-us/library/jj553405.aspx#BKMK_DeployUpdates. Alternatively, the updates are just patches (in the form of MSPs) and thus you can add them to the ccmsetup command-line using the PATCH property.


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

    Wednesday, September 7, 2016 1:29 PM
  • Jason Sandys wrote:

    "So you want to be on a *years* old version that has many, many issues fixed in newer versions that also have many new features and functions and doesn't even support Windows 10?"

    This comment makes me feel like I've been flamed.  Just remove my post/question & the attendant thread.

    • Edited by Wasisname Wednesday, September 7, 2016 1:53 PM
    Wednesday, September 7, 2016 1:51 PM