Forum Widgets
Latest Discussions
Hyper-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 ? thanks
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 DBCluster 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.Clients 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?
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 Regards
NPS 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?
RDP 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 ArnoldUnable 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.
Server 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. Help
