Thanks
@Garth.
The logs are pointing to an issue with the netbios name issue on our SQL Cluster.
Thinking the issue may be WINS - I have implemented binding as per
https://docs.microsoft.com/en-us/tr...s-wins-dont-bind-cluster-ip-address-resources, however the logs are still showing the same failure.
Any help is much appreciated.
Following are an extraction of the ConfigMgrPrereq.log:
dbcluster.blah.blah.org.au; Validate FQDN of SQL Server Computer; Passed Configuration Manager Prereq 25/08/2022 4:59:26 PM 59840 (0xE9C0)
INFO: Prerequisite rule 'Primary FQDN' will run for easysetup upgrade. Configuration Manager Prereq 25/08/2022 4:59:26 PM 59840 (0xE9C0)
INFO:CheckSupportedFQDNFormat <dbcluster.blah.blah.org.au> Configuration Manager Prereq 25/08/2022 4:59:26 PM 59840 (0xE9C0)
INFO: NetBIOS <SVW-BNE-HV-12> Configuration Manager Prereq 25/08/2022 4:59:26 PM 59840 (0xE9C0)
ERROR: Failed to get SQL instance sub registry key from [dbcluster.blah.blah.org.au] Configuration Manager Prereq 25/08/2022 4:59:26 PM 59840 (0xE9C0)
dbcluster.blah.blah.org.au; Primary FQDN; Error; Configuration Manager only supports the use of primary FQDN's, where the DNS hostname (first label in the FQDN) matches the NetBIOS hostname of the computer. The FQDN provided for this site system does not meet this requirement and cannot be used. Correct the FQDN and try again. Configuration Manager Prereq 25/08/2022 4:59:26 PM 59840 (0xE9C0)