none
Office 365 Monthly Client update are not changing the value in registry for "VersionToReport" to current office 365 deployed version RRS feed

  • Frage

  • Hi,

    Have deployed office 365 Monthly client update to SCCM client systems and it is not changing the value in registry for "VersionToReport" to version 16.0.11901.20176

    Due to this it is showing not complaint and if I am changing the value manually from version 16.0.11029.20108 to current version 16.0.11901.20176 of office 365 in following registry path it roll backs to the previous version again.

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration

    Any help would be appreciated.

    Regards,

    Manzoor

    Dienstag, 13. August 2019 11:21

Alle Antworten

  • This is really an O365 question, as scuh you will get better answer within o365 forum. 

    Garth Jones

    Blog: https://www.enhansoft.com/blog Old Blog: https://sccmug.ca/

    Twitter: @GarthMJ Book: System Center Configuration Manager Reporting Unleashed

    • Als Antwort vorgeschlagen Jason SandysMVP Dienstag, 13. August 2019 13:34
    Dienstag, 13. August 2019 12:28
    Moderator
  • Where you previously using just the ODT? Wondering if settings applied there linger and configmgr does not yet have full control so to speak (Previous ODT deployment overwriting your manual reg change):

    https://docs.microsoft.com/en-us/deployoffice/manage-updates-to-office-365-proplus-with-system-center-configuration-manager

    Dienstag, 13. August 2019 21:20
  • Hi,

    Had raised the support ticket with Microsoft team and shared the details and SCCM client systems logs.

    Got the below response from Microsoft support.

    Temporary fix suggested by Microsoft:

    So until it got fixed we have to go for a compliance rule to check the presence of update using the other registry key (ClientVersionToReport)

    Hello Manzoor, 

    I have a call with a Office 365 and also looked at the logs, and found that there is bad design with will be change in the near future.

    The problem is regarding the detection logic on office deployment. because different products share the same registry key, it will generate that error. 

    This is actually schedule for the next year, so I don't have a expected timeline, of when this will be corrected. 

    Until then I will actual go for a compliance rule to check the presence of update using the other registry key (ClientVersionToReport)

    Thank You,

    Donnerstag, 22. August 2019 14:05