Recent Discussions
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). Note that 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 –ResiliencySetttingName Mirror -PhysicalDiskRedundancy 3 -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 –ResiliencySetttingName Mirror -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.
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!Help needed to block Xbox and Game Pass from GPO - Panda Antivirus reported
Good morning, Thank you very much, i am Antonio and i have a Domain Controller and Backup Domain Controller domain forest in Windows Server 2019. I need to completely block everything related to Xbox and all calls to gamepass.com, catalog, gamepass.com, etc. This is because Panda Console is giving me this warning on all domain computers!!! And users are blocked by these warnings! So I'd like to prevent computers from receiving this warning. I can't modify Panda Antivirus, nor can I modify navigation. I'd like to prevent calls to GamePass and Xbox from the various domain clients using enforced methods. Can you please help me? I've already tried a thousand scripts, but they don't work, and the warnings from Panda Console keep coming. Thank you very much. Antonio. Thank you Thank YouIssues 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?
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.
Unable to get Windows Admin Center v2 (2410) to work at all
So I had the old Windows Admin Center installed and working, using Windows Credentials in my domain. There were a few issues with some of the menus that just would not work like they should, but normal updates to Windows Admin Center would fix it for a little while. They release Windows Admin Center v2 and I do an install of that with the old Windows Admin Center still installed. I am able to use the existing cert and could log into Windows Admin Center and see all the machines. Though after the Windows Admin Center v2 install, always got a ajax 500 error, when trying to connect any machine with Windows Admin Center, even the local machine. This past week, uninstall Windows Admin Center off of the Windows 11 computer that I had been using, both the v2 and v1 versions of it. I then reboot and install the Windows Admin Center v2, using custom setup. Prior to this I went into certificates on the computer and requested a web server cert for this computer using the name of the computer in DNS. My AD CS provided the new cert and I installed it as a computer certificate, under personal. Afterwards I then assigned Network Service full control of the certificate. I selected that certificate during the Windows Admin Center v2 setup and selected Windows authentication, and left everything else as default. Windows Admin Center installs and I launch it, I get to the prompt for username and password from Windows, enter the correct domain credentials and it repeatedly loops through. I went 17 tries and was never able to get into Windows Admin Center. Never got anything saying that I couldn't login, just repeatedly ask for the credentials. So how do I get this blasted thing to work? Uninstall it again, install the Windows Admin Center v1 then the v2 and try and deal with the ajax 500 issue? Nuke the entire computer and install it from a fresh Windows 11 install? Or just give up and always use remote desktop to manage all the servers, which Windows Admin Center v1 helped me half avoid?
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!Workgroup Failover Cluster backup service account
Hello, We have built a workgroup Hyper-V cluster. Live migration works well when taking a node. But the only account that we can use is the one used at the cluster creation. I found some post about account creating the same user / password on both node and grant cluster full access. But this account gets access denied in the cluster manager. But I would like to have specific account for backup and also a nominative account for administration. I just read Orin Thomas post , but it did not help. Have someone ever be able to use a different local local account to manager a workgroup cluster ? Or to achieve this need, I must stick to AD registered servers. Thanks for any help. Jean MarieVirtualization-Based Security (VBS): Elevating Modern IT Protection
In the rapidly evolving world of cybersecurity, traditional approaches to protecting operating systems are being continuously challenged by increasingly sophisticated threats. Cyber attackers now target the very core of our computing environments, seeking privileged access that can bypass conventional defenses. In this context, Virtualization-Based Security (VBS) emerges as a transformative solution, leveraging hardware virtualization to create robust isolation for critical system processes. What Is Virtualization-Based Security? VBS is a security feature integrated into modern Windows operating systems. It utilizes hardware virtualization to establish a virtual secure mode—an isolated environment that runs sensitive security tasks, shielded from the main operating system. Even if malware compromises the OS, this isolated environment prevents unauthorized access to protected processes and data. At its foundation, VBS operates through a lightweight hypervisor, enforcing strict security boundaries. This architecture ensures that, even if an attacker gains administrative rights within the operating system, vital security assets remain inaccessible. Core Benefits of VBS Credential Protection With Credential Guard, VBS stores sensitive credentials—such as NTLM hashes and Kerberos tickets—in a secure container. This strategy effectively blocks tools like Mimikatz from extracting credentials, significantly reducing the risk of lateral movement attacks. Kernel-Level Code Integrity Hypervisor-Enforced Code Integrity (HVCI) ensures that only approved, digitally signed drivers and binaries can execute at the kernel level. This defends against rootkits and kernel-level malware. Zero-Day Exploit Mitigation By isolating mission-critical processes, VBS minimizes the attack surface and lessens the impact of previously unknown vulnerabilities. Secure Boot Synergy VBS complements Secure Boot, ensuring the device loads only trusted software at startup and preventing bootkits and early-stage malware. Enhanced Compliance and Assurance Organizations in regulated industries—such as finance and healthcare—benefit from VBS’s robust controls, which support regulatory compliance and increase stakeholder confidence in IT security measures. System Requirements for Deploying VBS To implement VBS, ensure the following prerequisites are met: Windows 10/11 Enterprise, Pro, or Education editions 64-bit architecture UEFI firmware with Secure Boot capability enabled Hardware virtualization support (Intel VT-x or AMD-V) TPM 2.0 (Trusted Platform Module) for Credential Guard functionality Adequate RAM (VBS may slightly increase memory consumption) Practical Applications: Challenges Addressed by VBS Enterprise Credential Protection: Prevents credential theft and lateral movement across networks. Driver Vulnerability Defense: Blocks unauthorized or malicious drivers from executing. Mitigating Insider Threats: Restricts access to sensitive processes, even for users with administrative rights. Combating Advanced Persistent Threats (APTs): Provides a hardened layer of defense that significantly complicates APT infiltration efforts. VBS: Transforming Security for IT Professionals and Organizations For IT Professionals: Stronger Security Posture: Defense-in-depth with minimal complexity Streamlined Compliance: Simplifies adherence to standards such as NIST, ISO 27001, and HIPAA Future-Ready Infrastructure: Lays the groundwork for secure hybrid and cloud environments For Businesses: Lowered Breach Risks: Reduces the likelihood and impact of data breaches or ransomware incidents Increased Trust: Demonstrates robust security practices to clients and business partners Business Continuity: Safeguards critical systems, ensuring operational resilience Conclusion Virtualization-Based Security represents more than just another operating system feature—it marks a paradigm shift in how organizations and IT professionals approach endpoint protection. By isolating and safeguarding the most sensitive components of the OS, VBS empowers businesses to stay ahead of evolving threats and secure their digital assets with confidence. Whether you are an IT administrator, a security architect, or a business leader, adopting VBS is a strategic decision that paves the way toward a safer, more resilient future in the Microsoft ecosystem.In-place upgrade possibility planned for Windows Server 2025 Datacenter Azure Edition ?
There is currently no official ISO for Windows Server Datacenter: Azure Edition that supports setup.exe /auto upgrade for in-place upgrades. Azure Update Manager does not support OS version upgrades for Azure Edition through optional features. Is anyone aware of a supported workaround?Remote Access via HTTPS RDP Web Client on Windows Server 2022 - Installation Issue Solved .
Step 1: Install Remote Desktop Services** * Install the **Remote Desktop Services** role using (note role and feature installation) * Choose **Quick Start** for the deployment type. * Select **RD Connection Broker** as the default server. * Choose **Session-based desktop deployment**. > *Note: If you need a virtual machine–based environment, ensure Hyper-V or another virtualization platform is installed on the server.* * The following roles will be installed automatically: * Remote Desktop Session Host * Remote Desktop Gateway * Remote Desktop Licensing * Remote Desktop Web Access --- Step 2: Configure Core RDS Components** Configure all the following roles on the **same server** (or on different servers if desired): * RD Connection Broker * RD Gateway * RD Licensing * RD Web Access Use a **domain user** account that has administrative privileges (Domain Administrator or Server Administrator group). --- Step 3: Configure Certificates** * Open **Server Manager** → **Remote Desktop Services** → **Deployment Overview**. * Click **Tasks** → **Edit Deployment Properties**. * Under **Certificates**, create a **self-signed certificate** and apply it to all roles: * RD Connection Broker * RD Gateway * RD Licensing * RD Web Access > Make sure all roles use the **same certificate**. --- Step 4: Configure RD Gateway Policies** * Go to **Tools** → **Remote Desktop Services** → **RD Gateway Manager**. * Create a policy for: * **User authentication** * **Network access** > Allow only ports **443** (HTTPS) and **3389** (RDP). --- Step 5: Configure Quick Session Collection** * If a collection is not created automatically, create one by: * Navigating to **Server Manager** → **Remote Desktop Services** → **Collections**. * Choose the same server and create a new **QuickSessionCollection**. * Under **RemoteApp Programs**, add and publish the desired programs. * Check accessibility by browsing to: `https://<your‑FQDN>/RDWeb/` --- Access via Web Only (Web Client Setup) -------------------------------------------------------------------- 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.
Windows Server update keeps promptiing to install
Hi, We have a 2019 DC server that keeps prompting to install / restart windows update. I have done clicking the "install", "check for updates" and "restart" button multiple times already but everytime it comes back online, the update is still there. When I check the history it looks like this: Troubleshooting steps I did are: 1.) -Run windows update troubleshooter - couldn’t find any problem 2.) net stop wuauserv net stop cryptSvc net stop bits net stop msiserver ren C:\Windows\SoftwareDistribution SoftwareDistribution.old ren C:\Windows\System32\catroot2 catroot2.old net start wuauserv net start cryptSvc net start bits net start msiserver I am stuck and appreciate any help resolving this issue. Regards, Mina[msft.sme.remote-desktop v4.30.2] RDP extension fails to load in WAC 2.4.1
Description Product: Windows Admin Center v2.4.1 Extension: Connect to a server or PC via Remote Desktop ID: msft.sme.remote-desktop Version: 4.30.2 Authors: Microsoft License: MIT Issue: When attempting to launch the Remote Desktop extension, the UI never renders (infinite spinner) and the browser console reports: Uncaught SyntaxError: Unexpected token '<' In addition, certain .js module requests return HTTP 403, and the loader falls back to “null” instead of the correct main.<hash>.js. Steps to Reproduce: Install or enable the msft.sme.remote-desktop extension (v4.30.2) on WAC 2.4.1. Open WAC in a modern browser and navigate to Remote Desktop. Press F12 → Console and Network tabs. Observe: The <base href="/modules/msft.sme.remote-desktop/"> page loads, but subsequent scripts (main.<hash>.js) resolve to “null” or return 403. Console errors Unexpected token '<' Remote Desktop never initializes. Expected Behavior: The RDP extension UI should load normally, register its translation tables, and allow launching a remote session without syntax or module‐loading errors. Impact: Cannot use the built-in Remote Desktop tool within Windows Admin Center. Work-around: deinstalling the remote desktop v4.30.2 and reinstalling the old version v4.26.0 until the problem is resolved in the newer version
