Kerberos KDC Errors
Hello, I have been testing Windows Server 2025 with AD DC role and sometimes in event log I can see error. The Security Account Manager failed a KDC request in an unexpected way. The error is in the data field. The account name was and lookup type 0x108. Just a note - I did not remove the account name; it is not just there, not even once. I'm unable to connect it to some "action", so it looks a bit random. In data field there is only C000000D (in words) which is every time the same. Event ID is 7. Is this okay or anything to worry about?Windows Server 2025 is generally available as of Nov 1!!
Sweet! Build 26100.1742 is the final, 'RTM'. Available for download now on M365 Admin Center website (formerly VLSC) and other official download locations. Windows Server 2025 known issues and notifications | Microsoft Learn Windows Server release information | Microsoft Learn What's new in Windows Server 2025 | Microsoft Learn Happy downloading, installing...in-place upgrading! 😉 - MichaelWindows Server on ARM64 (Insider Previews)
When will there be a preview build of Windows Server on ARM? There is demandfor 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.b26085 - Windows Server 2025 Domain Controller fail to deploy via DSC
Hi there, I am trying to deploy mslab using Windows Server 2025 preview VM using Windows Server 2025 OS as a Hyper-V platform. I believe Jaromir as maintainer of mslab opened an SR. In result he updated the code, plus PS DSC Modules. edit: this issue is unrelated to the running SR. Still the deployment of the domain controller template will fail during first boot. This is not specific to b26085, this one is troubling for since WS2025 insider, so it never worked with this branch. Repro steps Install Windows Server 2025 b26085.1 on a physical machine and enable Hyper-V Download and extract mslab https://github.com/microsoft/MSLab/releases/tag/v24.04.1 run the mslab scripts in order 1_Prereq 2_CreateParentDisks > select Windows Server 2025 ISO b26085 (WS 2022 ISO will work) > skip the MSU dialogue Domain Controller VM gets created from parent disk image First boot will fail with following error Creating DC VM Applying Unattend and copying Powershell DSC Modules PSPath : Microsoft.PowerShell.Core\FileSystem::J:\mslab_v24.04.1\Temp\MountDir PSParentPath : Microsoft.PowerShell.Core\FileSystem::J:\mslab_v24.04.1\Temp PSChildName : MountDir PSDrive : J PSProvider : Microsoft.PowerShell.Core\FileSystem PSIsContainer : True Name : MountDir FullName : J:\mslab_v24.04.1\Temp\MountDir Parent : Temp Exists : True Root : J:\ Extension : CreationTime : 21.04.2024 13:20:16 CreationTimeUtc : 21.04.2024 11:20:16 LastAccessTime : 21.04.2024 13:20:16 LastAccessTimeUtc : 21.04.2024 11:20:16 LastWriteTime : 21.04.2024 13:20:16 LastWriteTimeUtc : 21.04.2024 11:20:16 Attributes : Directory Mode : d----- BaseName : MountDir Target : {} LinkType : Path : J:\mslab_v24.04.1\Temp\MountDir Online : False Path : J:\mslab_v24.04.1\Temp\MountDir Online : False PSPath : Microsoft.PowerShell.Core\FileSystem::J:\mslab_v24.04.1\Temp\MountDir\Windows\Panther PSParentPath : Microsoft.PowerShell.Core\FileSystem::J:\mslab_v24.04.1\Temp\MountDir\Windows PSChildName : Panther PSDrive : J PSProvider : Microsoft.PowerShell.Core\FileSystem PSIsContainer : True Name : Panther FullName : J:\mslab_v24.04.1\Temp\MountDir\Windows\Panther Parent : Windows Exists : True Root : J:\ Extension : CreationTime : 21.04.2024 13:20:22 CreationTimeUtc : 21.04.2024 11:20:22 LastAccessTime : 21.04.2024 13:20:22 LastAccessTimeUtc : 21.04.2024 11:20:22 LastWriteTime : 21.04.2024 13:20:22 LastWriteTimeUtc : 21.04.2024 11:20:22 Attributes : Directory Mode : d----- BaseName : Panther Target : {J:\Windows\Panther} LinkType : Creating DSC Configs for DC LastWriteTime : 21.04.2024 13:20:23 Length : 1206 Name : DC.meta.mof LastWriteTime : 21.04.2024 13:20:25 Length : 32600 Name : DC.mof Copying DSC configurations (pending.mof and metaconfig.mof) Applying changes to VHD LogPath : C:\WINDOWS\Logs\DISM\dism.log ScratchDirectory : LogLevel : WarningsInfo Starting DC Configuring DC using DSC takes a while. Initial configuration in progress. Sleeping 250 seconds Question: What could be reasons it keeps failing? We have no clue / pointers and imho it would be expected and necessary that mslab works with WS2025, despite being preview, too. Who at Microsoft could afford time to repro and looking into that? As mslab is also used by Microsoft, I hope anyone could spare time to investigate (with Jaromir and/or me). I personally can spare time for that investigation. Thank you very much in advance!
If only MS would take more care of details...
Currently setting up the "deduplication-corruption repo with newest pre-release Server 2025 as L1 and L2 VMs". And then I see this: It is still the problem a lot of "Client only, never needed or wanted on a server by default" stuff creeps into the Server UI. Another example of today is this bad default setting: Microsoft could do so much better if it would take more care of details, reduce the Marketing/Public-Relations (previously known as Propaganda Departement) budget and invest more in actual quality. Please Dave Cutler, you have to rescue Windows - AGAIN, like you did when XP was released (i.e. when it was SP0, I remember how bad it was at first)...
Microsoft 365 and Microsoft Office 2024 LTSC support on Windows Server 2025
For now, it is not clear if Microsoft 365 apps shall be supported on Windows Server 2025, at least during the mainstream support of the OS, although earlier there statements that said that they will be supported. Microsoft Office 2024 LTSC does not include Windows Server 2025 as a supported OS. Would this mean it shall not be installable? Perhaps a the limited Microsoft 365 model shall be applied? I am interested in having office apps installed for offline use, on demand, on Windows Server 2025. Are there any clear and recent information on this topic?
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.
