Windows 10: How to configure cluster on Biztlak 2020 servers

Any leads are appreciated.

:)

 

Managing Server 2019 clustering

SQL Server 2019 Always-on implemented on 2 Nodes on Windows Server 2022 and when i perform manual failover to the second node I got this warning "the current wsfc cluster quorum vote configuration is not recommended for this availability group", and the Always-on availability group is healthy and no problem with it.

i tried the following without no luck

1. Update Windows Server 2022 to latest update
   
2. reconfigure WSFC quorum to use Defualt configuration
   
3. reconfigure WSFC quorum to use Witness fileShare.
   

 

Windows 2019 Datacenter Cluster - Configuring Cluster Aware Updating

Hello, everyone.

I am trying to configure Cluster Aware Updating (CAU) on a 2-node, Windows 2019 Datacenter Cluster. Using Failover Cluster Manager, when I run the "Analyze cluster updating readiness" function, I receive a report with two errors and one warning.

The first error is "The failover cluster nodes must be enabled for remote management via WMIv2". They already are. When I run "WINRM QUICKCONFIG -q" on each node, I get no errors; in fact I get "WinRM service is already running on this machine. WinRM is
already set up for remote management on this computer."

The second error is "Windows PowerShell remoting should be enabled on each failover cluster node". It already is. When I run "Enable-PSRemoting" on each node, I get no errors;. in fact I get no messages back at all.

The one warning is "The CAU clustered role should be installed on the failover cluster to enable self-updating mode". I think this will go away once I get CAU set up and running on this cluster.

My command to add CAU to my cluster ends up being:

Add-CauClusterRole -ClusterName ES19TESTCL1 -Force -CauPluginName Microsoft.WindowsUpdatePlugin -MaxRetriesPerNode 3 -CauPluginArguments @{ 'IncludeRecommendedUpdates' = 'True' } -RequireAllNodesOnline -StartDate "8/1/2020 12:00:00 AM" -DaysOfWeek 64 -WeeksOfMonth
@(3) -VirtualComputerObjectName ES19TESTCL1CAU -EnableFirewallRules;

ES19TESTCL1CAU is a computer name I pre-staged in my Active Directory.

The results of running that PowerShell script was: "Validation failed for adding CAU cluster role." I'm guessing once I figure out and fix what's causing the validation errors, the script will work. Any suggestions are greatly appreciated. This is my first
cluster.

 

Issues with report server setup during Install of MBAM using a SQL failover cluster

I'm trying to setup MBAM 2.5SP1 on Server 2016 using a SQL 2016 on a Failover Cluster (but not using AO).

The initial database configuration went smooth, but setting up the next step (Reports) is causing an issue because it cannot find the instance of the report server.

"Unable to find an instance of the Reporting Services.

That said, I realize that the report server is not supported with the failover cluster, but is there a way to point the Report feature to another SQL server or a server that has the reporting services (ie: one of the Failover cluster nodes) instead of auto-detecting
the SQL failover cluster name/IP?

I'm trying to avoid having a SQL server just for MBAM if I can avoid it (for cost and manageability reasons).