SOLVED Server 2016.wim "Schedule Updates" greyed out

[Big_Mark]

SCCM 1902 Site Version: 5.0.8790.1000

As of a month ago I noticed that I could no longer schedule updates for my customized 2016 Server (1607) image via SCCM console.
Software Library > Operating Systems > Operating System Images > 2016 Server
Previously I had no problems scheduling and running updates on this image.
I have no issues updating my 2019 Server, Win10 1809 and 1903 images.

For troubleshooting I downloaded the latest 2016 .iso from Microsoft (SW_DVD9_WIN_SERVER_STD_CORE_2016_64BIT_ENGLISH_-4_DC_STD_MLF_X21-70526.ISO) then imported the install.wim image (Standard Server with GUI) with the same results.

As a work around I created a customized and updated .wim for 2016 server, then set my task sequence to apply updates during deployment, so I have what I need moving forward however I have not been able to find anyone else with this issue and wonder if this is normal or abnormal.
My preference is to have this work, or at least know that this SHOULD NOT WORK ( I hate it when things don;t work :-( )

P.S. first post, long time blog fan/user, thanks for the great resource P-man!

 

[Big_Mark]

I noticed there was another user with a similar issue however no solution was posted.

 

[Big_Mark]

Is anybody else having this issue or is it just Me?

 

[RMorty]

I am also having this issue. I am running 1902 as well, Server 2016 WIM.

 

[Sergey Korotkov]

This is a bug in CM 1902
has been fixed in CM 1906.... or u can fix 2016 version build in "SupportedProductsForOfflineServicing" table.

 

[Big_Mark]

Thanks for the info Sergey, I wasn't able to find any Microsoft documentation (or anywhere else) regarding this issue, will you post a link please?

 

[Sergey Korotkov]

This is a common mistake tp/release. As an example:

Schedule Updates Windows 10 Build 10586 - No Updates Shown

social.technet.microsoft.com

etc

 

[pede]

i checked it on 2 systems, one which has KB4500571 not installed works great the other one doesn´t.

both look the same
select * from SupportedProductsForOfflineServicing
Id ProductType OsVersionBuild Name
1 WinNT 6.0.6001 Windows Vista
2 WinNT 6.0.6002 Windows Vista
3 ServerNT 6.0.6001 Windows Server 2008
4 ServerNT 6.0.6002 Windows Server 2008
5 WinNT 6.1.7600 Windows 7
6 WinNT 6.1.7601 Windows 7
7 ServerNT 6.1.7600 Windows Server 2008 R2
8 ServerNT 6.1.7601 Windows Server 2008 R2
9 WinNT 6.2.9200 Windows 8
10 ServerNT 6.2.9200 Windows Server 2012
11 WinNT 6.3.0000 Windows 8.1
12 ServerNT 6.3.0000 Windows Server 2012 R2
13 WinNT 10.0.10240 Windows 10
14 ServerNT 10.0.10240 Windows Server 2016
15 ServerNT 10.0.17763 Windows Server 2019

 

[pede]

ConfigMgr team is aware of this. We have fixed this regression in 1906 caused by 1902 hotfix. Database table SuportedProductsForOfflineServicing has an incorrect value of build version for Windows Server 2016. If anyone is blocked by this, tech support can change a single database value if contacted. Table shows version 10240 for Windows Server 2016. While in fact it should be 14393.

 

[Big_Mark]

After updating to SCCM Version 1906 this issue was resolved