Vue normale

Il y a de nouveaux articles disponibles, cliquez pour rafraîchir la page.
À partir d’avant-hierFlux principal

Microsoft to disable NTLM by default in Windows

Par : IT Experts
2 février 2026 à 15:46
Disable NTLM in Windows Server 2025 using Group Policy
Microsoft announced a comprehensive roadmap to phase out the legacy NTLM (New Technology LAN Manager) authentication protocol in favor of more secure Kerberos-based alternatives. The company plans to disable NTLM by default in the next major Windows Server release and associated Windows client versions, marking a significant step toward enhancing Windows security after more than three decades of NTLM usage.

Source

S2D and SAN coexistence in Windows Server failover clustering for Hyper‑V, SQL Server, and file services

Par : IT Experts
29 décembre 2025 à 16:45
Organizations running modern data centers increasingly need flexible storage architectures that balance performance, resiliency, and investment protection. With Windows Server 2022 and Windows Server 2025, Microsoft now enables true S2D and SAN coexistence—allowing Storage Spaces Direct (S2D) to operate alongside traditional SAN storage within the same failover clustering environment. This mixed-storage approach lets IT teams optimize workloads such as Hyper-V, SQL Server, and file services by combining high-performance local storage with existing enterprise SAN infrastructure, all while maintaining full cluster support and operational consistency.

Source

Windows 11 : les mises à jour de décembre 2025 cassent les connexions RemoteApp

21 décembre 2025 à 18:45

Microsoft a révélé un bug pouvant entraîner des échecs de connexion RemoteApp sur Windows 11 et Windows Server 2025, avec les mises à jour de décembre 2025.

Le post Windows 11 : les mises à jour de décembre 2025 cassent les connexions RemoteApp a été publié sur IT-Connect.

Windows Server 2025 introduces native NVMe support with performance gains of up to 80 percent

Par : IT Experts
17 décembre 2025 à 16:10
Microsoft has released native Non-Volatile Memory Express (NVMe) support for Windows Server 2025, delivering performance improvements of up to 80 percent in IOPS and delivering a 45 percent savings in CPU cycles per I/O compared to Windows Server 2022.

Source

Migrate WSUS: Install role and move data to Windows Server 2025

Par : Leos Marek
14 novembre 2025 à 13:23
This guide walks you through the process of installing the WSUS (Windows Server Update Services) role and migrating your configuration and data to Windows Server 2025. You'll perform a clean setup to ensure a stable, efficient patch management environment on the latest Windows Server release. Follow these steps to safely move WSUS settings, groups, and approvals, and prepare your system for long-term support.

Source

Windows Server 2025 WSUS blocks ESU updates

Par : IT Experts
17 octobre 2025 à 17:20
Windows Server 2025 implements security hardening changes that block WSUS from distributing extended security updates (ESU) to end-of-life operating systems. The modifications affect Windows Server 2012 and 2012 R2 systems receiving ESU updates through WSUS, requiring administrators to implement workarounds or upgrade their infrastructure.

Source

Install Linux Subsystem for Windows (WSL) on Windows Server 2025

15 octobre 2025 à 18:02
This article explains the differences between WSL 1 and WSL 2, how they compare to WSL on Windows Server 2022 and Windows Server 2025, and how to install WSL on Windows Server 2025 using the graphical user interface (GUI) or PowerShell.

Source

AD replication error 8418: The replication operation failed because of a schema mismatch between the servers involved

Par : IT Experts
13 octobre 2025 à 18:22
Active Directory domain controllers running Windows Server 2025 with the schema master FSMO role may create duplicate schema attribute values when performing Exchange Server schema extensions, causing replication failures across the entire forest. This issue triggers this error message: Error 8418: The replication operation failed because of a schema mismatch between the servers involved. The issue affects environments attempting to deploy Exchange Server cumulative updates or Exchange Server Subscription Edition. Microsoft has acknowledged this as a known issue in KB5065426.

Source

❌
❌