Recent Discussions
Default Profile not setting Backgroud
Hello, this is driving me nuts! I'm just preparing our template for Windows Server 2025 VM rollout. I try to set a solid background in the default profile (c:\uses\default\ntuser.dat), so every new user gets this as default background. I have set HKCU\Control Panel\Colors Background REG_SZ 50 84 154 HKCU\Control Panel\Desktop Wallpaper REG_SZ HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\DesktopSpotlight\Settings EnabledState DWORD 0 HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Wallpapers BackgroundType DWORD 1 but every new user/profile still gets the windows default background image (C:\WINDOWS\web\wallpaper\Windows\img0.jpg). Don't want to use GPOs, as the setting should be optional. All other settings from teh default profile copy all right. Anyone any idea? Thanx! Cheers __Leo
vNVMe on Hyper-V to unlock PCIe 5.0 NVMe performance
On hosts with NVMe PCIe 5.0 (E3.S/U.2), Hyper-V guests still use virtual SCSI and leave a lot of performance on the table. We are paying for top-tier storage, yet software becomes the limiter. A virtual NVMe device that preserves checkpoints/Replica/Live Migration would align guest performance with modern hardware without forcing DDA and its operational trade-offs.
DCs not replicating across VPN
I am at a loss here. I have looked at every CMD option I can find, verified DNS and cannot get my DCs replicating across the VPN. I don't understand how I was able to join the domain but now the connectivity is a problem. So here is my setup: 2 DCs in Site (my building) 2 DCs in Datacenter connected by IPSec VPN I can ping the IP, the DNS name, the short name, and the domain from all DCs regardless of location. I have verified on each DNS server that the name servers are correct and resolved. I have run nltest, dcdiag, syncall, repadmin, etc. The only error that keeps showing up in most commands is 1722 network error. RPC unavailable. Topology incomplete. One oddity that I found was that on the DCs in the datacenter Sites and Services was missing one of the local DCs. I added it manually but there are no NTDS Settings for it. I have flushed DNS, reregistered DNS, restarted the servers. All Windows firewalls are set to ANY ANY for domain services. My WAN firewalls are ANY ANY between the sites I have no idea what to look for next. Please if anyone has ideas let me know. Also I have already build new servers multiple times and this keeps happening.
Server 2016 Essentials Version 1607 (OS Build 14393.8246)
Hi. Ive had some problems with this server recently and im trying to use DISM to restore health. Problem is Im unable to find the copy of the OS to do it. The only version we have been able to find is a later version which obviously wont work. Any thought on where I can find a copy? MS only seem to have eval versions of 2016. ThanksServer 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.
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?
Active Directory Unable to reset user passwords
I am managing a Windows Server 2025 Active Directory environment with client machines. I created a test user and enabled the option “User must change password at next logon.” I then provided a temporary password to the user, expecting them to get the prompt to change it on first login. However, when the user attempts to change the password, they receive the error: “The user must change password before signing in.” My goal is that when I provide a temporary password to a user: They get the prompt to change the password at next logon. When they change it, it should not throw the “user must change password before signing in” error. I need guidance on how to achieve this so users can reset their passwords successfully.WAC Extension VM Conversion: Pre-checks failed: PowerCLI is not installed
Hi, i have Windows Administration Center Version 2410 Build 2.4.2.1, i try to migrate VMware VMs to Hyper-V using WAC Extension VM Conversion and when i start sync i get this error: Pre-checks failed: PowerCLI is not installed. Please install PowerCLI and try again.. Check the logs for details. (1%) but PowerCLI is already installed with offline installation procedure because no internet connexion available in my environment, i can import vmware.powercli module in powershel but same error in WAC Than you for your helpMICROSOFT XPS DOCUMENT WRITER
Good Day! Does anyone know who to install the same MICROSOFT XPS DOCUMENT WRITER that installs on WINDOWS 10/11 on SERVER 2025. An application needs it to send emails with attachments via OUTLOOK. None of the drivers available to install manually are the same as the one on WINDOWS 10/11. Thank you!Windows update failure Error 0x8024200B
Windows server 2022 standard version 21H2 Installed 08/04/2025 OS Build 20348.3807 KB5063880 installation failed. Error 0x8024200B Latest servicing stack installed 10.0.20348.4160 Can't get the update to install, been through the entire guide on how to reset windows update etc. The only solution I can find is to reset windows and reinstall the OS, but surely that is a bit drastic for a security update, especially since the server was installed only 5 months ago? Any help would be useful please!
Modernized Gateway - WinRM over HTTPS
Hi I wanted to try the modernized gateway preview but I get the "WinRM cannot complete the operation" when trying to connect to any server imported in WAC. The same action works just fine with the 2311 version though. It's like the Modernized Gateway just ignores the "Force WinRM over HTTPS" setting. Has anyone faced the same issue ? Is there a workaround for this ? We do not want WinRM over HTTP.
Recent Blogs
- Hello team, Manuel here. In recent years, Microsoft has introduced Strong Certificate Name Mapping (Strong Mapping) as a requirement for certificate-based authentication in Active Directory environme...Sep 05, 2025
- Welcome to part four of our Networking Deployment Series for Windows Server 2025! In this series, we’ve been following Contoso Medical Center’s journey to deploy Windows Server 2025 Software Defined ...Aug 28, 2025
