Recent Discussions
Unable to manage DFS namespace from DFS MMC
Error: The namespace cannot be queried. The specified domain either does not exist. Hi, I have an issue with DFS at our site. It has been working fine for years, but recently the ability to manage it using the DFS MMC no longer works. DFS is still working for the users fine and I can map to it manually, but the MMC tool no longer connects. I can create new namespaces fine though. The error is: " The namespace cannot be queried. The specified domain either does not exist or could not be contacted. " I can't risk recreating the namespace due to the impact on users, so anyone have any idea to fix this? Many thanks DB21Views0likes1CommentAllow 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/AAy4ihw17Views0likes0CommentsHyper-v Replica Traffic segregation
We have two standalone Windows 2025 Hyper-v Servers. They have been configured with a network team for Management, one for VM traffic and one for replica traffic. We have configured both hosts with self-signed certificate to configure HTTPS replica. The two hosts FQDN are host1.company.com host2.company.com and those names are resolved in the DNS with the management Network IP. To have the replica going through the "replica team" we created on each host's host file two entry like host1.repl.company.com host2.repl.company.com pointing to the replica network IP. The self-signed certificate of each host contains both fqdn ( xxx.company.com, xxx.repl.company.com ) Problem is that when activating a replica for a VM if we chose xxx.repl.company.com as replication partner the process fails with the error that the hosts cannot be contacted, if we use the fqdn company.com it works. To test connectivity we also set the hosts file using the replica network IP for the company.com FQDN and it works. So it's like it doesn't like the FQDN repl.company.,com Any Idea on what the issue might be ? thanks28Views0likes1CommentWindows Server Datacenter: Azure Edition preview build 26491 now available in Azure
Hello Windows Server Insiders! We welcome you to try Windows Server vNext Datacenter: Azure Edition preview build 26491 in both Desktop experience and Core version on the Microsoft Server Operating Systems Preview offer in Azure. Azure Edition is optimized for operation in the Azure environment. For additional information, see Preview: Windows Server VNext Datacenter (Azure Edition) for Azure Automanage on Microsoft Docs. For more information about this build, see Announcing Windows Server vNext Preview Build 26491 | Microsoft Community Hub.Cluster Aware Updating is Failing with Sep 2025 Updates
We have a failover cluster running on Server 2019, providing file shares. We have been using Cluster Aware Updating with no issues for years now. Suddenly with the Sep 2025 updates it's failing. We did replace out WSUS server for Sep updates, and discovered the cluster nodes had the old server IP configured for WSUS, instead of the DNS alias. But even after correcting that and rebooting both nodes, it still fails. The logs for it when it tries to run " Could not initialize internal Windows PowerShell: (RemoteException) Running startup script threw an error: The specified module 'Hyper-V' was not loaded because no valid module file was found in any module directory.." We of course do not have anything HyperV running. I believer the underlying issue is the beginning of that message "Could not initialize internal Windows PowerShell" I have checked that WMI and WRM are running on both nodes. When running a status check within the CAU GUI, it gives all green checks. Nothing has changed, other than that WSUS server update.44Views0likes1CommentWireless secure Windows server 2022
Hello everyone, I am trying to implement ‘wireless secure’ in my domain. I have followed various guides and everything seems to be configured correctly, but I keep getting this error: Reason: Explicit EAP error received Error: 0x40420016 EAP reason: 0x40420016 EAP root cause string: Network authentication failed\nThe authentication method required to connect to the network is not available in Windows. EAP error: 0x40420016 I have verified that communication via AP-WLC-NPS is working correctly, but it is unable to authenticate via eap-tls. Do you have any suggestions? I have collected several logs, but many of them may not be necessary. Thank you for your support.Solved90Views0likes1CommentClients failed to obtain internet right after DC 01 failover to DC02.
Hi, Recently, our team conducted a Disaster Recovery (DR) exercise where we successfully failed over from DC01 to DC02. The objective was to verify that DC02 could take over Windows services such as DNS, DHCP, and Active Directory (AD) to ensure business continuity. However, after shutting down DC01, we observed the following issues: Clients began losing internet connectivity. DHCP failed to lease addresses to clients. Connectivity on client machines was only restored after running the ipconfig /flushdns command, which forced them to communicate with DC02. Everything when back to normal when we resumed AD01. For additional context, our environment is also using ClearPass as the RADIUS server and has no issue authenticating clients. I would like to seek advice from anyone with expertise in this area: did we overlook any critical steps during or after the failover process?65Views0likes1CommentAnnouncing Windows Server vNext Preview Build 26491
Announcing Windows Server vNext Preview Build 26491 Hello Windows Server Insiders! Today we are pleased to release a new build of the next Windows Server Long-Term Servicing Channel (LTSC) Preview that contains both the Desktop Experience and Server Core installation options for Datacenter and Standard editions and Azure Edition (for VM evaluation only). Branding remains, Windows Server 2025, in this preview - when reporting issues please refer to Windows Server vNext preview. If you signed up for Server Flighting, you should receive this new build automatically. What's New Windows Server Flighting is here!! If you signed up for Server Flighting, you should receive this new build automatically later today. For more information, see Welcome to Windows Insider flighting on Windows Server - Microsoft Community Hub Feedback Hub app is now available for Server Desktop users! The app should automatically update with the latest version, but if it does not, simply Check for updates in the app’s settings tab. Known Issues Download Windows Server Insider Preview (microsoft.com) Flighting: The label for this flight may incorrectly reference Windows 11. However, when selected, the package installed is the Windows Server update. Please ignore the label and proceed with installing your flight. This issue will be addressed in a future release. Available Downloads Downloads to certain countries may not be available. See Microsoft suspends new sales in Russia - Microsoft On the Issues. Windows Server Long-Term Servicing Channel Preview in ISO format in 18 languages, and in VHDX format in English only. Windows Server Datacenter Azure Edition Preview in ISO and VHDX format, English only. Microsoft Server Languages and Optional Features Preview Keys: Keys are valid for preview builds only Server Standard: MFY9F-XBN2F-TYFMP-CCV49-RMYVH Datacenter: 2KNJJ-33Y9H-2GXGX-KMQWH-G6H67 Azure Edition does not accept a key. Symbols: Available on the public symbol server – see Using the Microsoft Symbol Server. Expiration: This Windows Server Preview will expire September 15, 2026. How to Download Registered Insiders may navigate directly to the Windows Server Insider Preview download page. If you have not yet registered as an Insider, see GETTING STARTED WITH SERVER on the Windows Insiders for Business portal. We value your feedback! The most important part of the release cycle is to hear what's working and what needs to be improved, so your feedback is extremely valued. Please use the new Feedback Hub app for Windows Server if you are running a Desktop version of Server. If you are using a Core edition, or if you are unable to use the Feedback Hub app, you can use your registered Windows 10 or Windows 11 Insider device and use the Feedback Hub application. In the app, choose the Windows Server category and then the appropriate subcategory for your feedback. In the title of the Feedback, please indicate the build number you are providing feedback on as shown below to ensure that your issue is attributed to the right version: [Server #####] Title of my feedback See Give Feedback on Windows Server via Feedback Hub for specifics. The Windows Server Insiders space on the Microsoft Tech Communities supports preview builds of the next version of Windows Server. Use the forum to collaborate, share and learn from experts. For versions that have been released to general availability in market, try the Windows Server for IT Pro forum or contact Support for Business. Diagnostic and Usage Information Microsoft collects this information over the internet to help keep Windows secure and up to date, troubleshoot problems, and make product improvements. Microsoft server operating systems can be configured to turn diagnostic data off, send Required diagnostic data, or send Optional diagnostic data. During previews, Microsoft asks that you change the default setting to Optional to provide the best automatic feedback and help us improve the final product. Administrators can change the level of information collection through Settings. For details, see http://aka.ms/winserverdata. Also see the Microsoft Privacy Statement. Terms of Use This is pre-release software - it is provided for use "as-is" and is not supported in production environments. Users are responsible for installing any updates that may be made available from Windows Update. All pre-release software made available to you via the Windows Server Insider program is governed by the Insider Terms of Use.List with FQDNs and IPs for updates via proxy
Good day, I am sorry if its the wrong subspace. I have a couple of Windows servers above or equal server 2016 that do download updates directly from the internet via a proxy. I can not find a website by MS that lists all needed IPs and ports that are to be opened on the proxy to do that successfully. Since a month ago, it failed and we think the reason is that some more requirements we were not aware of were added. Best Regards18Views0likes0CommentsSSO for PowerShell in WAC
So we have WAC setup working with Delegated access for the servers with no login prompts, however once you attempt to load PowerShell it does prompt for creds, I take it this is by default to re-verify the creds. The problem we have is that we are transitioning to a PAM solution and will not have access to the passwords, does anyone know if there is a way to force it to use delegation or to inject the creds of the service account running WAC?785Views2likes1CommentNPS fails to generate logs
I have a new 2025 domain and am setting up 802.1X to allow access to users/computers using certificate based authentication. I have a CA installed on a new 2025 member server and configured that role and also have Group Policies deployed to enroll users/computers with the certificate needed to connect internal WiFi/wired networks. I've verified clients are receiving all needed certs and the root cert. I have installed NPS (same server has CA), registered to AD, added Radius clients and configured policies. Everything looks good except...nothing works. Clients are not receiving authentication responses (just timeouts) and there are no logs being generated. Also, there are no relevant entries in the Windows Event Logs. I enabled auditing via the cmd line and verified it is enabled. I've also forced auditing via Group Policy. I've verified the NPS log location and have even tried moving it to other folders to see if it was a permission issue. I'm out of ideas. What else can I try?13Views0likes0CommentsRDP Long delay between Longon-Event and GPO-Processing
Hello, i have an 2019 rdp connection-broker and some 2019 session-hosts with current os. Sometimes it takes a very long time (up to 15 minutes) between the logon at the session-host till i get an desktop. In the event-log i see the security-event 4624 (an account was logged on) at 08:02. If i check gpresult for this user i see the processing of the gpo startet at 08:16 and is finished in a few seconds. And this times match with the user-experience that they see a "loading user profile" message. How can i get information which task takes so long? Regards Arnold19Views0likes0CommentsWindows Server Datacenter: Azure Edition preview build 26484 now available in Azure
Hello Windows Server Insiders! We welcome you to try Windows Server vNext Datacenter: Azure Edition preview build 26484 in both Desktop experience and Core version on the Microsoft Server Operating Systems Preview offer in Azure. Azure Edition is optimized for operation in the Azure environment. For additional information, see Preview: Windows Server VNext Datacenter (Azure Edition) for Azure Automanage on Microsoft Docs. For more information about this build, see Announcing Windows Server vNext Preview Build 26484 | Microsoft Community Hub.Unable to personalize display in Hyper-V VM
I have two physical servers running Windows Server 2025 Standard Edition, each with Hyper-V installed. On the first 2025 server, I have no issues adjusting video/personalization settings in running virtual machines. On the second server, I created a 2025 domain controller but I am unable to adjust any of the video settings ("remote resolution changes not allowed") even though enhanced sessions are enabled. How can I fix this on the second server? Thanks.28Views0likes0CommentsServer 2025 - unable to Open shared files and webpages on another 2025 Server
I have three or 4 2025 virtual servers on our domain penciled in to replace some older servers. All the servers have file and storage roles and one is an IIS server as well. If i try and open a shared file from any 2025 server the windows users name and password pop up opens and you cannot get past it. If trying to open a IIS site from a 2025 server you cannot either. From any other older server or client the share and the webpages are accessible and work as expected. I obviously need this to work as these servers are part of an ERP Environment and need to have access to each other. I've Searched the web and tried some of the suggestions but nothing so far has worked. DNS has passed, pings have passed, Using IP brings the same issues. Help150Views0likes3CommentsUnable to Install Windows Server 2022 standard Edition
Hi Team , i'm trying to install the iso of windows server 2022 downloaded from microsoft web site. but i'm receiving an error message at the beginning of the installation. the error message is saying : " windows cannot find the Microsoft Software License Terms. Make sure the installation source is valid " . i kindly request your help on how i can resolve this issue32Views0likes0Comments
Events
Recent Blogs
- 5 MIN READAbout media-based upgrade to Windows Server 2025 With N-4 media based upgrades, you can upgrade your organization’s physical devices and virtual machines directly from Windows Server 2012R2, Window...Sep 23, 20251.5KViews3likes2Comments
- 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, 20256.4KViews7likes3Comments