Recent Discussions
DC Client DNS Config
Hello, We have two buildings and two DCs in each building. The network speed within each building, between DCs, is 10Gb. The network speed between the buildings is 1Gb. There is a single domain and a single AD site. Each DC has AD integrated DNS. What should the DNS settings be on each server? I'm thinking.. Building 1 DC1 Building 1 DC2 Building 2 DC1 Building 2 DC2 Loopback Building 1 DC2 Building 1 DC1 Building 2 DC1 Building 2 DC2 Loopback Building 2 DC1 Building 2 DC2 Building 1 DC1 Building 1 DC2 Loopback Building 2 DC2 Building 2 DC1 Building 1 DC1 Building 1 DC2 Loopback If there were two AD sites, I'd have each site DC1 point to DC2 on the same site and itself by loopback. I'd have DC2 point to DC1 on the same site and itself by loopback. But with a 1Gb link between buildings, it doesn't seem necessary to have two AD sites so I have four DCs in the same AD site. Thoughts and references if possible. Many thanks.
WAC opens but will not connect to any servers
I installed WAC into a Win2k19 server, with all the defaults except WinRM was set up as https, not the default. I can add servers, but not connect to any of them. All the servers I put in have PS 5.x and WinRM enabled. I get the following not-so-helpful messages: To perform a single sign-in using your Windows account, you might need to set up Kerberos constrained delegation. -- the above command is supposed to do this, admin center is logged in as essexarc\administrator Error The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig". I tried this: Set-ADComputer -Identity (Get-ADComputer dc1) -PrincipalsAllowedToDelegateToAccount (Get-ADComputer ac1) where ac1 is the WAC server, dc1 is a server I want to manage. Haven't found anything on the interwebs. Thank you, Tom
Windows Admin Center 2410: cannot add computers
After a fresh installation of Windows Admin Center 2410, I cannot add any servers, clusters, PCs etc. WAC gives me "You can add this computer to your list of connections, but we can't confirm it's available" when I enter a computer name (either of FQDN or computer name alone). When I change to the Search Active Directory tab, I get: "We can’t search Active Directory because the Windows Admin Center computer isn’t joined to an Active Directory domain. It’s also possible that your account doesn’t have permission to read from Active Directory." The account I use is a domain admin, and the server running WAC is definitely joined to the AD DS. The server had the previous version of WAC installed where everything worked. Now, with the new version, that's no longer the case...
Issue with existing drive formatted to ReFS and mounting in new server
I had a hardware failure which also took out my Server installation drive. I have new hardware and have installed Server 2022 again on new drive. I have connected a drive that I had formatted as ReFS and now it shows as RAW and Event log shows "ReFS failed to mount the volume. Version 3.14 doesn't match expected value 3.7" I have no idea what is going on here. Both installations of Server 2022 used the same media. This is getting very painful. I have connected the drive to a Windows 11 24H2 computer, and it reads fine.ReFS volume appears as RAW after rebuild of server
I had a Windows 2022 server that had a drive formatted as ReFS. The hardware failed and I had to get a new system. The Windows installation also got corrupted when the hard failed. I have the new hardware and I have installed Server 2022 again but the drive is coming up as Raw and ReFS failed to mount the volume. Version 3.14 doesn't match expected value 3.7 is appearing in the ReFS/Operational event logs. I connected the drive to a Windows 11 Pro pc and are able to view the drive. Why has this happened? Is there a way to upgrade the version of RsFS to 3.7? Is there something I have missed when building the new server?
SMS WinRM DNS error
Hi, I started the cutover, old server was renamed with a new IP, new server was renamed to the OG server with IP it is now frozen at 69% due to WINrm failing due to being unable to resolve the name of the destination server. SVGB-TEST1 —> SVGB-TEST2 SVGB-TEST1(OLD) —> SVGB-TEST1 Failed cannot resolve SVGB-TEST2 (It has been renamed?) Any help appreciated.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 JackServer 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.
PowerShell counterpart for Failover Cluster Manager "Live Migration Settings"
In Failover Cluster Manager, there's "Live Migration Settings" where I can define what cluster networks I want to carry live migration traffic. Even after some research, I cannot find a PowerShell cmdlet that lets me do the same...WSUS Automatic Patch and Reboot in Offline Hours
Hello, I'd like to patch and reboot some of our servers automatically in the offline hours, configured by GPOs. I have managed to get the patches installed and defined a active window. But the servers don't reboot. On issue could be the active window. On the GUI the maximum active window can be max 18h. Is this also valid if you set the window per GPO? As I want to have a very narrow window for the reboots so I need a active window e.g. 22h. Also the start could be ater than the end as I want to cover midnight. E.g. active window starts at 4:00 and ends 2:00 so retarts could be triggered between 2:00 and 4:00 Thanx __LeoServer 2022 WMI Issues
Hi there, I have a Server 2022 with WMI problems affecting the server in a few ways. The server is a domain controller, RD Broker and hosts some files also. The server actually operates ok for the users day-to-day. I discovered the issue when opening AD Connect, getting an Invalid Class error message. When running various fundamental commands at the command prompt (e.g. tasklist) I get the same error. When looking at the WMI Control in Computer Management again - Invalid Class. I have tried various fixes found online such as verifying the WMI repository (it comes back as consistent) but I think I've reached a dead end. I don't want to restore the server from backup as I believe this issue has been ongoing for a couple of months before it was discovered. I can't get in to the Remote Desktop part of server manager to replace the certificate, and the certificate expires next week. Does anyone have any ideas please? Any help greatly appreciated, thanks. ChrisPFN LIST CORRUPT windows server 2016
Hi everyone We’ve recently been experiencing BSOD with the error code PFN_LIST_CORRUPT when using RDP from Apple applications like Jump Desktop or the Windows RDP app. As soon as we log in the servers get the BSOD. We must disable "redirect" in the option "Devices & Audio" in the Windows APP and that works for log in the server and not get the BSOD with that error. This issue occurs only on Windows Server 2016, across multiple servers that are all virtualized on VMware, and spread across different ESXi hosts. Any Idea? Regards,
Compatible Windows Server Hardware Inquiry
Witch Windows server version can take place on HP DL380 Gen9 with Intel Xeon E5-2620V3 / 2.4 GHz ? Previously, I was running Windows Server 2012, but due to the end of technical and service support, I would like to upgrade my software. Please recommend the best version.Hyper-V SMB UNC LocalIP/name avoiding loopback
Hello, I have the following scenario: Two standalone servers joined to a domain (I can't set up a failover cluster at the moment) What I want to achieve is: Access the storage resources via UNC SMB paths in order to perform a storage migration from both nodes \\svhpv1\VMs \\svhpv2\VMs But when I try to have svhpv1 access \\svhpv1\VMs, I get an "Access Denied" error. I believe this error occurs because the access is being attempted through the loopback adapter. I’m experiencing the same issue with svhpv2 when trying to access \\svhpv2\VMs. How can I avoid the loopback so I can properly configure my scenario? Any help is appreciated.
ISSUE - sconfig interface index different / cannot edit static IP
Dear Microsoft Team, I would like to request looking into these issues: 1. Get-Netadapter ifIndex is different in sconfig. Sconfig ifindex do not match an are apparently wrong. this is reproducible. Currently the only way to identify is the InferfaceDescription in sconfig, because ifalias / ifname are missing. I made a FR for these aswell as for VLAN config in previous threads. No reponse on these yet 2. if an adapter has DHCP disabled and a static IP address, sconfig can no longer be used to change the IP adress. There is no option to remove IPAdress and Gateway either. error :-Failed to release DHCP lease, Result Code 83 Please to look into these and my FRs for sconfig. I understand that the point of Artem is that sconfig is not a management rather first settings tool, Yet these basics have to work anyway as inexperienced people would be lost. It is not easy to remediate such state with PowerShell. Especially on Azure Stack HCI and Windows Server Core.
ISO version reporting
Is there a standard way in which the Windows installer ISOs can be interrogated for which version of Windows is on them? This is a bit convoluted so I'll explain the use case. When installing W10 on one of the last generation of x64 Apple Macs, the Boot Camp installer will take the ISO and prepare it by injecting drivers - particularly that for the T2 security chip which handles the first part of the boot process and is the storage controller, among other things. With W10 going out of support (and W11 not really an option due to the hardware requirements) I have been looking at trying to install one ofthe W10-based server versions instead. These are obviously very similar in structure and would probably install and work from a technical standpoint - but if I try it the Boot Camp installer reports that the ISOs aren't Windows 10, and won't proceed. I'm basically looking to clarify whether there is any minor editing of the ISO (or files on it) which can be done to convince Boot Camp that actually this is W10. Anyone know? Thanks
iSCSI Target servers - high availability?
Hello, I have two VMs configured as iSCSI target servers with a 600GB VDHX file on each, and then two VMs configured as file servers in a failover cluster. The iSCSI servers should serve out the data that is shared in the failover cluster file server. I would like to also configure the iSCSI target servers in high availability mode, so that they replicate their data and if one of the iSCSI target server go down, the shares and data is still accessible. How would I go about doing this? So far I've tried setting up storage replica, but since I only have one site, it doesn't allow me to replicate to the second iSCSI disk from the one that currently has data. I also tried iSCSI Target-role in the failover cluster manager, but it puts me back at the same situation where if the storage server with the virtual iSCSI disk goes down, I lose access to all data.NUMA Problems after In-Place Upgrade 2022 to 2025
We have updated several Hyper-V hosts with AMD Milan processors from Windows 2022 to Windows 2025 using the in-place update method. We are encountering an issue where, after starting about half of the virtual machines, the remaining ones fail to start due to a resource shortage error. The host's RAM is about 70% free. We can only get them to start by enabling the "Allow Spanning" configuration, but this reduces performance, and with so many free resources, this shouldn't be happening. Has anyone else experienced something similar? What has changed in 2025 to cause this issue? The error is: Virtual machine 'R*****2' cannot be started on this server. The virtual machine NUMA topology requirements cannot be satisfied by the server NUMA topology. Try to use the server NUMA topology, or enable NUMA spanning. (Virtual machine ID CA*****3-ED0E-4***4-A****C-E01F*********C4). Event ID: 10002 <EventRecordID>41</EventRecordID> <Correlation /> <Execution ProcessID="5524" ThreadID="8744" /> <Channel>Microsoft-Windows-Hyper-V-Compute-Admin</Channel> <Computer>HOST-JLL</Computer>
Events
Meet our Windows Server and Azure engineering leaders and get a look behind the scenes at what's coming next in Windows Server, Azure and hybrid cloud innovations. Speakers: Douglas Phillips, Ian ...
Online
Windows Server 2025 is the easiest to upgrade Windows Server version ever. In this session, Rob Hindman and Jeff Woolsey will discuss media upgrade and features updates in depth. Speakers: Rob Hin...
Online
Recent Blogs
- 11 MIN READIn our tech-savvy age, networks are all the rage 🌐; Joining a domain, though, can sometimes feel like a cage 🖥️. It makes managing PCs a breeze, with security and ease 🔒, But troubleshoo...Apr 22, 2025
- Deploying Windows Server 2025 Clusters with Edge Networking Solutions Part 2: How Network HUD ensures optimal, healthy and smooth Networking operations and health. Welcome to the second blog ...Apr 09, 2025
