Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

NEW Trying to upgrade MECM to version 2111 in offline mode.

  • Thread starter Thread starter Matchew
  • Start date Start date
  • Replies Replies 0
  • Views Views 1K

Matchew

New Member
Messages
1
Reaction score
0
Points
0
The issue started when we tried to upgrade MECM to version 2107 as that was the only update option it would allow us to do while the system is in offline mode. In updates and Servicing we can only see Configuration Manager 2111 Hotfixes currently, are not able to update the Distribution Points to 2111, but main CAS has upgraded to 2111. Also 2111 hotfixes are showing in updates and Servicing set to Available to download but in EasySetupPayload they have downloaded as I can check against GUID and they are same but will not allow me to check pre-requisites or install, probably because only the main CAS is 2111 and the others are 2107.

Its is a multi site configuration and the primary CAS has upgraded to version 5.00.9068.1000 (Which is 2111), but the other sites are still on 5.00.9058.1000 (Which is 2107) I did get 2111 to show up in updates and Servicing but it failed with the following: Failed to apply update changes 0x80004005 Error information persisted in the database. Then after do another offline import, 2111 got stuck on checking pre-requisites so i removed from the database, but now not able to get it to show the update again in ECM console. But I did update main CAS site to 2111, but all other distribution points are still 2107. And cannot find anyway to get the Distribution Points updated to 2111.

Under Site Configuration > Sites if you click on one of the DP, Upgrade is greyed out.

If there is a manual way to execute the update that would be useful as I still have the .cab file for 2111, which GUID ID is 44CE0720-6C46-4554-89CF-C9713E9C06C6

The query I ran against the database to delete the hung update was as follows:

SELECT * FROM dbo.CM_UpdatePackages

This was to view all updates, then once I had found 2111 it then ran the following against the CAS database

DELETE FROM dbo.CM_UpdatePackages WHERE PackageGuid = '44CE0720-6C46-4554-89CF-C9713E9C06C6'

Any pointers would be great.

Thanks
 
Back
Top