Windows 10: Azure Stack HCI Failover Cluster Test report Domain Controller Error.

Hello Everyone, we have recently deployed 3 different dell nodes for Azure stack HCI and everything was ok so far but now, when we setup a failover cluster for the nodes, and ran a test which shows us all the configuration in place, here we are getting a error message that the systemonfiguration > active directory connection fails. any response to it much appreciated. error message is- Connection to a writable domain controller from node "hci1.xyz.com" could not be determined due to the following error: The domain controller name could not be retrieved from computer "hci1abc".

:)

 

I have a failover cluster 2012R2  with 10+ nodes, I have 6+ Domain Controller running on 2012r2. Is it okay If I upgrade domain controller to 2019 and leave failover cluster running on 2012r2?

I have a failover cluster 2012R2 with 10+ nodes, I have 6+ Domain Controller running on 2012r2. Is it okay If I upgrade domain controller to 2019 and leave failover cluster running on 2012r2?

 

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

 

Windows server 2016 Domain Controller Fail-over Clustering

Dear all,

I have installed two windows server 2016 on virtual environment, and I want to apply Domain Controller fail-over clustering on them. what scenario I can apply on my servers to handle the fail-over clustering? Is it possible to apply Failover clustering between
two Domain controller? For example, if one of my Domain Controller goes down and is inaccessible, then the second Domain Controller should take action and all user should not be disconnected. In addition to this all users must be able to access the domain,
and all services must be available to all users at the second Domain Controller.

Thanks in Advance.