Oh you great instructor freak, teach me please, how to maintain tons of threads for c**ts like you to f**k them up over and over....
https://forums.mydigitallife.net/threads/server-ip-ltsc-builds.84158/page-25#post-1801692 Added all checksums...
https://forums.mydigitallife.net/threads/server-ip-ltsc-builds.84158/page-25#post-1801692 Added KiT ISO mirror and SVFSFX Repo.
Ok, not to distract people from the whining about the thread title, why people care so f**king much, I have no idea, its pretty clear to me what this thread is for and is about... When I use this build and multiple ones before this to spin up a couple domain controller, the non fsmo role holder keeps marking the network as "public" instead of "domain authenticated" like it should.
Last time I checked forums were intended to help people, *all* people, not just an elite who already know where to look. Last time I checked when you cand do a good job (w/o additional effort) but you do a bad one, there must be a reason. That reason is pretty clear to me, obviusly is less clear to people who comes here once in a while, and don't follow what happens outside the server room. Not the right time to hope for decent builds. They started to screw up a lot of things since 252xx or so, now with 259xx thew messed the things further. Likely they decided to pospone a bit the release and to follow the route of Win12, so they don't care to break things that worked until "yesterday"
Just noticed that in 25931 the expiration date is pushed to September 2024, which means we are now sure that the release date will be after that date. In short: Surely Server 11 will NOT be called Server 2024 Surely will not be released as companion of LTSC 2024, but will be a different thing, like the last round LTSC2021/Server 2022 Very likely the release date will be something like October/November 2024 And there is also a possibility that Server 11 will never exist as a released product and we will get directly a "Server 12" release, branded as Server 2025. The abrupt changes between 253xx and 259xx builds could point in that direction.
Just to note since I went over it before, I had trouble with getting the already installed Duckduckgo Browser to actually launch after upgrading... and in fact with installing virtually all varieties of .appinstaller and related bundle files. Everything was reporting "class not registered" when trying, even though they were showing the correct install icons. This did NOT happen on the upgrade to 25921 from prior - only from 25921 to 25931. The solution was from Powershell to do; Get-AppxPackage -allusers | foreach {Add-AppxPackage -register "$($_.InstallLocation)\appxmanifest.xml" -DisableDevelopmentMode} The DDG Browser and files immediately worked again.