Posts

Configuration Based SQL Server FCI Action On A Windows Server Failover Cluster

Configuration Based SQL Server FCI Action On A Windows Server Failover Cluster.md This document targets Windows Server 2022, Windows Server 2025, SQL Server 2022, and SQL Server 2025. This document presumes that you store your SQL Server installation media, service packs, configuration files, and scripts on a UNC path. Table of Contents Table of Contents Requirements Cluster Node First-Time Configuration SQL Server FCI Mount Point, Folder, and File Configuration SQL Server FCI Action: InstallFailoverCluster, AddNode, RemoveNode Windows Server 2025/SQL Server 2025 Notes Update Notes Requirements Before you install a SQL Server Failover Cluster Instance (FCI) on a Windows Server Failover Cluster (WSFC), review the Active Directory, DNS, and storage requirements. See Requirements for SQL Server AlwaysOn Feature on a Windows Server Failover Cluster.md . Cluster Node First-Time Configuration Use the steps below to configure a WSFC cluster node for first-time ...

Remote PowerShell Without “Second Hop” Problem

Remote PowerShell.md This document targets Windows Server 2022 and Windows Server 2025. Table of Contents Table of Contents Overview Windows Server 2022/2025 Administration Host and PowerShell Remote PowerShell Using CredSSP Reuse a Credential Across Multiple Sessions Remote PowerShell Using Resource-Based Kerberos Constrained Delegation Update Notes Overview Windows Server 2022 and Windows Server 2025 offer two server installation options : Server Core — This option is a minimal install. It removes the graphical shell and many nonessential components. You manage it from the command line, PowerShell, the Server Configuration tool (SConfig), or a remote tool. Server with Desktop Experience — This option installs the full graphical user interface and all client-experience features. You choose one option during setup. You cannot switch to the other option after installation, without a reinstall. If you manage a Server Core host, you see only a comm...

Configure WSFC Clustered MSDTC Via PowerShell 3.0

Overview: This document will discuss the steps to configure and change a clustered MSDTC instance on a Windows Server 2012 Failover Cluster [WSFC] using PowerShell 3.0.  This document does not describe the steps to install a clustered MSDTC instance. NOTE :  The steps below are run from a remote Windows Server 2012 administrative server with the necessary firewall access to administrate a WSFC and its node.  As an alternative you may run PowerShell on the hosts locally. Query WSFC Clustered MSDTC Settings: 1.      From the Start window run Windows Powershell as administrator . 2.      Enter a remote PowerShell session to the host using the fully qualified domain name [FQDN]. Enter-PSSession <HOST>.<DOMAIN> 3.   Query the current network settings for the clustered MSDTC instance. Get-DtcNetworkSetting –DtcName <DTC_NAME> Sample Output: AuthenticationLevel    ...

Pre-Staging Windows Server Failover Cluster Active Directory Objects

Overview This document will outline, on a high level, the process to pre-staged new Windows Server Failover Cluster [WSFC] Active Directory objects.  For detailed steps on creating these objects please refer to this document by Microsoft . Organizational Unit All Active Directory objects associated to the WSFC should be added to the appropriate Organizational Unit [ OU ].  This is primarily handled by your Windows/Infrastructure team. Cluster Name Object The Cluster Name Object [ CNO ] is the computer object which owns all other computer objects associated to the WSFC. Run dsa.msc from the Windows command prompt.  This will bring up the Active Directory Users and Computers UI. Go to the appropriate OU and create the new computer object [ CNO ] under it. NOTE :  Put in an appropriate description to help identify the purpose of this new object e.g. MYTESTCNO1$ Disable the new CNO obj...

Windows Server Failover Clustering Hotfixes for SQL Server AlwaysOn

Windows Server Failover Clustering/SQL Server Firewall Access Rules Last updated: 2026-08-21 17:01:33 This document defines the firewall rules necessary for a Multi-Subnet Windows Server Failover Cluster (WSFC) environment. It covers WSFC core communication, the WSFC dependency on Active Directory (AD), and SQL Server Availability Group (AG) communication. Use these rules when you request network access for a Multi-Subnet Cluster. This version corrects several rows to agree with current Microsoft documentation. See Verification Notes at the end of this document for the list of changes and sources. Table of Contents Windows Server Failover Clustering/SQL Server Firewall Access Rules Table of Contents Best Practice: IP Specificity Critical Action: Review Ephemeral Port Ranges Section 1: Core WSFC and Active Directory Ports Section 2: SQL Server Database Engine and Availability Group Ports Section 3: SQL Server BI Stack Ports (Conditional) Section 4: Multi-...