SERVERPROPERTY('IsClustered') does not return the correct value in a cluster configuration
Hi all! I'm testing some t-sql SQL properties for a data collection project and I got a strange case with the query below: SELECT SERVERPROPERTY(''MachineName') AS [MachineName], SERVERPROPERTY('ServerName') AS [ServerName], SERVERPROPERTY('InstanceName') AS [Instance], SERVERPROPERTY('IsClustered') AS [IsClustered], SERVERPROPERTY('ComputerNamePhysicalNetBIOS') AS [ComputerNamePhysicalNetBIOS], SERVERPROPERTY('Edition') AS [Edition] I have two test instances of SQL Server 2019. They both belong to a cluster without shared storage, as the availability groups allow it: SQLAGCLU I don't understand why the query is returning "incorrect" properties. I expected them to have the value 1 for the "IsClustered" column. From the query that I use, I have no idea witch SQL instance are in a cluster... Some one can give a feedback about it? Thanks ALEN
Failover Cluster Validation Stuck
Hello everyone, I'm having the following problem when creating a 2-node HA cluster (Server 2025) using the Windows Admin Center (Gateway). Up to the point "Validate Cluster" everything worked fine. Unfortunately, the process gets stuck at "1% Gathering data about nodes". However, I can confirm that the cluster report was successfully created on the first node without any errors. Has anyone else seen something similar and, ideally, have a solution for me? I checked the following: Permissions such as CredSSP, Remote Powershell and WinRM are correctly implemented on the WAC gateway and nodes. Manually execute the PowerShell command successfully: Test-Cluster -Node $ServerList -Include "Storage Spaces Direct", "Inventory", "System Configuration"
New-FileShare and FileServerFriendlyName
Hi, I tried to use the New-FileShare CMDLet (or functions actually) for creating network share on my cluster, but that seems to requiring argument: FileServerFriendlyName. Anybody knows what that argument should be? I have tried to use resource name from the file share or cluster name, both of them failed with error: "New-FileShare : No MSFT_FileServer objects found with property 'FriendlyName' equal to. . ." When I used active node name I got a bit different error: "The operation failed with return code 2147948333. . ." The error is referring that node is not active, but at least the storages are. When the share is done from File Explorer there are no troubles.SQL Always On when QUORUM fails
Hello friends, i have a sql cluster with always on and today i noticed a scenario. When I restarted the domain / dns server that is my quorum when trying to authenticate to the databases I had difficulty and generated several failures in the cluster of quorum unavailable. So I asked myself regarding the importance of the availability of my domain controller server to access the databases. However I have another domain controller server (secondary) which is also DNS. Can anyone tell me how long it takes servers that authenticate to the domain/dns server need to direct connections to the secondary server? Can this be adjusted to be faster? Thanks.
Server 2019 no "Server Hello" when using TLS_RSA_WITH_AES_ ciphers (TLS1.2) schannel 36874
Hi Hoping someone might have come across something similar as the support forum entries are filled with irrelevant responses and tumbleweed. A recently migrated CA cluster is not sending any TLS conversation completion when the client uses a cipher from the TLS_RSA_WITH_AES_* type (so TLS_RSA_WITH_AES_128_CBC_SHA256 or similar). This also seems to be negatively impacting RPC certificate enrolment from Windows 7 systems. Using Nartac tools and manually (double, triple, quadruple) checking the registry settings myself I can see that the ciphers are present in the list of supported/available ciphers. I can see that TLS1.2 is working. As soon as a client offers TLS_ECDH_* the server responds like an enthusiastic puppy. using TLS_RSA_WITH_AES_ it ignores the traffic (no server hello or attempt to negotiate) and logs Schannel Errors 36874 in the server event log. I have verified this using wireshark on client and server. Whilst these are hosted in azure there shouldn't be any network layer kit interfering with the connection. There is a standard load balancer which single routes all traffic to the active AD CS cluster node. No inspection or TLS termination should be occurring. There are no GPOs controlling anything to do with TLS or communication security (checked with gpresult and gpmc, along with repeated verification of the registry settings) has anyone seen anything like this before? yes I have been through the enabling TLS 1.2 articles a bajillion times and know where to enable TLS 1.2 for both schannel and .net In need of more straws to clutch at.
