After the upgrade of 2002 , Client version on the boot image is not getting changed.

Question

Hi Experts ,

Yesterday we have upgraded SCCM environment to 2002 version.

Before upgrading the SCCM environment, we had updated ADK to latest version and distributed the image , post completion of distribution of both image  only we have started the SCCM upgrade.

Post upgrade , recent client version 5.00.8968.1042 is promoted to production. And then I have again distributed a new boot image to DP by using an option Reload this boot image with the current Windows PE version from the Windows ADK but still when I am seeing the client version of boot image , it is showing as old.

Update Distribution point - HTMD Forum - Welcome to the world of Device Management! This is community build by Device Management Admins for Device Management Admins❤️ Ask your questions!! We are here to help you! - After the upgrade of 2002 , Client version on the boot image is not getting changed. Version still shows old - HTMD Forum - Welcome to the world of Device Management! This is community build by Device Management Admins for Device Management Admins❤️ Ask your questions!! We are here to help you! - After the upgrade of 2002 , Client version on the boot image is not getting changed.

Note : I followed this article correctly : https://www.anoopcnair.com/update-windows-adk-step-by-step-guide-for-sccm/

 

 

solved 0
Ketan Kamble 2020-08-16T08:53:32+05:30 10 Answers 1328 views Beginner
0

Answers ( 10 )

  2. Donna Jennings
    0
    2020-08-24T07:30:14+05:30
    Reply

    Hi Ketan, we had the same issue with both default and custom boot images. We had to remove the affected boot images from all Distribution Points, then go through the process to update them with the latest client version again, and then distribute to all DPs.

  4. Ketan Kamble
    0
    2020-08-16T16:27:35+05:30
    Reply

    I don’t think so it will create any issue , but this is MS bug I think so . Can you please also check with your references .

    Best answer
  6. Anoop C Nair
    0
    2020-08-16T13:25:00+05:30
    Reply

    I have no clue … i think the screen shot that I shared above is from ConfigMgr 2006 version … but the client version is of 2002 … I have no clue why …

    But I’m trying to understand what is the significance of the client version in the boot image … there is no impact isn’t it ?

  8. Ketan Kamble
    0
    2020-08-16T11:23:53+05:30
    Reply

    Tested just now for for custom boot image also, the same issue .

    I noticed one thing when I am clicking on update distribution points it is changing client version for some time ,but again after 15- 20 min it is showing previous client version.(5.00.8913.1032)

    No details are there in DISM logs for client version change.

  10. Anoop C Nair
    0
    2020-08-16T10:05:42+05:30
    Reply

    Ok… let us know

  12. Ketan Kamble
    0
    2020-08-16T09:50:53+05:30
    Reply

    I observed this issue , that why I have not yet distributed the custom boot image .

    Let me check if I find anything in dism.log.

  14. Anoop C Nair
    0
    2020-08-16T09:34:56+05:30
    Reply

    better to check the logs related to distmgr to get some more client …

    dism.log also get some clue time….

  16. Ketan Kamble
    0
    2020-08-16T09:26:49+05:30
    Reply

    Yes , While distributing the content its detecting the new client version but post distributing the content , it is again detecting the Old Client version.

    I tried 2 -3 times the distribution

  18. Anoop C Nair
    0
    2020-08-16T09:21:10+05:30
    Reply

    I have different client versions associated with boot image … https://snipboard.io/0q8jVC.jpg

    However, the client version getting installed part TS via using client package –

    I don’t know why it shows different versions…

Leave an answer

Sorry, you do not have permission to answer to this question .