Initially got a WinRM error when trying to set options in the CAU gui so ran test-causetup which reported the same errors after rule 11 below. It's also reporting several other failures though which are bogus. Rule 3 is giving an error saying PSRemoting is not enabled yet it is and I've even tried "enabling" it using -force. Rule 2 not positive about but know winrm is running and configured and firewall is off. Rule 11 is failing on the cluster name its not a server...
To test PSRemoting I ran this command on the other cluster node and it works BUT if you run it and target the same machine you are on it fails. This happens on both nodes and both nodes are giving all the same errors.
Invoke-Command -ComputerName 90vmhost5 -ScriptBlock { Get-ChildItem c:\ } -credential CM
PS C:\Windows\system32> Test-CauSetup
RuleId : 1
Title : The failover cluster must be available
State : Started
Severity : Info
FailedMachines : {}
PercentComplete : 1
RuleId : 1
Title : The failover cluster must be available
State : Succeeded
Severity : Info
FailedMachines : {}
PercentComplete : 5
RuleId : 2
Title : The failover cluster nodes must be enabled for remote management via WMIv2
State : Started
Severity : Info
FailedMachines : {}
PercentComplete : 6
RuleId : 2
Title : The failover cluster nodes must be enabled for remote management via WMIv2
State : Failed
Severity : Error
FailedMachines : {90VMHost5}
PercentComplete : 11
RuleId : 3
Title : Windows PowerShell remoting should be enabled on each failover cluster node
State : Started
Severity : Info
FailedMachines : {}
PercentComplete : 12
RuleId : 3
Title : Windows PowerShell remoting should be enabled on each failover cluster node
State : Failed
Severity : Error
FailedMachines : {90VMHost5}
PercentComplete : 16
RuleId : 4
Title : The failover cluster must be running Windows Server 2012
State : Started
Severity : Info
FailedMachines : {}
PercentComplete : 17
RuleId : 4
Title : The failover cluster must be running Windows Server 2012
State : Succeeded
Severity : Info
FailedMachines : {}
PercentComplete : 21
RuleId : 5
Title : The required versions of .NET Framework and Windows PowerShell must be installed on all
failover cluster nodes
State : Started
Severity : Info
FailedMachines : {}
PercentComplete : 22
RuleId : 5
Title : The required versions of .NET Framework and Windows PowerShell must be installed on all
failover cluster nodes
State : Succeeded
Severity : Info
FailedMachines : {}
PercentComplete : 45
RuleId : 6
Title : The Cluster service should be running on all cluster nodes
State : Started
Severity : Info
FailedMachines : {}
PercentComplete : 46
RuleId : 6
Title : The Cluster service should be running on all cluster nodes
State : Succeeded
Severity : Info
FailedMachines : {}
PercentComplete : 55
RuleId : 7
Title : Automatic Updates must not be configured to automatically install updates on any failover
cluster node
State : Started
Severity : Info
FailedMachines : {}
PercentComplete : 56
RuleId : 7
Title : Automatic Updates must not be configured to automatically install updates on any failover
cluster node
State : Succeeded
Severity : Info
FailedMachines : {}
PercentComplete : 64
RuleId : 8
Title : The failover cluster nodes should use the same update source
State : Started
Severity : Info
FailedMachines : {}
PercentComplete : 65
RuleId : 8
Title : The failover cluster nodes should use the same update source
State : Succeeded
Severity : Info
FailedMachines : {}
PercentComplete : 73
RuleId : 9
Title : A firewall rule that allows remote shutdown should be enabled on each node in the failover
cluster
State : Started
Severity : Info
FailedMachines : {}
PercentComplete : 74
RuleId : 9
Title : A firewall rule that allows remote shutdown should be enabled on each node in the failover
cluster
State : Succeeded
Severity : Info
FailedMachines : {}
PercentComplete : 82
RuleId : 10
Title : The machine proxy on each failover cluster node should be set to a local proxy server
State : Started
Severity : Info
FailedMachines : {}
PercentComplete : 83
RuleId : 10
Title : The machine proxy on each failover cluster node should be set to a local proxy server
State : Failed
Severity : Warning
FailedMachines : {90VMHost5, 90VMHost6}
PercentComplete : 91
RuleId : 11
Title : The CAU clustered role should be installed on the failover cluster to enable self-updating
mode
State : Started
Severity : Info
FailedMachines : {}
PercentComplete : 92
RuleId : 11
Title : The CAU clustered role should be installed on the failover cluster to enable self-updating
mode
State : Failed
Severity : Warning
FailedMachines : {VMCluster}
PercentComplete : 100
WARNING: <f:WSManFault xmlns:f="http://schemas.microsoft.com/wbem/wsman/1/wsmanfault" Code="2150859027" Machin
e="90VMHost5.pacific.local"><f:Message>The WinRM client sent a request to an HTTP server and got a response sa
ying the requested HTTP URL was not available. This is usually returned by a HTTP server that does not support
the WS-Management protocol. </f:Message></f:WSManFault>
WARNING: Connecting to remote server 90VMHost5 failed with the following error message : The WinRM client sent
a request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usual
ly returned by a HTTP server that does not support the WS-Management protocol. For more information, see the a
bout_Remote_Troubleshooting Help topic.
WARNING: The WinRM client sent a request to an HTTP server and got a response saying the requested HTTP URL wa
s not available. This is usually returned by a HTTP server that does not support the WS-Management protocol.
ModelId : Microsoft/Windows/ClusterAwareUpdating
SubModelId :
Success : True
ScanTime : 2/1/2017 4:10:32 PM
ScanTimeUtcOffset : -08:00:00
Detail : {90VMHOST5, 90VMHOST5}