Forum Widgets
Latest Discussions
In-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?Release of Windows Server 2025 Datacenter Azure Edition
Hi all, I am happy to see there are still Insider versions of Windows Server Datacenter Azure Edition vNext Is there any ETA for a release for the next iteration after 2022? What are the feature benefits that justify Azure Edition "2025" to be ahead of WS 2025 Thank you for your help!
I can't Turn on network discovery
Hi Why in Advanced sharing settinggs the Turn on network discovery can't save the settings in Windows Server 2019 Preview? Although as an admin I turn it on and save settings, it's again off when I open Advanced sharing settinggs. The second problem is that when I click Choose media streaming optons, I get the message The page failed to load.
Login to account on Server Insider?
Should I login to my Microsoft account on a Windows Server Insider VM, knowing that I will upgrade instead of performing clean installs and that I use the Desktop Experience? And does flighting (install new Server Insider builds via Windows Update) work without a Microsoft account?
Server 2025 Core ADDS DC, Network Profile Showing as "Public" and not as "DomainAuthenticated"
OS: Windows Server 20225 Standard Core (no GUI), build 26085.1 Role: ADDS, DNS ForestMode: Windows2025Forest DomainMode: Windows2025Domain Platform: Hyper-V guest When standing up a clean Windows Server 2025 using server core and configuring it as a domain controller, the network category (profile) always shows as "public." A clean load of Windows Server 2022 with server core as a domain controller has the same behavior. However, in Server 2022, the fix is to add DNS as a required service to the nlasvc (Network Location Awareness) service. Once that is done, the network category reflects "DomainAuthenticed" and persists between reboots. In Server 2025, the nlasvc service does not have the same requiredservices as Windows Server 2022, and it does not start automatically. Even after configuring the nlasvc service the same way it is in Server 2022 and adding DNS as a required service, the network category still reflects "public." The only way to get the network category to properly reflect the "DomainAuthenticated" status is to disable and reenable the network adapter after each reboot.
DNS Server order on DC NICs
DC DNS Settings Hi, I have four domain DCs. What would be the preferred IPv4 'DNS Servers' order on the NICs? DC01 & DC02 are on one 10Gb network and DC03 & DC04 are on another 10GB network. The two networks have a 1Gb link between them. This is what I'm thinking but any advice appreciated. DC01 DC02 DC03 DC04 Loopback DC02 DC01 DC03 DC04 Loopback DC03 DC04 DC01 DC02 Loopback DC04 DC03 DC01 DC02 Loopback
