Forum Widgets
Latest Discussions
Windows event collector (WEC) troubles
Hi all. I have really frustrating issue I can`t resolve. We have set up WEC, a long time ago... Now I upgraded in-place to server 2025 and it`s behaving really weird. Problem is this: I created new subscription and my PC was sending events just fine yesterday. I rebooted server and my PC, still all is fine. Turned off my PC, went to sleep, started working in the morning and NO logs from my machine in WEC. At all. Other PCs also randomy sending logs some yes some no. So I tested WinRM connectivity all fine. Error on my PC: The forwarder is having a problem communicating with subscription manager at address http://MYWECSERVER:5985/wsman/SubscriptionManager/WEC. Error code is 2150859263 and Error Message is <f:WSManFault xmlns:f="http://schemas.microsoft.com/wbem/wsman/1/wsmanfault" Code="2150859263" Machine="MYWECSERVER"><f:Message> <f:ProviderFault provider="Subscription Manager Provider" path="%systemroot%\system32\WsmSvc.dll"> <f:WSManFault xmlns:f="http://schemas.microsoft.com/wbem/wsman/1/wsmanfault" Code="2150859263" Machine="MYWECSERVER"> <f:Message>The event source of the push subscription is in disable or inactive on the Event controller server. </f:Message></f:WSManFault></f:ProviderFault></f:Message></f:WSManFault>. I have also some errors on WEC server: The Subscription DomainComputers could not be activated on target machine MY-PERSONAL-PC due to communication error. Error Code is 0. All retries have been performed before reaching this point and so the subscription will remain inactive on this target until subscription is resubmitted / reset. Additional fault message: eventsource is in either disable or inactive state OR The Subscription DomainComputers could not be activated on target machine MY-PERSONAL-PC due to communication error. Error Code is 20. All retries have been performed before reaching this point and so the subscription will remain inactive on this target until subscription is resubmitted / reset. Additional fault message: eventsource is in either disable or inactive state Also runtime status is like this: A lot of Active computers, mine is in yellow Inactive state... I have NO idea how to fix this, and why it works for some clients and not for others and most perplexing question, why it worked yesterday until sleep. Just like that WEC sets status to Inactive and then my PC sends logs and does not change status back to Active. Thanks for all suggestions!
Untagged VLAN - Server 2025 Hyper-V
Hi, I have a strage issue and not finding a solution. Using Server 2025 with two node Hyper-V cluster. Most of the machines using VLANs which works fine. Some machines using no VLAN config. Which usually means the "Access VLAN 1" regarding our switch configuration. With Server 2019 this worked fine. With Server 2025 same NIC port, same server/NIC hardware "Untagged" VMs don't get any network connection. If I add a second NIC to the VM "Untagged" the NIC get immidiatly an IP address and has a proper connection. If I remove the first NIC, the second NIC stop working. It looks like something has changed with Server 2025 (maybe already with Server 2022). Do you have any idea what kinde of problem I have found? Thanks Jack
No SET-Switch Team possible on Intel X710 NICs?
Hello, we have lot of servers from different vendors using Intel X710 DA2 network cards. They work fine in standalone and they work fine if we create switch independet teams using Server Manager, Regardless of Dynmic or Hyper-V Port. But sadly we can't use these teams in Server 2025 because have to create SET-Switch Teams instead. But as soon as we create an Hyper-V SET-Switch Team with X710 cards, they have limited to no network communication. They still can communicate with some servers, are slow with some ohters, and can't communicate with some at all. Especially communication to other servers, which also use X710 cards with SET-Switches, is zero. SET-Teams with other cards like E810 work just fine. I've read several times that the X710 cards just wont work with SET, even since Server 2016. But I can't really give up on this, since we would have to replace a lot of them. We have tried to disable a lot of features like VMQ, RSS, RCS... but couln't make it work. Firmware and Drivers are the most recent, but it happens with older versions too. Does anyone have a solution? Thank you!
Windows Server 2019 AD & DNS replication
Hello, I'm running into issues with AD & DNS replication on a recently joined server in our environment. Environment: Three writable DCs in separate sites: Server A (Site A) – Windows Server 2019, AD DS & DNS (healthy) Server B (Site B) – Windows Server 2019, AD DS & DNS (healthy) Server C (Site B, new) – Windows Server 2019, AD DS & DNS (failing) Issues Observed Inbound replication to Server C from Server A & Server B successfully propagates for both AD and DNS zone/record changes. Outbound replication from Server C to Server A & Server B fails for both AD and DNS zone/record changes. Server A logs Event ID 1311 (KCC). Server A & B logs Event ID 1925 when trying to establish the link to Server C. What I’ve Tried: Pointed each servers NIC's to a heathy DC with the correct suffix. I've checked any windows FW and network FW rules to make sure no blockages. Verified A+SRV records for both heathy DC's. Confirmed AD-Integrated zones on all 3 servers show correct ACLs and records. I've tried running repadmin → still errors. Tested RPC connectivity: TCP 135 open. Ensured subnets/site mappings are correct in Sites and Services. I've tried to seed a zone and record on the healthy servers in efforts of t/s. Any help would be greatly appreciated!WiFi Computer-based authentication not working (WS 2019)
We are trying to do computer-based authentication for our endpoints locally (on-prem AD) and it is not working whatsoever. My CA and NPS are all on one server (WS 2019) and are setup correctly. - I deployed a certificate template (I duplicated Computer and gave read, enroll, and autoenroll to Desktop Computers) - I registered NPS with AD. - I setup RADIUS through my Unifi setup and NPS (including the APs) - I created a Connection Request Policy that checks to see if it is a wireless connection coming in. - I created a Network policy for Smart Card or other Certificate ensuring that the CA certificate is selected. - I created a Wireless policy for my endpoints and selected the CA as the option in the security settings (and as Computer authentication). When I go to connect to the SSID, it shows the Certificate details for issued to and issued by as the CA server, but it gives an error that it can't connect to the network.
NTLMv1 authentication
I know this is long overdue, but in pursuit. I have identified our Radius servers (Windows Server 2019 NPS) as the main source of NTLMv1 authentications taking place. I want to disable NTLMv1 and LM, and enforce at least NTLMv2 within our Windows Environment. The radius servers are used to provide network access, wired and wireless. How can we make sure that NTLMv1 is no longer used?Windows Server 2025: SET failover much slower than traditional NIC Teaming
Hello everyone, I'm experiencing a significant performance difference between Switch Embedded Teaming (SET) and traditional NIC Teaming regarding failover times, and I'm seeking insights or potential solutions. Environment: Host: Windows Server 2025 Standard (physical servers) Guest: Windows Server 2025 Standard VMs NICs: Two 1Gbps adapters in SET configuration. I’m aware that 10Gbps NICs are recommended for SET, but our workload requirements are modest and 1Gbps is sufficient in this case. Load balancing algorithm: Dynamic (also tested Hyper-V Port with identical results) VMs configured with VLANs Switch: Spanning-tree Portfast enabled Issue: During failover testing by physically removing network cables, SET shows dramatically longer network interruption compared to traditional Windows NIC Teaming (LBFO): SET: Up to 20 seconds of communication interruption Traditional NIC Teaming (Static LAG/LACP): Typically under 3 seconds Each VM typically uses only one of the two physical adapters at a time. When the cable is removed from the adapter not in use by the VM, no communication loss occurs. However, when removing the cable from the adapter actively used by the VM, we observe a network disruption of around 4 seconds in the best case, and up to 20 seconds in the worst case. Notably, reconnecting the cable does not cause any disruption, regardless of which adapter is used. Test Method: We used a PowerShell script that pings the target VM at 0.1-second intervals to detect even short interruptions. Here’s the script used for monitoring: $PingTarget = "192.168.10.5" while ($true) { $start_time = Get-Date $result = Test-Connection -ComputerName $PingTarget -Count 1 -ErrorAction SilentlyContinue $log_entry = Get-Date -Format 'yyyy-MM-dd HH:mm:ss.fff' if ($result) { $log_entry += " Reply from $($result.Address)" } else { $log_entry += " No response from $PingTarget" } Write-Host $log_entry $end_time = Get-Date $elapsed = ($end_time - $start_time).TotalSeconds $sleep_time = [math]::Max(0.1 -$elapsed, 0) Start-Sleep -Milliseconds ($sleep_time * 1000) } Traffic was generated via VM-to-VM communication between separate Hyper-V hosts, and results were consistent across comparable environments. Verification: Identical NICs (make/model/speed/config) Latest firmware and drivers applied Both Dynamic and Hyper-V Port algorithms tested All adapters showed “Up” state via Get-NetAdapter Questions: Is this extended failover time (20s vs 3s) expected behavior for SET compared to traditional NIC Teaming? Are there configuration parameters or registry settings that could help reduce SET failover detection/recovery time? Are there architectural differences in how SET and LBFO detect failures that could explain this discrepancy? Could the Hyper-V virtual switch integration be contributing to the delay in failover detection? This behavior is reproducible across multiple identical server configurations. Any guidance, references, or troubleshooting suggestions would be greatly appreciated. Thank you for your time and expertise!HyperV 12 on Windows 2025 ready for production?
Fighting with three HyperV servers in a failover cluster. I understand that now you have to use SET teaming and lbfo is no longer supported. I also understand that SET is still quite buggy. I have created three teams with two adapters in each of them, but it confuses me how they appear in "Network and internet > Ethernet" vs "Advanced Network setting. I have set the vEthernets to the static IPs that I need. But the way the NIC shows up seems random... Some of them shows the IP of the vEthenets and they are all set to DHCP Network seems very unstable if I use more than one NIC in a team. As far as I can google, I am not the only one having these issues. SET networking does not work stable if more than 1 NIC - correct? So if one needs an HA setup - how to handle NIC teaming correct? Can HyperV 12 on Windows 2025 be used in a prof. live setup? thx...Install RD Web Client on Windows Server 2022 – Complete Setup Guide
To access Remote Desktop only via the browser, install the Web Client package --- Step 1: Export the Self-Signed Certificate * Open **Run** → type `certlm.msc` * Navigate to **Personal** → **Certificates** * Select the certificate created for the **RD Connection Broker** * Export the certificate (e.g., to `C:\temp\abcde.cer`) --- Step 2: Install and Publish Web Client Package Open Windows PowerShell 5.1 and run: powershell Install-Module PowerShellGet -Force Install-Module RDWebClientManagement Import-Module RDWebClientManagement # Clean up any stale IIS locks Reset-IISServerManager -Confirm:$false Remove-Module IISAdministration -ErrorAction SilentlyContinue Import-Module RDWebClientManagement # Install the Web Client Install-RDWebClientPackage # Import the exported certificate Import-RDWebClientBrokerCert "C:\temp\abcde.cer" # Publish the Web Client for production Publish-RDWebClientPackage -Type Production -Latest --- Step 3: Access the Web Client Visit: https://<your-serverFQDN>/RDWeb/webclient/index.html If the page does not appear: Restart the **Default Web Site** in **IIS Manager**. Ensure the **webclient** folder is present under the IIS site directory. Check if the correct certificate is applied under **Bindings** in IIS. If want Beginning from Remote access deployment- use this link - Remote Access via HTTPS RDP Web Client on Windows Server 2022 - Installation Issue Solved . | Microsoft Community HubWindows Server 2025 Datacenter - Windows search stopped to work
Hello, Following the most recent cumulative Windows update (June 2025), Windows Search has stopped functioning on our Windows Server 2025 Datacenter. When we attempt to search, a blank window appears and loads indefinitely without returning any results. This is version of affected system: Troubleshooting Steps We've Tried: Checked for additional updates (only security updates were available) Restarted the Windows Search service Restarted Windows Explorer via Task Manager Restarted the server Ran the Windows Troubleshooter Rebuilt the search index Ran sfc /scannow and DISM health checks Has anyone else experienced this issue? If so, were you able to resolve it? Any help would be appreciated. Thanks!
