Recent Discussions
Demoting 2016 server problems
I am trying to demote a Windows 2016 server and am running into errors. I am using a Domain Admin account. The error that comes up is that the domain cannot be reached which is strange, considering that all DCs are reachable from this server. It is not running a GC and the DNS server on it has been removed. This is a relatively small domain with only three DCs. We are demoting this one so that we can add a new Windows 2022 DC and eventually 2025 DCs. We have two sites: Office and Datacenter. There are two DCs at Office and one at Datacenter. Going forward we will be removing one of the office DCs and adding a second one at Datacenter. Let's call these servers: Server Alpha, 172.16.1.1, Datacenter Server Bravo, 172.17.1.1, Office (this is the server to be removed) Server Charlie, 172.17.1.2, Office When I run the command: dcdiag /test:dns /DnsRecordRegistration on each of these servers I get the following: Server Alpha: Success, no errors Server Bravo: Success, no errors Server Charlie: DNS error, points to very old IP (172.20.1.1) that Server Bravo used to have when it was at an older, DR datacenter. The error is: "PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 172.20.1.1" We do still have the reverse DNS zone for that subnet however neither of the other two servers have this problem. Also I cannot find any other entries for that IP address anywhere. What am I missing?
VMXnet3 Server 2025 performance issues
Had an odd one crop up today. I updated my Server 2025 template to the 26063.1 release and then sysprepped it. Converted it back to a new VM and network performance was .25 Mbps down. Both on my local lan and on the internet. I removed the VMXnet3 and put in an E1000 and performance was exactly as expected. I shut the VM down, removed the E1000 put in a new network with vmxnet3 and again got horrible performance. I have not seen this with other deployments of 2025 earlier builds.
Storage Migration Service fails at 18% from server 2016 to server 2022
Hi, we have setup a storage migration from a physical server 2016 to physical server 2022. This fails at 18%, the validation passes and transfer starts but then stops at 18% I have downloaded the "proxy admin" and "Storage migration service admin" event logs from the storage migration service in admin center.
Announcing Windows Server vNext Preview Build 26445
Announcing Windows Server vNext Preview Build 26445 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, Annual Channel for Container Host 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 [NEW] Rack Level Nested Mirror (RLNM) for S2D Campus Cluster Rack Level Nested Mirror (RLNM) for S2D Campus Cluster enables customers to meet NIS2 two data room requirements for their factories by providing fast and resilient storage using Storage Spaces Direct (S2D). For S2D Campus Cluster, we recommend using all-flash storage (SSD or NVMe drives), all capacity (no cache drives), and RDMA NICs (iWARP, RoCE, or InfiniBand). Note: Rack fault domains must be created on the cluster in order to use this feature – a new cluster must be created: #Create a test cluster but do not create storage: New-Cluster -Name TestCluster -Node Node1, Node2, Node3, Node4 -NoStorage #Define the fault domains for the cluster – two nodes are in “Room1” and two nodes are in “Room2”: Set-ClusterFaultDomain -XML @”<Topology><Site Name=”Redmond”><Rack Name=”Room1”><Node Name=”Node1”/><Node Name=”Node2”/></Rack><Rack Name=”Room2”><Node Name=”Node3”/> <Node Name=”Node4”/></Rack></Site></Topology>”@ #Add Storage Spaces Direct (S2D) Storage to the cluster – note that Enable-ClusterS2D cmdlet can also be used: Enable-ClusterStorageSpacesDirect #Update the Storage Pool Update-StoragePool #Check that the StoragePool version is 29: (Get-CimInstance -Namespace root/microsoft/windows/storage -ClassName MSFT_StoragePool -Filter 'IsPrimordial = false').CimInstanceProperties['Version'].Value #Check that the Storage Pool’s FaultDomainAwareness property is set to StorageRack: Get-storagepool -FriendlyName <S2DStoragePool> | fl #Note that resiliency is specified when the volume is created – our idea with the S2D Campus cluster is that customers can create both four-copy and two-copy volumes - valuable workload (VMs) and data should go on the 4-copy volumes. #Create a four-copy volume on the storage pool, fixed provisioned: New-Volume -FriendlyName “FourCopyVolumeFixed” -StoragePoolFriendlyName S2D* -FileSystem CSVFS_ReFS –Size 500GB -ResiliencySettingName Mirror -PhysicalDiskRedundancy 3 -ProvisioningType Fixed -NumberOfDataCopies 4 –NumberOfColumns 3 #Optional - Create a four-copy volume on the storage pool, thinly provisioned: New-Volume -FriendlyName “FourCopyVolumeThin” -StoragePoolFriendlyName S2D* -FileSystem CSVFS_ReFS –Size 500GB -ResiliencySettingName Mirror -PhysicalDiskRedundancy 3 –ProvisioningType Thin -NumberOfDataCopies 4 –NumberOfColumns 3 #Optional - Create a two-copy volume on the storage pool, fixed provisioned: New-Volume -FriendlyName “TwoCopyVolumeFixed” -StoragePoolFriendlyName S2D* -FileSystem CSVFS_ReFS –Size 500GB -ResiliencySettingName Mirror -PhysicalDiskRedundancy 1 -ProvisioningType Fixed #Optional - Create a two-copy volume on the storage pool, thinly provisioned: New-Volume -FriendlyName “TwoCopyVolumeThin” -StoragePoolFriendlyName S2D* -FileSystem CSVFS_ReFS –Size 500GB -ResiliencySettingName Mirror -PhysicalDiskRedundancy 1 -ProvisioningType Thin Windows Server Flighting is here!! If you signed up for Server Flighting, you should receive this new build automatically 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, 2025. 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.
Active Directory documentation and best practices
Dear all, please, I have to fix a critical situation. I have recovered a DC VM on an old Hyper-V host. This DC is corrupted and seems that it is not working as well. I installed 2 new phisical host (cluster) with Windows Server Datacenter 2025, configured Hyper-V role, networks etc.. Also prepared (out of cluster) 2 new VM Win 2025 and I would like to prepare as new DC01 + DC02. I guess is better to configure the DC on the hosts to grant that the DC role is always available also if the cluster is not running (feel free to correct if I'm wrong, I will appreciate). I need link to video or documents to correctly perform the configuration of the new DC. The old DC are running a Windows Server 2012 R2 standard version. Is it possible to migrate to Windows 2025 datacenter ? Take note that at the end I have to assign to the new DC, the same IP address. thank you very much for your support. BR Alex.
Windows Server 2016 and internet issues
Hello everyone, I'm relatively new here and hoping for some help. I'm IT at a school in Manhattan that has an old Dell tower running Windows Server 2016 in the basement that is not in use any more with the school as they have transferred over everything to digital. This was set up before my time working here and the person who set it up unfortunately did not leave any notes. We are ready to disconnect the machine as all of it's functions have been moved elsewhere. But, every time it is turned off or disconnected from our network patch, the internet in the entire building goes dead. I do not have previous experience with these kinds of servers and am trying to figure out what could possibly be causing this. I am concerned because the machine is old and feels like it's being held together by duct tape, and if it goes down, I hoping internet doesn't go with it. Looking for any advice or knowledge about these servers and what I can try to do to disconnect it.Hyper‑V SET Loop Risk, Asymmetric Paths & Active‑Standby (ALE OXE VM Offline)
Hi everyone, Environment - Windows Server 2025 Hyper‑V - One external virtual switch - Physical NICs combined with Switch Embedded Teaming (SET) - One VM: Alcatel‑Lucent Enterprise OmniPCX Enterprise (OXE) Questions → 1) Loop prevention → 2) Asymmetric traffic → 3) Active‑Standby Problem The OXE VM intermittently becomes unreachable (no ICMP, no SIP). Hyper‑V shows it as “Running,” CPU is low, guest logs are clean. Rebooting the VM or toggling the SET team restores connectivity. Looking for advice on: - Loop‑prevention mechanisms in Hyper‑V SET - How inbound vs outbound flows are balanced - Whether Active‑Standby is possible and how to configure it - Diagnostics to confirm if asymmetric paths or loops are causing the outage Thanks in advance!WAC over WinRM HTTPS for non-domain-joined Devices
When configuring Windows Admin Center to use WinRM over HTTPS, it's not possible to add non-domain-joined devices (such as Windows Server 2025) if UAC remote restrictions are enabled on the target machine. Adding a device using a local account with administrator permissions fails with the error "Credentials needed - Access was denied". The self-signed certificate of the remote machine is present in the trusted root store and remote PowerShell over WinRM HTTPS is also working but the only workaround is to disable remote UAC entirely which brings a security risk. GPO Computer Configuration -> Administrative Templates -> MS Security Guide -> Apply UAC restrictions to local accounts on network logons Registry HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\LocalAccountTokenFilterPolicy = 1 Is there a way to overcome this ?Announcing Windows Server vNext Preview Build 26454
Announcing Windows Server vNext Preview Build 26454 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, Annual Channel for Container Host 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 Rack Level Nested Mirror (RLNM) for S2D Campus Cluster Rack Level Nested Mirror (RLNM) for S2D Campus Cluster enables customers to meet NIS2 two data room requirements for their factories by providing fast and resilient storage using Storage Spaces Direct (S2D). For S2D Campus Cluster, we recommend using all-flash storage (SSD or NVMe drives), all capacity (no cache drives), and RDMA NICs (iWARP, RoCE, or InfiniBand). Note: Rack fault domains must be created on the cluster in order to use this feature – a new cluster must be created: #Create a test cluster but do not create storage: New-Cluster -Name TestCluster -Node Node1, Node2, Node3, Node4 -NoStorage #Define the fault domains for the cluster – two nodes are in “Room1” and two nodes are in “Room2”: Set-ClusterFaultDomain -XML @”<Topology><Site Name=”Redmond”><Rack Name=”Room1”><Node Name=”Node1”/><Node Name=”Node2”/></Rack><Rack Name=”Room2”><Node Name=”Node3”/> <Node Name=”Node4”/></Rack></Site></Topology>”@ #Add Storage Spaces Direct (S2D) Storage to the cluster – note that Enable-ClusterS2D cmdlet can also be used: Enable-ClusterStorageSpacesDirect #Check that the Storage Pool’s FaultDomainAwareness property is set to StorageRack: Get-storagepool -FriendlyName <S2DStoragePool> | fl #Create a four-copy volume on the storage pool: New-Volume -FriendlyName “FourCopyVolume” -StoragePoolFriendlyName S2D* -FileSystem CSVFS_ReFS –Size 500GB -PhysicalDiskRedundancy 3 -ProvisioningType Fixed -NumberOfDataCopies 4 –NumberOfColumns 3 #Create a four-copy volume on the storage pool, thinly provisioned: New-Volume -FriendlyName “FourCopyVolume” -StoragePoolFriendlyName S2D* -FileSystem CSVFS_ReFS –Size 500GB -PhysicalDiskRedundancy 3 –ProvisioningType Thin -NumberOfDataCopies 4 –NumberOfColumns 3 Windows Server Flighting is here!! If you signed up for Server Flighting, you should receive this new build automatically 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, 2025. 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.
Bloqueado por 2FA sin solución ni acceso a licencias Windows Server 2022 Standard
He perdido el dispositivo donde tenía configurado el segundo factor de autenticación (Microsoft Authenticator) para mi cuenta email address removed for privacy reasons. La cuenta está completamente bloqueada y no puedo acceder al portal de administración. Compré licencias perpetuas de Windows Server 2022 Standard (16 cores) a través de BEcomit, distribuidas por Arrow, y tengo la factura oficial como prueba de propiedad. He intentado: Contactar con BEcomit (no tienen acceso delegado ni pueden ayudar) Llamar al soporte técnico de Microsoft España en varios números Usar formularios de recuperación y portales de ayuda En todos los casos se me exige contratar un plan de soporte adicional, incluso cuando solo intento recuperar acceso a una cuenta bloqueada por 2FA. Esto está afectando seriamente mi actividad profesional. Solo necesito que se verifique mi propiedad para recuperar el acceso o transferir las licencias a otra cuenta. Si alguien de Microsoft o del ecosistema de partners ha vivido algo similar o puede ayudar a escalar este caso, lo agradecería muchísimo. 🙏 Adjunto factura si se requiere por privado.Users "Status" fields blank on RDS with Windows Server 2025
Hi, we have two RDS Server with Windows Server 2025 installed (In-Place Upgrade from Server 2019). In Task-Manager under the "Users" Tab all fields of the "Status" row are blank. We cant see if a user is connected or disconnected. In cmd with "query user" it works. Someone else discovered this problem?Issues with server on domain
So we are having an odd problem with intermittent connectivity on Windows server 2022 install. It's a repository server, that is also used for dev work so at any one time we have users connected to it from different groups in the US, as well as outside the US (India & Australia). It is located on on our US domain, and users connect using their AD credentials. The problem we are seeing is that users outside the US can't connect to the system randomly, but most of the time users in the US can. However occasionally they have issues too so it's random. So far we have tried the following to address it, but are still seeing problems: - We've tried removing and rejoining the domain. - DNS settings are correct, and are the same as other WS2022 (and 2016 servers) that are also on the domain. - We are using a corporate NTP server, which is also used by the corporate DC's. - Firewalls aren't blocking traffic. - Most recently about 3 weeks ago I did see some GPO errors, so did do a GPO update. This seemed to help until this past Friday when the issue occurred. - We are fairly thorough with maintenance as we have a monthly window after MS patch Thursday to update and reboot the system at least once a month. We have a secondary site where this system is replicated, and both of of the vm's were made from the same template...but this system doesn't have the same issues. Any ideas on what we could be missing or what to look at next?Does GPO "Install updates for other Microsoft Products" still work on Server 2019?
We've configured Automatic Updates (option 4 - auto download and install) on a server that has SQL Server installed. The option Install updates for other Microsoft products is disabled. We've also set the Microsoft update service location to our internal WSUS server. To confirm, I pulled a RSOP report, as shown below. Now this server has a SQL Server security updates pending for installation, and during the last scheduled update run, an update installation for SQL Management Studio was started, but eventually failed. In my understanding, these are other Microsoft Products and should not be downloaded and installed by Windows Auto Update. But they were and are. Side note, because the Microsoft Support Premiere engineer I'm working with on this case thought this was important: The two SQL updates are approved in WSUS, because we do have SQL servers where we'd like to have them offered for installation. But in my understanding, this should only offer these updates and the Update Agent should then decide based on the setting, whether or not to install updates for other Microsoft products. I do not agree with the support engineer, that the WSUS approval is responsible for the installation of that update. Can someone exactly explain, how the update agent works in this case? Or better, why the update agent does install updates for other Microsoft products, although I did not enable that?DHCP Failover Issue – Standby Server Responding When It Should Not
Hi everyone, I'm encountering an issue with my DHCP failover setup in Hot Standby mode, and I need insights into why the standby server is providing DHCP leases when it shouldn’t. Setup Overview: I manage a network with over 100 sites worldwide, each having a local DHCP server. Each site has a dedicated DHCP server running on the server VLAN. Clients reside on different VLANs, and IP helpers (DHCP relay) are configured on a Checkpoint firewall at each site. The IP helper forwards DHCP requests to: The local DHCP server (primary) in the site's server VLAN. The standby DHCP server (failover), located at an on-premises data center (DC). DHCP servers are configured in Hot Standby mode using Microsoft DHCP Failover. Issue: Despite the Hot Standby configuration, I noticed that my Cisco Meraki dashboard frequently reports a new DHCP server detected, referring to the standby DHCP server, even though the primary DHCP server at the local site is available. Cisco Meraki triggers this alert when it detects DHCPACK packets from the standby DHCP server traversing the local networks. However, in Hot Standby mode, the failover server should only issue leases if the primary server is unreachable. Example: Site-1's primary DHCP server (DHCP-1) has a failover partnership with Failover-1 at the DC. Site-1's connectivity to the DC is stable, yet Cisco Meraki occasionally detects DHCPACK packets from Failover-1, triggering alerts. Troubleshooting Done So Far: Verified that failover mode is correctly set to Hot Standby (not Load Balance). Confirmed that the primary DHCP server is healthy and responding. Checked DHCP logs on both servers but found no clear failover events. Performed packet captures of DHCP traffic, but the results were inconclusive. Investigated whether Checkpoint firewall’s IP helper can prioritize the primary DHCP server, but it appears not to support this functionality. Created a PowerShell script to check for failover-related event logs (Event IDs: 20254 and 20255). This provided better visibility but did not correlate with the Meraki alerts. Questions: Are there any known scenarios where a standby DHCP server in Hot Standby mode might mistakenly issue leases, even when the primary is active? Is there any detailed information on the failover “heartbeat” mechanism between primary and standby servers? I found that it uses TCP port 647, but I couldn’t locate official documentation on the interval and failure conditions. Could failover state synchronization delays cause this behavior? Are there specific logs or PowerShell commands I should check to confirm why the standby server is responding? Is there a way to prevent the standby server from responding unless the primary is truly unreachable (e.g., registry settings, advanced configuration)? Any guidance or troubleshooting steps would be greatly appreciated! Thanks in advance.W2K19 vss issue
Hello, I'm looking for some troubleshooting suggestions for a 2019 Server that is experiencing vss issues. Yesterday I had a backup fail with a VSS error. Failed: Failed - 0x80042306 - IDispatch error #8454 - Retrying without VSS Writers ERROR: COM call "m_pVssObject->BackupComplete(&pAsync)" failed. - Returned HRESULT = 0x80042301 - Error text: VSS_E_BAD_STATE After some further troubleshooting I realised that the VSS issue extended beyond the backup system C:\windows\System32>vssadmin list writers vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool (C) Copyright 2001-2013 Microsoft Corp. Writer name: 'Task Scheduler Writer' Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124} Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b} State: [1] Stable Last error: No error Writer name: 'VSS Metadata Store Writer' Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06} Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93} State: [1] Stable Last error: No error Writer name: 'Performance Counters Writer' Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2} Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381} State: [1] Stable Last error: No error Writer name: 'System Writer' Writer Id: {e8132975-6f93-4464-a53e-1050253ae220} Writer Instance Id: {4a4003f5-e11d-4f99-8071-e8a74259dfb3} State: [1] Stable Last error: No error Writer name: 'ASR Writer' Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4} Writer Instance Id: {7254596f-d6ee-4268-b16b-0ac353af5af6} State: [1] Stable Last error: No error Writer name: 'Shadow Copy Optimization Writer' Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f} Writer Instance Id: {6704e612-a914-4db9-81da-fe66b9a63684} State: [1] Stable Last error: No error Writer name: 'Microsoft Hyper-V VSS Writer' Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de} Writer Instance Id: {d4e0e02d-d932-424c-8708-976037c2fc5f} State: [7] Failed Last error: Timed out Writer name: 'Registry Writer' Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485} Writer Instance Id: {faf20311-d7ae-446d-b82b-f73f3c94a91b} State: [1] Stable Last error: No error Writer name: 'COM+ REGDB Writer' Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f} Writer Instance Id: {62ce4679-7634-423c-b549-efd60969679e} State: [1] Stable Last error: No error Writer name: 'BITS Writer' Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0} Writer Instance Id: {bd78bd8d-0bcb-4143-9494-1f94aaa9412e} State: [1] Stable Last error: No error Writer name: 'IIS Config Writer' Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6} Writer Instance Id: {cabe2719-7881-4a17-a306-b91bf55a0ca7} State: [7] Failed Last error: Timed out Writer name: 'WMI Writer' Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0} Writer Instance Id: {327e2198-51e5-418f-857b-807592618509} State: [7] Failed Last error: Timed out Writer name: 'Certificate Authority' Writer Id: {6f5b15b5-da24-4d88-b737-63063e3a1f86} Writer Instance Id: {53ff0a16-053f-4b4a-a670-63dbf07f0cd0} State: [7] Failed Last error: Timed out Writer name: 'DFS Replication service writer' Writer Id: {2707761b-2324-473d-88eb-eb007a359533} Writer Instance Id: {f7b764bc-f504-4542-b423-2b2436c3c373} State: [1] Stable Last error: No error Writer name: 'NTDS' Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757} Writer Instance Id: {2c66a49d-efd6-41a7-a35b-ce3362000b2a} State: [7] Failed Last error: Timed out Writer name: 'Dhcp Jet Writer' Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad} Writer Instance Id: {de15b14a-bcf4-41b9-bdf0-76af8edaee68} State: [7] Failed Last error: Timed out Writer name: 'WINS Jet Writer' Writer Id: {f08c1483-8407-4a26-8c26-6c267a629741} Writer Instance Id: {05ee1245-8ad7-4486-9845-3d83bb443557} State: [7] Failed Last error: Timed out I have done the following: chkdsk /f on all volumes dism /online /cleanup-image /checkhealth dism /online /cleanup-image /scanhealth dism /online /cleanup-image /restorehealth sfc /scannow no errors reported After the above: vssadmin list writers reported no errors and the backup completed normally. So I thought that the issue was resolved. Today the backup failed again and vssadmin list writers is as above again. I can't see anything in the Event Log (System or Application) that looks to be relevant. At this stage the only idea that I have is to restore the server back to prior to the errors commencing, but this is a DC in a multi-DC environment, so that is not a trivial step. I'd prefer to try and resolve the issue directly if I can. Thanks VWThe TLS connection request has failed.
We are in the process of configuring a new SharePoint 2016 on-premises Farm using Azure VMs. The App and WFE run on Windows 2019 R2. The SQL DB is Windows 2022 running in CM 110. All DataCenter editions The farm is not completely configured and is not having traffic yet. I am seeing the following event (id 36874) in our Event Viewer An TLS 1.2 connection request was received from a remote client application, but none of the cipher suites supported by the client application are supported by the server. The TLS connection request has failed. The servers were setup by another team so I'm not sure on what all they did to prepare them and I am not a Sysadmin by training or experience, but I can try and answer questions you may have. Could there be something missing in the setup of these servers that will prepare them for TLS communication? Is this an issue with having different ciphers available to each server due to different OS and not being able to agree on one? I verified that there are ciphers available on the DB that are in common with the ones on our SP Servers, which are in the same order on each server and should be usable. This is why I'm wondering if TLS has to be eabled or tuned on in some way when newly installing these or perhaps I'm missing something? THese are normal messages? Thank you!
Run As Administrator not always working?
I have dealt with this for about 10 years now since Server 2003/Windows XP. Just now getting around to addressing this. If this isn't the right place, I'd appreciate a link to the right place. Have a Server 2019 domain with 13 workstations all running Windows 11 Pro. Workstation user only have user access rights. On occasion I'll need to run something, such as services.msc for example with admin rights. On some workstations I can right-click services, select Run As Administrator, enter the domain admin credentials and can then stop/start/change services as needed. Yet on other workstations the Run As Administrator doesn't work. It runs services.msc. But I'm not prompted for admin credentials and can't start/stop/change the service. What can I do to make it work so I don't have to waste time logging of the normal user to log in with a domain admin account? Note that I do have and use group policies on the server. I've never "knowingly" set any policy that would prevent the Run As Administrator for working. I also have WSUS set up and it's configured with SSL if that matters. Thanks for any feedback on this. - CarlWindows 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!
Recent Blogs
- Welcome to part three of our Networking Deployment Series for Windows Server 2025. In this deployment series, we look at Contoso Medical Center’s journey deploying and harnessing the power of Windows...Jul 28, 2025
- 3 MIN READEffective July 16, 2025, Hotpatching for Windows Server 2025 on Azure Arc–connected machines will be generally available (GA) and transition to a paid subscription model. This post provides technical...Jul 16, 2025
