ISSUE: Microsoft ADK b25217 or earlier, VAMT 3.1 has issues with Windows Server 2019 / 2022
Affected Products: Windows ADK VAMT 3.x - W11 version 22H2 Windows ADK VAMT 3.x - W11 version 21H2 Windows ADK VAMT 3.x - W10 version 21H2 Windows ADK VAMT 3.x - WS2022 version Windows ADK VAMT 3.x - current preview 1. VAMT 3.1 has the issue that the Windows Server 2022 is still named Windows Server 2021 in the configuration. Introduced with ADK Windows 11 ADK 21H2 / Windows Server 2022 ADK Problem: 2. GVLK for Windows Server 2019 Datacenter or Standard are no longer accepted. Introduced with ADK Windows 11 ADK 22H2 (eventually previous versions) Problem: WS 2019 Standard + Datacenter generic keys can no longer be added to VAMT database. Other product keys seem unaffected. error: GVLK Key source https://learn.microsoft.com/windows-server/get-started/kms-client-activation-keys Thank you for flagging this to the team, it has been discussed in other topics, but I hope the next release of ADK will provide a fix (DB connection issue, is already fixed). TYVM in advance.
For those with Windows Insider Problems to read please before posting in this Server Insiders Forum
For all Windows Insider Build issues Home, Pro, Pro for Workstations, Etc. the Windows Insider Forum is https://learn.microsoft.com/en-us/answers/tags/953/windows-insider Respectfully meaning to be helpful Thank You p.s. Can Microsoft please lock this conversation topic as closed and if possible pin it?
Problems to join Debian/Ubuntu machines to a domain
Is not posible to join Debian/Ubuntu machines to a domain based on Windows Server 2025 (using realm at least) this is the error: ! Couldn't set password for computer account: XXXX$: Message stream modified adcli: joining domain xxxx.local failed: Couldn't set password for computer account: XXXX$: Message stream modified ! Failed to join the domain realm: Couldn't join realm: Failed to join the domain Domain is discoverable vía realm: root@lnms01:/home/administrator# realm discover xxxx.local xxxx.local type: kerberos realm-name: XXXX.LOCAL domain-name: xxxx.local configured: no server-software: active-directory client-software: sssd required-package: sssd-tools required-package: sssd required-package: libnss-sss Tested on WS2025 build 26227 and Linux 6.1.0-21-amd64 x86_64, Linux 6.6.31+rpt-rpi-v8 aarch64 and Linux 6.8.0-31-generic x86_64. Those 3 versions of Linux joined to another doman based con Windows Server 2022 without issues.
Can't roll-back from 25h2 to 24h2.
A few days ago, my PC automatically updated from version 24H2 to 25H2, and ever since then, I've been experiencing persistent issues that I haven't been able to resolve. Unfortunately, the option to roll back to the previous version seems to be unavailable, which has made troubleshooting even more difficult. I've tried just about everything I could think of—tweaking settings, running diagnostics, checking for compatibility problems, and even reaching out to support forums—but nothing has worked so far. It's been incredibly frustrating, and I'm still stuck with the same problem.Windows Server on ARM64 (Insider Previews)
When will there be a preview build of Windows Server on ARM? There is demand for it from developers, and devops personal as well. It is known that it already partial exists due to the article on Azure Host OS. Azure Host OS – Cloud Host - Microsoft Community Hub Please release this so we can test it against our code.Allow for the expansion of physical disks in a storage pool
Allow for the expansion of physical disks in a storage pool just like lvm on Linux. This would be useful in virtual environments and in Azure to be able to expand the physical representation of the virtual disk file. Be it a vmdk or vhdx. This currently allowable on other modern logical volume managers out there. This should be trivial to modify since the meta data is already there. It could be added to the powershell commandlets to rescan-physicaldisk, which would rebuild the metadata on the pool. I have a feedback hub suggestion open on it, which if you could please upvote: https://aka.ms/AAy4ihwIn-place upgrade possibility planned for Windows Server 2025 Datacenter Azure Edition ?
There is currently no official ISO for Windows Server Datacenter: Azure Edition that supports setup.exe /auto upgrade for in-place upgrades. Azure Update Manager does not support OS version upgrades for Azure Edition through optional features. Is anyone aware of a supported workaround?
