Good afternoon,
Need help with what seems to be a simple task, but continues to fails. We’re trying to build a Windows 2016 Failover Cluster, which continues to fail. Windows 2012 R2 Failover Cluster is successful, same domain, accounts. Here are the details on each configuration. Will be glad to provide additional information that could help.
Thanks, -jim
Windows 2016 Failover Cluster
AD – Windows 2016 domain
FFL – Windows 2012 R2 Forest Functional Level
DFL – Windows 2016 Domain Functional Level
2 servers, Windows 2016 Datacenter
Event Viewer – FailoverClustering DiagnosticVerbose log enabled
Results: Cluster Validation passes, select build cluster from test details. Build immediately fails, very little details in the cluster.log (see details below)
Same results via GUI or with PS New-cluster cmdlet
Windows 2012 R2 Failover Cluster
AD – Windows 2016 domain
FFL – Windows 2012 R2 Forest Functional Level
DFL – Windows 2016 Domain Functional Level
2 server, Windows 2012 R2 Standard
Results: Build completes successfully, ton of details in the cluster.log
Some additional points/details…
- Create Cluster Wizard report shows the 'bind to domain controller . more data is available.' Error (see details below).
- Prestaged the CNO, no difference with or without.
- We've also tried the build with and without the 'Deny Access to this computer from the Network' policy set. Still fails.
- Cluster DiagnosticsVerbose logs are not showing much details/errors.
- Tried alternate pair of Win2016 servers in two domains of forest, same error.
- Seems to be a permissions error in AD since the failure happens right after the cluster build dialog that states 'Find a suitable domain controller for node <nodename>'
Cluster.log from failed Windows 2016 build…
00002a78.00002b2c::2018/03/20-14:54:06.249 DBG Cluster node cleanup thread started.
00002a78.00002b2c::2018/03/20-14:54:06.249 DBG Starting cluster node cleanup...
00002a78.00002b2c::2018/03/20-14:54:06.249 DBG Disabling the cluster service...
00002a78.00002b2c::2018/03/20-14:54:06.251 DBG Releasing clustered storages...
00002a78.00002b2c::2018/03/20-14:54:06.252 DBG Getting clustered disks...
00002a78.00002b2c::2018/03/20-14:54:06.252 DBG Waiting for clusdsk to finish its cleanup...
00002a78.00002b2c::2018/03/20-14:54:06.253 DBG Clearing the clusdisk database...
00002a78.00002b2c::2018/03/20-14:54:06.254 DBG Waiting for clusdsk to finish its cleanup...
00002a78.00002b2c::2018/03/20-14:54:06.255 DBG Relinquishing clustered disks...
00002a78.00002b2c::2018/03/20-14:54:06.255 DBG Opening disk handle by index...
00002a78.00002b2c::2018/03/20-14:54:06.258 DBG Getting disk ID from layout...
00002a78.00002b2c::2018/03/20-14:54:06.258 DBG Reset CSV state ...
00002a78.00002b2c::2018/03/20-14:54:06.259 DBG Relinquish disk if clustered...
00002a78.00002b2c::2018/03/20-14:54:06.261 DBG Opening disk handle by index...
00002a78.00002b2c::2018/03/20-14:54:06.263 DBG Getting disk ID from layout...
00002a78.00002b2c::2018/03/20-14:54:06.264 DBG Reset CSV state ...
00002a78.00002b2c::2018/03/20-14:54:06.264 DBG Relinquish disk if clustered...
00002a78.00002b2c::2018/03/20-14:54:06.266 DBG Opening disk handle by index...
00002a78.00002b2c::2018/03/20-14:54:06.271 DBG Resetting cluster registry entries...
00002a78.00002b2c::2018/03/20-14:54:06.273 DBG Resetting NLBSFlags value ...
00002a78.00002b2c::2018/03/20-14:54:06.278 DBG Unloading the cluster Windows registry hive...
00002a78.00002b2c::2018/03/20-14:54:06.279 DBG Getting the cluster Windows registry hive file path...
00002a78.00002b2c::2018/03/20-14:54:06.280 DBG Getting the cluster Windows registry hive file path...
00002a78.00002b2c::2018/03/20-14:54:06.281 DBG Getting the cluster Windows registry hive file path...