Techie-v2 Posted October 11, 2022 Posted October 11, 2022 Hi All, I am trying to update office using SCEM/SCCM but am running into an issue with versions. Using the Office 365 client management feature, I created a update group and deployment group for version 2209 and deployed this to my test machine. All went well and office was update, hurrah So next I deployed it to a suite of computers, all failed. Couldn't for the life of me work out why, then i realised that during the summer I rebuild our SCCM server, so in turn a new version of office was created on the server. The suite of computer I tried to deploy it to was rebuilt using teh new SCCM server, where as my test machine was built using my old SCCM server, with an older version of office on it. So in short, deploying office 2209 to machines with 1907 on them updates fine. But deploying it to machines with 2206 on them fails. Some of the error codes are CAS failed to download update (246b14a2-1b2c-4259-bd80-c45a0e5e85fc). Error = 0x80200061. Releasing content request. and CAS failed to download update (246b14a2-1b2c-4259-bd80-c45a0e5e85fc). Error = 0x800705b4. Releasing content request. All sorts of internet answers lead to they usual boundary groups and and timeouts etc but this has to be something more specific with office and updating the older version works fine, all other updates and deployments work fine. Anyone have any ideas or seen this themselves? Thanks
denmyos Posted April 19, 2023 Posted April 19, 2023 Hi Did you ever find a slolution to this problem? All my office 2021 update are failing with 0x80200061 error. Have been seaching google, and nobody seems to have find the holy grail to this problem.
Techie-v2 Posted June 8, 2023 Author Posted June 8, 2023 Hi, Yeah sorry I did. Turns out I had previously had two different languages deployed so I needed to add both en-gb and en-us to my upgrade package, then whatever version the computer had, it could upgrade. Hope this helps
adminner Posted July 14, 2023 Posted July 14, 2023 I've seen this solution for a few out there, but we're experiencing the same symptoms and we have en-us deployed ONLY.
kevin_lane Posted July 14, 2023 Posted July 14, 2023 Strange I’ve been testing this I don’t know if I’m doing anything wrong but I did notice that some of my clients have gone from managed to unmanaged - the install works fine , however where before when the pupils logged they seem to be getting a prompt where as before it would just sign them in, once they do sign in everything is fine - not sure - I’m deploying office 365, app and did the xml etc not sure if anyone else has come across this
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now