There is 2021-07 .NET Framework update for Server 21H2 ARM64, but not LCU this time and neither at the time of OOB. It is still Insider Pre-Release so is early days.
My issue is that downloading from opendirectory.luzea.de is not working. EDIT: Nevermind. It's working now! Cheers!
I see them in WSUS under "Windows Insider Pre-Release" product, no other designation for the product, but the title of the update says it. There are 3 updates in total released on patch Tuesday, LCU KB5004243, .NET 3.5 & 4.8 KB5003536 one each for AMD64 and another for ARM64. Still inconsistent with the catalog which is not normal behaviour for a released product, but this is still early. The documentation for the LCU never mentions server 21H2, but Azure Stack HCI which is a different product with common components, not released yet as well. I think we have a bug which if I remember well I noticed first time in June, Domain Controllers do not detect the updates for server 21H2 but only those for the Azure Stack 21H2. This is about the category where the updates are placed and which is selected separately in WSUS. The cab updates for the 2 products are identical bit by bit otherwise, at least in relation to the LCU which I verified specifically. Regular servers (non Domain Controllers) detect the correct updates and possible those for the Azure Stack. The LCU updates can be installed manually or from Windows Update which doesn't care about category as long as some update is detected as needed. The .NET Framework update is not detected, but certainly exists as you found both of them. This might be corrected in the next few days. I am not spending more time with this issue as the server is pre-release and some teething issues are expected, but posted it here if anyone wants to take it further and explain what happens. I cannot see any issue from the mum file and really do not understand very well the metadata detection mechanism when new updates are available.
@ch100 i actually don't run or have any specific technical knowledge about server, i just started to publish the release info's in here because nobody else took it upon him/her to do. I only list what i can find and appreciate (yours and all other members) information and contributions.
Thank you for your contribution. It is extremely useful like all the other contributions in the desktop OS threads. I realised that you are less involved with the server, but as we know well, there are a lot of commonalities between the desktop LTSC and the server with GUI LTSC. The desktop version is not available yet and nobody knows if there will be an equivalent this time although I am expecting one. A lot of people who are posting here are interested in using the "server as workstation" in which I stopped being interested around 2003 when I started encountering display driver issues. Domain Controllers, Hyper-V, Azure cloud were mentioned so some people have interests in those areas, either from the side or involved as system administrators mostly for small business if I understand well. So the server threads are useful even if not mainstream for the forum and don't go in the same level of detail like for the desktop versions.
The matter is way simpler now. Since server 2016 practically there isn't any meaningful difference between server and LTSC. 2016 lacks a couple of audio drivers (which I presume is more a mistake rather than a choice) and BT functionality is not 100% All the difference left are license related not due to missing bits (as usual you can't install a client antivirus some partitioning SW and so on) In short Server2012 essentials, server 2016, 2019 and 2022 are just perfect client machines, with few very small and very easy to fix problems, and a lot of possibilities that Win 10 lacks, starting from the easy way to remove Defender (server manager GUI), w/o resorting to tools like MSMG or NTLITE
When you add the AppCompatibility feature to a server core install it breaks RDP. When you RDP the server you just get a blank screen. Thought they had fixed this already.
It took months for MS to fix RDP in HyperCore 2019 (not sure if Core 2019 was affected too)., I mean AFTER the RTM not when it was in beta stage. The solution was to use rdpwrap or a hacked termserv.dll (the things used to get multiple RDP session on W10). Not sure if it's the old bug resurfacing but the effect is close.
This is something primarily for @abbodi1406 but others who might know please feel free to provide opinions. Stand-alone server Windows 2022 or domain member can get 2021-07 updates from WSUS under the Insider Pre-Release category. Domain Controllers Windows 2022 instead cannot detect 2021-07 LCU or 2021-07 .NET Update. Instead detects 2021-06 .NET Update - regular only, not the 2021-06 Preview which is the same with regular 2021-07. The level of patching, i.e 20348.1 or 20348.75/76 is not relevant, the behaviour is the same. I see in the logs that the detection is performed by a component named TiLight which I can't find in the registry and I don't know what represents (Trusted Installer Light?). What could be different in the detection mechanism between a regular server and a domain controller which is a server "promoted" and changed in many ways but which should not essentially change the WU/MO mechanism? I don't ask for the actual difference if this was not already researched before, but rather for some direction based on Windows 10 experience to do my own investigation, as I understand well that this forum is less specialised in the server OS. If it is too much trouble, please ignore this, it is still Insider Preview after all. Windows Update online behaves differently than WSUS and serves the updates from a different category than WSUS which is not quite normal but again it might be a bit of oversight due to the IP. Note: This is obviously a bug as similar issues are not encountered with other server OS and if I remember well, was not encountered with 2021-06 patches.
can you upload the WindowsUpdate.log from both systems, the standalone and the domain controller one? just open PowerShell and run the "Get-WindowsUpdateLog" command and the file will be placed on your desktop. that file will contain most of the things on which Windows Update will decide what updates it offers, primarily the device parameters and the product array.
@ch100 I don't even know what Domain Controllers are in WSUS, i only see one detectoid for Server 2022 which require/detect WindowsVersion 10.0 / BuildNumber 20348 / ProductType 2 or 3 theoretically, all Server 2022 updates should use it but maybe 2021-07 LCU or 2021-07 .NET have different detection rules