Accidentally set OS Mgmt network to "Do Not Allow Cluster Comm on this network"

now can't manage cluster via failover cluster manager. can't launch fcm either of local hosts they're core boxes. 

been looking @ powershell , cluster , cluster network commands, don't see definitive reverse this. 

i can connect server via windows server manager. 

how can reverse can manage cluster via public interface? 

the cluster has 2 interfaces, os mgmt (public) , heart beat (private). failover , vms still up, can't manage via fcm. 

thanks,

woody

more info:

2 node 2008 r2 sp1 hyper-v cluster

thanks blake, did try that, no go. here's did reverse changes:

discovered role of os mgmt network set 0:

d  os mgmt              role                           0 (0x0)

in order set original value , allow cluster , client communication, had set value 3 using following command on active cluster node:

cluster network "os mgmt" /prop role=3

Windows Server  >  High Availability (Clustering)