Windows 10: Failover Cluster

DearsWe upgraded our environment from Windows Server 2012 R2 into Windows 2019 Everything seems to work normally except for Windows Failover Cluster ServiceThe service is not able to run at all with the event id1090We removed the failover cluster feature and re-add it again; however, the problem persistsPlease adviseThank you

:)

 

Windows 10 RSAT - Failover Cluster Manager

I installed the remote server admin tools yesterday to my Win10 enterprise which made me very happy at first. DNS, DHCP, ADUC all worked great. Then I opened failover cluster manager. Problems began.

We have dozens of MS clusters running 2003 and up, mostly 2008R2 or 2012R2. When I try and manage them I get

Connection Not Supported

Cluster XXXXXXX not supported

The cluster to which you are attempting to connect is not a version of the cluster supported by this version of Failover Cluster Manager

This is happening with all the clusters I need to manage. Is this a bug or "working as designed"?

 

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).

 

Win. 10 Failover Cluster Manager error

Hey all,

When I'm trying to connect to VM via "Failover Cluster Manager" mmc I'm getting "Failed to connect to virtual machine 'xxx'. For more data, see 'Information Details'."

When connecting to VMs from Hyper-v Manager mmc the VMs open as expected.

My Hyper-v cluster is 2012-R2 with latest updates and my win. 10 is fully updated.

Any suggestions?

Nir