I have a 2 member Exchange 2019 DAG with a third file server serving as the File Witness Server. After the last round of Windows updates, the DAG lost connection to the FSW quorum server and I couldn't bring it back online in Failover Cluster Manager or start it in Exchange Start-ClusterResource as it failed with the error "The cluster resource could not be brought online by the resource monitor".
I attempted to rebuild the File Share Witness resource via Set-DatabaseAvailabilityGroup back to the original values, but I got the error and now I am missing the FSW resource under Cluster Core Resources entirely.
There was a problem changing the quorum model for database availability group Exch-2019-DAG. Error: An error occurred while attempting a cluster operation. Error: Cluster API failed: "ClusterResourceControl(controlcode=CLUSCTL_RESOURCE_SET_PRIVATE_PROPERTIES) failed with 0x533. Error: This user can't sign in because this account is currently disabled"
Does anyone know how to get around the account currently disabled issue? I checked the Cluster Name Object in AD and it is disabled, but I think it is supposed to be that way.