Office 365 Pro Plus - update via SCCM

%3CLINGO-SUB%20id%3D%22lingo-sub-1610653%22%20slang%3D%22en-US%22%3EOffice%20365%20Pro%20Plus%20-%20update%20via%20SCCM%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1610653%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20Guys%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFew%20months%20before%20we%20deployed%20Office%20365%20Pro%20Plus%201902%20Semi-annual%20Channel%20via%20System%20Center%20Configuration%20Manager%201910%20(SCCM)%20as%20Application%20Deployment%20(not%20update)%20over%20300%20Clients.%20The%20client's%20old%20version%20was%20Semi-Annual%20Channel%20Version%201808.%20Application%20deployment%20was%20successful%20and%20all%20clients%20were%20upgraded%20to%201902.%20But%20after%20this%2C%20we%20are%20trying%20to%20deploy%20Semi-annual%20next%20%22updates%22%20from%20SCCM%20Office%20365%20Client%20Management.%20But%20SCCM%20detected%20only%20about%2050%20Clients%20as%20%22required%22%20so%20could%20update%20only%20these%2050%20Clients.%20Other%20look%20like%20do%20not%20need%20to%20update.%3CBR%20%2F%3EWe%20opened%20%23SCCM%20(1910)%20Case%20in%20Microsoft%20for%20this%20problem%2C%20but%20they%20think%20a%20problem%20is%20related%20to%20%23office365%20problem%2C%20not%20SCCM.%3CBR%20%2F%3EAfter%20investing%20a%20lot%20of%20time%20I%20found%20that%20in%20these%2050%20Clients%20where%20update%20working%20successfully%20%22ClientVersionToReport%22%20and%20%22VersionToReport%22%20Values%20are%20the%20same%20in%20Registry%20Entry.%20I%20mean%20both%20value%20numbers%20were%20the%20same%20as%20Office%20365%20semi-annual%201902%20Deployment%20version.%20But%20these%202%20Values%20are%20different%20in%20all%20other%20clients.%20In%20some%20of%20them%20%22VersionToReport%22%20is%20missing%20or%20older%2C%20newer%20than%20%22ClientVersionToReport%22%2C%20on%20the%20other%20hand%2C%20%22ClientVersionToReport%22%20missed%20from%20some%20clients%2C%20or%20%22ClientVersionToReport%22%20value%20is%20still%201808%20version%20instead%20of%20clients%20are%20already%20upgrade%20to%201902.%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22rashadbakirov_0-1598365788314.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F214635iF84DA82A10975942%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20title%3D%22rashadbakirov_0-1598365788314.png%22%20alt%3D%22rashadbakirov_0-1598365788314.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EAs%20I%20understood%2C%20maybe%20i%20m%20wrong%20SCCM%20Office%20365%20Client%20Management%20detection%20method%20checking%20these%202%20Values%20in%20Clients%20to%20add%20them%20as%20%22required%22%20or%20as%20%22not%20Required%22%20list.%3CBR%20%2F%3E%3CBR%20%2F%3EMy%20question%20is%2C%20could%20some%20explain%20why%20Office%20365%20installation%20behavior%20was%20different%20per%20Client%3F%20We%20deployed%20Application%20in%20one%20Deployment%20pack%20to%20all%20clients%20and%20clients%20got%20the%20same%20configure.xml%20and%20installation%20was%20successful%20for%20all%20clients.%20Only%20version%20differences%20I%20see%20in%20these%202%20Values%20in%20Registry%20Entry.%3CBR%20%2F%3EHow%20we%20can%20solve%20this%20problem%3F%20Additional%20I%20want%20to%20say%20if%20we%20want%20to%20update%20Office%20365%20manual%20from%20for%20example%20Outlook%20App%20it%20will%20work%20and%20got%20the%20latest%20semi-annual%20version%3CBR%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%221808.JPG%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F214634i5A18FDC96CC3203F%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%221808.JPG%22%20alt%3D%221808.JPG%22%20%2F%3E%3C%2FSPAN%3E%3CBR%20%2F%3EIn%20the%20photo%2C%20you%20can%20see%20that%20after%20Office%20365%201808%20Version%2C%20SCCM%20could%20not%20get%20correct%20info%20about%20Clients.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBest%20Regards%3C%2FP%3E%3CP%3ERashad%20Bakirov%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1610653%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ECompliance%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%20Groups%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20Apps%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOn-Premises%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EProPlus%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1613089%22%20slang%3D%22en-US%22%3ERe%3A%20Office%20365%20Pro%20Plus%20-%20update%20via%20SCCM%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1613089%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F768844%22%20target%3D%22_blank%22%3E%40rashadbakirov%3C%2FA%3E%26nbsp%3BHi%2C%20this%20is%20not%20that%20easy%20to%20understand%20to%20be%20honest.%20From%20my%20experience%20working%20with%20update%20channels%20(not%20SCCM)%20and%20the%20registry%20is%20that%20it%20can%20be%20quite%20a%20mess%20without%20any%20logic%20sometimes%2C%20so%20I%20wouldn't%20stare%20blindly%20at%20the%20registry%20keys.%20But%20perhaps%20another%20member%20know%20more%20about%20it.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20have%20run%20into%20issues%20similar%20to%20what%20you're%20describing%20where%20all%20settings%20looked%20ok%20(update%20channels%2C%20SCCM%2C%20update%20available%20software)%20but%20some%20of%20the%20clients%20on%20that%20particular%20channel%20just%20wouldn't%20update%20to%20a%20newer%20build.%20It%20turned%20out%20to%20be%20a%20problem%20at%20Microsoft%20in%20the%20backend%20causing%20it%20so%20we%20had%20to%20force%20the%20update%20on%20the%20clients.%20Perhaps%20you%20can%20use%20that%20for%20your%20scenario%20as%20well.%3C%2FP%3E%3CDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%20class%3D%22copy-paste-block%22%3E%3CDIV%3E%3CEM%3EStart-Process%20%22C%3A%5CProgram%20Files%5CCommon%20Files%5Cmicrosoft%20shared%5CClickToRun%5COfficeC2RClient.exe%22%20-ArgumentList%20%22%2Fupdate%20user%22%3C%2FEM%3E%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3EHope%20it%20helps%20in%20some%20way.%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1615617%22%20slang%3D%22en-US%22%3ERe%3A%20Office%20365%20Pro%20Plus%20-%20update%20via%20SCCM%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1615617%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F551905%22%20target%3D%22_blank%22%3E%40bec064%3C%2FA%3EHi%20Christian%2C%20thank%20you%20very%20much%20for%20your%20reply.%20We%20are%20interested%20in%20solving%20the%20problem%20with%20SCCM%20because%20we%20are%20updating%20our%20Clients%20via%20Configuration%20Manager.%20We%20want%20to%20find%20why%20SCCM%20thinks%20only%2050%20Clients%20out%20of%20300%20need%20required%20new%20updates%2C%20though%20they%20are%20all%20on%20the%20same%20level.%3CBR%20%2F%3EOne%20more%20example%2C%20the%20latest%20Microsoft%20365%20Apps%26nbsp%3BSemi-annual%20Version%202002%20Build%20is%2012527.20988%2C%20and%20a%20lot%20of%20our%20clients%20are%20older%20than%20this%20version%20(Build%2012527.20880%20or%20older).%20But%20somehow%2C%20Configuration%20Manager%20detects%20only%20a%20few%20of%20them%20required%20build%20number%2012527.20988.%3CBR%20%2F%3EWe%20know%20we%20can%20update%20all%20clients%20manually%20to%20version%2012527.20988.%20But%20our%20goal%20is%20to%20find%20a%20problem%20because%20we%20will%20continue%20to%20update%20our%20environment%20always%20via%20SCCM.%26nbsp%3B%3C%2FP%3E%3CP%3Ewe%20thought%20that%20problem%20on%20SCCM%20so%20we%20opened%20Microsoft%20Case%20for%20SCCM%2C%20but%20they%20believe%20it%20related%20to%20Office.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1615695%22%20slang%3D%22en-US%22%3ERe%3A%20Office%20365%20Pro%20Plus%20-%20update%20via%20SCCM%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1615695%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F768844%22%20target%3D%22_blank%22%3E%40rashadbakirov%3C%2FA%3E%26nbsp%3BHello%20again%2C%20I%20understand%20and%20it%20seems%20as%20if%20we%20use%20the%20same%20approach.%20I%20know%20a%20lot%20about%20update%20channels%20but%20unfortunately%20I%20don't%20manage%20Configuration%20Manager%20so%20cannot%20assist%20in%20the%20way%20I%20would%20like.%20I%20think%20you%20should%20continue%20with%20the%20Microsoft%20ticket%20for%20proper%20assistance.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Hello Guys,

 

Few months before we deployed Office 365 Pro Plus 1902 Semi-annual Channel via System Center Configuration Manager 1910 (SCCM) as Application Deployment (not update) over 300 Clients. The client's old version was Semi-Annual Channel Version 1808. Application deployment was successful and all clients were upgraded to 1902. But after this, we are trying to deploy Semi-annual next "updates" from SCCM Office 365 Client Management. But SCCM detected only about 50 Clients as "required" so could update only these 50 Clients. Other look like do not need to update.
We opened #SCCM (1910) Case in Microsoft for this problem, but they think a problem is related to #office365 problem, not SCCM.
After investing a lot of time I found that in these 50 Clients where update working successfully "ClientVersionToReport" and "VersionToReport" Values are the same in Registry Entry. I mean both value numbers were the same as Office 365 semi-annual 1902 Deployment version. But these 2 Values are different in all other clients. In some of them "VersionToReport" is missing or older, newer than "ClientVersionToReport", on the other hand, "ClientVersionToReport" missed from some clients, or "ClientVersionToReport" value is still 1808 version instead of clients are already upgrade to 1902.

rashadbakirov_0-1598365788314.png

 


As I understood, maybe i m wrong SCCM Office 365 Client Management detection method checking these 2 Values in Clients to add them as "required" or as "not Required" list.

My question is, could some explain why Office 365 installation behavior was different per Client? We deployed Application in one Deployment pack to all clients and clients got the same configure.xml and installation was successful for all clients. Only version differences I see in these 2 Values in Registry Entry.
How we can solve this problem? Additional I want to say if we want to update Office 365 manual from for example Outlook App it will work and got the latest semi-annual version
1808.JPG
In the photo, you can see that after Office 365 1808 Version, SCCM could not get correct info about Clients.

 

Best Regards

Rashad Bakirov

3 Replies
Highlighted

@rashadbakirov Hi, this is not that easy to understand to be honest. From my experience working with update channels (not SCCM) and the registry is that it can be quite a mess without any logic sometimes, so I wouldn't stare blindly at the registry keys. But perhaps another member know more about it.

 

I've have run into issues similar to what you're describing where all settings looked ok (update channels, SCCM, update available software) but some of the clients on that particular channel just wouldn't update to a newer build. It turned out to be a problem at Microsoft in the backend causing it so we had to force the update on the clients. Perhaps you can use that for your scenario as well.

 
Start-Process "C:\Program Files\Common Files\microsoft shared\ClickToRun\OfficeC2RClient.exe" -ArgumentList "/update user"
 
Hope it helps in some way.
Highlighted

@bec064Hi Christian, thank you very much for your reply. We are interested in solving the problem with SCCM because we are updating our Clients via Configuration Manager. We want to find why SCCM thinks only 50 Clients out of 300 need required new updates, though they are all on the same level.
One more example, the latest Microsoft 365 Apps Semi-annual Version 2002 Build is 12527.20988, and a lot of our clients are older than this version (Build 12527.20880 or older). But somehow, Configuration Manager detects only a few of them required build number 12527.20988.
We know we can update all clients manually to version 12527.20988. But our goal is to find a problem because we will continue to update our environment always via SCCM. 

we thought that problem on SCCM so we opened Microsoft Case for SCCM, but they believe it related to Office.

 

 

Highlighted

@rashadbakirov Hello again, I understand and it seems as if we use the same approach. I know a lot about update channels but unfortunately I don't manage Configuration Manager so cannot assist in the way I would like. I think you should continue with the Microsoft ticket for proper assistance.