CM 1910 prerequisites check failing for clustered SQL Server

[hybrid]

A little background. We have:

• a single site server (Windows Server 2016 1607) running the various CM roles (CM 1906, site version 5.0.8853.1000)
• a two-node Windows Server 2019 cluster hosting SQL Server 2016 for the site database server

The database cluster has a shared hostname and IP address for the Windows cluster computer object itself (DB-Cluster.our-domain) and another shared hostname and IP address for the SQL Server role (DB-Cluster-SQL.our-domain).

We've not had any previous issues with this setup for the last few updates to ConfigMgr, but when attempting to upgrade to 1910, the prerequisites check is failing.

===== INFO: Prerequisite Type & Server: SQL:DB-Cluster-SQL..********* =====  $$<Configuration Manager Prereq><01-10-2020 09:54:31.766+00><thread=11992 (0x2ED8)>
<<<RuleCategory: Access Permissions>>>  $$<Configuration Manager Prereq><01-10-2020 09:54:31.766+00><thread=11992 (0x2ED8)>
<<<CategoryDesc: Checking access permissions...>>>  $$<Configuration Manager Prereq><01-10-2020 09:54:31.782+00><thread=11992 (0x2ED8)>
INFO: Prerequisite rule 'SQL Server sysadmin rights' will run for easysetup upgrade.  $$<Configuration Manager Prereq><01-10-2020 09:54:31.782+00><thread=11992 (0x2ED8)>
DB-Cluster-SQL..*********;    SQL Server sysadmin rights;    Passed  $$<Configuration Manager Prereq><01-10-2020 09:54:31.782+00><thread=11992 (0x2ED8)>
INFO: Prerequisite rule 'SQL Server sysadmin rights for reference site' will run for easysetup upgrade.  $$<Configuration Manager Prereq><01-10-2020 09:54:31.797+00><thread=11992 (0x2ED8)>
DB-Cluster-SQL..*********;    SQL Server sysadmin rights for reference site;    Passed  $$<Configuration Manager Prereq><01-10-2020 09:54:31.797+00><thread=11992 (0x2ED8)>
INFO: Prerequisite rule 'Site server computer account administrative rights' will run for easysetup upgrade.  $$<Configuration Manager Prereq><01-10-2020 09:54:31.828+00><thread=11992 (0x2ED8)>
INFO: Retrieving the list of nodeS for cluster <DB-Cluster-SQL..*********>  $$<Configuration Manager Prereq><01-10-2020 09:54:31.828+00><thread=11992 (0x2ED8)>
CSql Error: Cannot find data for connection type: CLUSTER_NODE_LIST, cannot get a connection.  $$<Configuration Manager Prereq><01-10-2020 09:54:31.828+00><thread=11992 (0x2ED8)>
INFO: Retrieved nodes: <DB02,DB01>  $$<Configuration Manager Prereq><01-10-2020 09:54:31.891+00><thread=11992 (0x2ED8)>
INFO: CheckLocalSys is Admin of <DB02>.  $$<Configuration Manager Prereq><01-10-2020 09:54:31.891+00><thread=11992 (0x2ED8)>
INFO: smstsvc.exe source path is set to E:\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\CMUSTAGING\E2F7B2F9-4828-4650-9144-5DC7956781B7\SMSSETUP\BIN\X64  $$<Configuration Manager Prereq><01-10-2020 09:54:31.891+00><thread=11992 (0x2ED8)>
INFO: File \\?\C:\WINDOWS\smstsvc_test_1.exe does not exist. No zapping needed.  $$<Configuration Manager Prereq><01-10-2020 09:54:31.906+00><thread=11992 (0x2ED8)>
INFO: test loop count:6.  $$<Configuration Manager Prereq><01-10-2020 09:54:38.232+00><thread=11992 (0x2ED8)>
INFO: smstsvc_test_1 Return result <0>  $$<Configuration Manager Prereq><01-10-2020 09:54:38.232+00><thread=11992 (0x2ED8)>
INFO: CheckLocalSys is Admin of <DB01>.  $$<Configuration Manager Prereq><01-10-2020 09:54:40.239+00><thread=11992 (0x2ED8)>
INFO: smstsvc.exe source path is set to E:\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\CMUSTAGING\E2F7B2F9-4828-4650-9144-5DC7956781B7\SMSSETUP\BIN\X64  $$<Configuration Manager Prereq><01-10-2020 09:54:40.239+00><thread=11992 (0x2ED8)>
INFO: File \\?\C:\WINDOWS\smstsvc_test_2.exe does not exist. No zapping needed.  $$<Configuration Manager Prereq><01-10-2020 09:54:40.239+00><thread=11992 (0x2ED8)>
INFO: test loop count:6.  $$<Configuration Manager Prereq><01-10-2020 09:54:46.392+00><thread=11992 (0x2ED8)>
INFO: smstsvc_test_2 Return result <0>  $$<Configuration Manager Prereq><01-10-2020 09:54:46.392+00><thread=11992 (0x2ED8)>
DB-Cluster-SQL..*********;    Site server computer account administrative rights;    Passed  $$<Configuration Manager Prereq><01-10-2020 09:54:48.406+00><thread=11992 (0x2ED8)>
INFO: Prerequisite rule 'SQL Server security mode' is marked to not run for easysetup.  $$<Configuration Manager Prereq><01-10-2020 09:54:48.423+00><thread=11992 (0x2ED8)>
<<<RuleCategory: System Requirements>>>  $$<Configuration Manager Prereq><01-10-2020 09:54:48.423+00><thread=11992 (0x2ED8)>
<<<CategoryDesc: Checking system requirements for ConfigMgr...>>>  $$<Configuration Manager Prereq><01-10-2020 09:54:48.438+00><thread=11992 (0x2ED8)>
INFO: Prerequisite rule 'Unsupported site server operating system version for Setup' will run for easysetup upgrade.  $$<Configuration Manager Prereq><01-10-2020 09:54:48.438+00><thread=11992 (0x2ED8)>
CurrentVersion =   $$<Configuration Manager Prereq><01-10-2020 09:54:48.454+00><thread=11992 (0x2ED8)>
INFO: OS version:0, ServicePack:0.  $$<Configuration Manager Prereq><01-10-2020 09:54:48.454+00><thread=11992 (0x2ED8)>
DB-Cluster-SQL..*********;    Unsupported site server operating system version for Setup;    Error;    Configuration Manager site systems can only be installed on computers running supported operating systems. https://go.microsoft.com/fwlink/?linkid=841654  $$<Configuration Manager Prereq><01-10-2020 09:54:48.454+00><thread=11992 (0x2ED8)>
INFO: Prerequisite rule 'Domain membership' will run for easysetup upgrade.  $$<Configuration Manager Prereq><01-10-2020 09:54:48.485+00><thread=11992 (0x2ED8)>
DB-Cluster-SQL..*********;    Domain membership;    Passed  $$<Configuration Manager Prereq><01-10-2020 09:54:48.500+00><thread=11992 (0x2ED8)>
INFO: Prerequisite rule 'Pending system restart' will run for easysetup upgrade.  $$<Configuration Manager Prereq><01-10-2020 09:54:48.516+00><thread=11992 (0x2ED8)>
INFO: Failed to open registry key SOFTWARE\Microsoft\ServerManager on DB-Cluster-SQL..*********. Error = 53  $$<Configuration Manager Prereq><01-10-2020 09:54:48.531+00><thread=11992 (0x2ED8)>
INFO: Failed to open registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\RebootPending on DB-Cluster-SQL..*********. Error = 53  $$<Configuration Manager Prereq><01-10-2020 09:54:48.531+00><thread=11992 (0x2ED8)>
INFO: Failed to open registry key SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired on DB-Cluster-SQL..*********. Error = 53  $$<Configuration Manager Prereq><01-10-2020 09:54:48.547+00><thread=11992 (0x2ED8)>
INFO: Failed to open registry key SYSTEM\CurrentControlSet\Control\Session Manager on DB-Cluster-SQL..*********. Error = 53  $$<Configuration Manager Prereq><01-10-2020 09:54:48.547+00><thread=11992 (0x2ED8)>
DB-Cluster-SQL..*********;    Pending system restart;    Passed  $$<Configuration Manager Prereq><01-10-2020 09:54:48.547+00><thread=11992 (0x2ED8)>
<<<RuleCategory: Dependent Components>>>  $$<Configuration Manager Prereq><01-10-2020 09:54:48.578+00><thread=11992 (0x2ED8)>
<<<CategoryDesc: Checking dependent components for ConfigMgr...>>>  $$<Configuration Manager Prereq><01-10-2020 09:54:48.578+00><thread=11992 (0x2ED8)>
INFO: Prerequisite rule 'SQL Server version' will run for easysetup upgrade.  $$<Configuration Manager Prereq><01-10-2020 09:54:48.578+00><thread=11992 (0x2ED8)>
INFO: SQL Server version detected is 13.0, 13.0.5598.27 (SP2).~  $$<Configuration Manager Prereq><01-10-2020 09:54:48.578+00><thread=11992 (0x2ED8)>
INFO: Return code:0, Major:13, Minor:0, BuildNum:5598  $$<Configuration Manager Prereq><01-10-2020 09:54:48.594+00><thread=11992 (0x2ED8)>
DB-Cluster-SQL..*********;    SQL Server version;    Passed  $$<Configuration Manager Prereq><01-10-2020 09:54:48.594+00><thread=11992 (0x2ED8)>
INFO: Prerequisite rule 'SQL Server supported version' will run for easysetup upgrade.  $$<Configuration Manager Prereq><01-10-2020 09:54:48.610+00><thread=11992 (0x2ED8)>
INFO: SQL Server version detected is 13.0, 13.0.5598.27 (SP2).~  $$<Configuration Manager Prereq><01-10-2020 09:54:48.625+00><thread=11992 (0x2ED8)>
INFO: Return code:0, Major:13, Minor:0, BuildNum:5598  $$<Configuration Manager Prereq><01-10-2020 09:54:48.625+00><thread=11992 (0x2ED8)>
DB-Cluster-SQL..*********;    SQL Server supported version;    Passed  $$<Configuration Manager Prereq><01-10-2020 09:54:48.625+00><thread=11992 (0x2ED8)>
INFO: Prerequisite rule 'SQL Server Edition' will run for easysetup upgrade.  $$<Configuration Manager Prereq><01-10-2020 09:54:48.641+00><thread=11992 (0x2ED8)>
ERROR:Can not get sql instance regkey.  $$<Configuration Manager Prereq><01-10-2020 09:54:48.656+00><thread=11992 (0x2ED8)>
ERROR:Failed to get Sql edition, Sql Server:DB-Cluster-SQL..*********, instance:.  $$<Configuration Manager Prereq><01-10-2020 09:54:48.656+00><thread=11992 (0x2ED8)>
DB-Cluster-SQL..*********;    SQL Server Edition;    Passed  $$<Configuration Manager Prereq><01-10-2020 09:54:48.656+00><thread=11992 (0x2ED8)>
INFO: Prerequisite rule 'SQL Server Tcp Port' will run for easysetup upgrade.  $$<Configuration Manager Prereq><01-10-2020 09:54:48.672+00><thread=11992 (0x2ED8)>
INFO: Checking Tcp is enabled to Static port, SQL Server:DB-Cluster-SQL..*********, Instance:.  $$<Configuration Manager Prereq><01-10-2020 09:54:48.688+00><thread=11992 (0x2ED8)>
DB-Cluster-SQL..*********;    SQL Server Tcp Port;    Passed  $$<Configuration Manager Prereq><01-10-2020 09:54:48.797+00><thread=11992 (0x2ED8)>
INFO: Prerequisite rule 'Configuration for SQL Server memory usage' is marked to not run for easysetup.  $$<Configuration Manager Prereq><01-10-2020 09:54:48.813+00><thread=11992 (0x2ED8)>
INFO: Prerequisite rule 'SQL Server process memory allocation' is marked to not run for easysetup.  $$<Configuration Manager Prereq><01-10-2020 09:54:48.813+00><thread=11992 (0x2ED8)>
INFO: Prerequisite rule 'Case-insensitive collation on SQL Server' will run for easysetup upgrade.  $$<Configuration Manager Prereq><01-10-2020 09:54:48.813+00><thread=11992 (0x2ED8)>
DB-Cluster-SQL..*********;    Case-insensitive collation on SQL Server;    Passed  $$<Configuration Manager Prereq><01-10-2020 09:54:48.813+00><thread=11992 (0x2ED8)>
INFO: Prerequisite rule 'Validate FQDN of SQL Server Computer' will run for easysetup upgrade.  $$<Configuration Manager Prereq><01-10-2020 09:54:48.844+00><thread=11992 (0x2ED8)>
INFO: Check Machine FQDN: <DB-Cluster-SQL..*********>.  $$<Configuration Manager Prereq><01-10-2020 09:54:48.844+00><thread=11992 (0x2ED8)>
INFO: getaddrinfo returned success.  $$<Configuration Manager Prereq><01-10-2020 09:54:48.844+00><thread=11992 (0x2ED8)>
DB-Cluster-SQL..*********;    Validate FQDN of SQL Server Computer;    Passed  $$<Configuration Manager Prereq><01-10-2020 09:54:48.844+00><thread=11992 (0x2ED8)>
INFO: Prerequisite rule 'Primary FQDN' will run for easysetup upgrade.  $$<Configuration Manager Prereq><01-10-2020 09:54:48.860+00><thread=11992 (0x2ED8)>
INFO:CheckSupportedFQDNFormat <DB-Cluster-SQL..*********>  $$<Configuration Manager Prereq><01-10-2020 09:54:48.860+00><thread=11992 (0x2ED8)>
INFO: NetBIOS <DB01>  $$<Configuration Manager Prereq><01-10-2020 09:54:48.891+00><thread=11992 (0x2ED8)>
ERROR: Failed to get SQL instance  sub registry key from [DB-Cluster-SQL..*********]  $$<Configuration Manager Prereq><01-10-2020 09:54:48.891+00><thread=11992 (0x2ED8)>
DB-Cluster-SQL..*********;    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><01-10-2020 09:54:48.891+00><thread=11992 (0x2ED8)>
<<<RuleCategory: Site Upgrade Requirements>>>  $$<Configuration Manager Prereq><01-10-2020 09:54:48.922+00><thread=11992 (0x2ED8)>
<<<CategoryDesc: Checking if the target ConfigMgr site is ready to upgrade...>>>  $$<Configuration Manager Prereq><01-10-2020 09:54:48.922+00><thread=11992 (0x2ED8)>
===== INFO: Prerequisite Type & Server: SDK:SCCM-2012..********* =====  $$<Configuration Manager Prereq><01-10-2020 09:54:48.922+00><thread=11992 (0x2ED8)>
<<<RuleCategory: Access Permissions>>>  $$<Configuration Manager Prereq><01-10-2020 09:54:48.922+00><thread=11992 (0x2ED8)>
<<<CategoryDesc: Checking access permissions...>>>  $$<Configuration Manager Prereq><01-10-2020 09:54:48.922+00><thread=11992 (0x2ED8)>
INFO: Prerequisite rule 'Administrative rights on site system' will run for easysetup upgrade.  $$<Configuration Manager Prereq><01-10-2020 09:54:48.938+00><thread=11992 (0x2ED8)>
INFO: The rule 'Administrative rights on site system' has been run on server 'SCCM-2012..*********', skipped.  $$<Configuration Manager Prereq><01-10-2020 09:54:48.938+00><thread=11992 (0x2ED8)>
<<<RuleCategory: System Requirements>>>  $$<Configuration Manager Prereq><01-10-2020 09:54:48.938+00><thread=11992 (0x2ED8)>
<<<CategoryDesc: Checking system requirements for ConfigMgr...>>>  $$<Configuration Manager Prereq><01-10-2020 09:54:48.938+00><thread=11992 (0x2ED8)>
INFO: Prerequisite rule 'Unsupported site server operating system version for Setup' will run for easysetup upgrade.  $$<Configuration Manager Prereq><01-10-2020 09:54:48.938+00><thread=11992 (0x2ED8)>
INFO: The rule 'Unsupported site server operating system version for Setup' has been run on server 'SCCM-2012..*********', skipped.  $$<Configuration Manager Prereq><01-10-2020 09:54:48.938+00><thread=11992 (0x2ED8)>
INFO: Prerequisite rule 'Domain membership' will run for easysetup upgrade.  $$<Configuration Manager Prereq><01-10-2020 09:54:48.938+00><thread=11992 (0x2ED8)>
INFO: The rule 'Domain membership' has been run on server 'SCCM-2012..*********', skipped.  $$<Configuration Manager Prereq><01-10-2020 09:54:48.938+00><thread=11992 (0x2ED8)>
<<<RuleCategory: Dependent Components>>>  $$<Configuration Manager Prereq><01-10-2020 09:54:48.938+00><thread=11992 (0x2ED8)>
<<<CategoryDesc: Checking dependent components for ConfigMgr...>>>  $$<Configuration Manager Prereq><01-10-2020 09:54:48.938+00><thread=11992 (0x2ED8)>
INFO: Prerequisite rule 'Windows Deployment Tools installed' will run for easysetup upgrade.  $$<Configuration Manager Prereq><01-10-2020 09:54:48.938+00><thread=11992 (0x2ED8)>
INFO: The rule 'Windows Deployment Tools installed' has been run on server 'SCCM-2012..*********', skipped.  $$<Configuration Manager Prereq><01-10-2020 09:54:48.959+00><thread=11992 (0x2ED8)>
INFO: Prerequisite rule 'Windows Preinstallation Environment installed' will run for easysetup upgrade.  $$<Configuration Manager Prereq><01-10-2020 09:54:48.959+00><thread=11992 (0x2ED8)>
Check if 'WinPE' component of latest ADK is installed on SCCM-2012..*********.  $$<Configuration Manager Prereq><01-10-2020 09:54:48.959+00><thread=11992 (0x2ED8)>
INFO: Found ADK 10 installed on SCCM-2012..********* at 'E:\Windows Kits\10\'.  $$<Configuration Manager Prereq><01-10-2020 09:54:48.959+00><thread=11992 (0x2ED8)>
INFO: 'Windows PE' component of ADK 10 is installed.  $$<Configuration Manager Prereq><01-10-2020 09:54:48.969+00><thread=11992 (0x2ED8)>
INFO: 'WinPE' component of ADK 10 is installed on <SCCM-2012..*********>  $$<Configuration Manager Prereq><01-10-2020 09:54:48.969+00><thread=11992 (0x2ED8)>
SCCM-2012..*********;    Windows Preinstallation Environment installed;    Passed  $$<Configuration Manager Prereq><01-10-2020 09:54:48.969+00><thread=11992 (0x2ED8)>
INFO: Prerequisite rule 'SMS Provider machine has same domain as site server' will run for easysetup upgrade.  $$<Configuration Manager Prereq><01-10-2020 09:54:48.985+00><thread=11992 (0x2ED8)>
SCCM-2012..*********;    SMS Provider machine has same domain as site server;    Passed  $$<Configuration Manager Prereq><01-10-2020 09:54:48.985+00><thread=11992 (0x2ED8)>
<<<RuleCategory: Site Upgrade Requirements>>>  $$<Configuration Manager Prereq><01-10-2020 09:54:49.000+00><thread=11992 (0x2ED8)>
<<<CategoryDesc: Checking if the target ConfigMgr site is ready to upgrade...>>>  $$<Configuration Manager Prereq><01-10-2020 09:54:49.016+00><thread=11992 (0x2ED8)>
***************************************************  $$<Configuration Manager Prereq><01-10-2020 09:54:49.016+00><thread=11992 (0x2ED8)>
******* Prerequisite checking is completed. *******  $$<Configuration Manager Prereq><01-10-2020 09:54:49.031+00><thread=11992 (0x2ED8)>
***************************************************  $$<Configuration Manager Prereq><01-10-2020 09:54:49.031+00><thread=11992 (0x2ED8)>

The key bits that stand out to me from the log:

FQDN

INFO: Prerequisite rule 'Primary FQDN' will run for easysetup upgrade.  $$<Configuration Manager Prereq><01-10-2020 09:54:48.860+00><thread=11992 (0x2ED8)>
INFO:CheckSupportedFQDNFormat <DB-Cluster-SQL..*********>  $$<Configuration Manager Prereq><01-10-2020 09:54:48.860+00><thread=11992 (0x2ED8)>
INFO: NetBIOS <DB01>  $$<Configuration Manager Prereq><01-10-2020 09:54:48.891+00><thread=11992 (0x2ED8)>
ERROR: Failed to get SQL instance  sub registry key from [DB-Cluster-SQL..*********]  $$<Configuration Manager Prereq><01-10-2020 09:54:48.891+00><thread=11992 (0x2ED8)>
DB-Cluster-SQL..*********;    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><01-10-2020 09:54:48.891+00><thread=11992 (0x2ED8)>

We are following the advice here -- using the name of the SQL Server cluster instance and not the virtual Windows server name. I don't see how we can use the "primary FQDN" of one of the two hosts while also following the MS advice. ?

However, this check does not appear to have failed in the GUI (is this the same check?):

Operating System Check

INFO: Prerequisite rule 'Unsupported site server operating system version for Setup' will run for easysetup upgrade.  $$<Configuration Manager Prereq><01-10-2020 09:54:48.438+00><thread=11992 (0x2ED8)>
CurrentVersion =   $$<Configuration Manager Prereq><01-10-2020 09:54:48.454+00><thread=11992 (0x2ED8)>
INFO: OS version:0, ServicePack:0.  $$<Configuration Manager Prereq><01-10-2020 09:54:48.454+00><thread=11992 (0x2ED8)>
DB-Cluster-SQL..*********;    Unsupported site server operating system version for Setup;    Error;    Configuration Manager site systems can only be installed on computers running supported operating systems. https://go.microsoft.com/fwlink/?linkid=841654  $$<Configuration Manager Prereq><01-10-2020 09:54:48.454+00><thread=11992 (0x2ED8)>

This appears to be another problem relating to this virtual hostname. Sysinternals Process Monitor reveals that at this stage, the prereq check is trying to access \\DB-Cluster-SQL.our-domain\PIPE\winreg.

• The Remote Registry service is running on the database hosts and has permissions that permit the user running the prereq check.
• Accessing the Remote Registry using \\DB-Cluster.our-domain\PIPE\winreg (the Windows cluster name, instead of -SQL) works fine.
• Other parts of the prereq check appear to use WMI on the DB-Cluster-SQL hostname to access the registry remotely and this works. When this check uses the named pipe instead (and the wrong hostname??), it fails.

The failure to access the registry appears to result in this prereq check believing we're running OS version 0 which is an "unsupported OS".

Around the internet, similar issues seem to point to remote registry service, or permissions on it, or permissions on the SQL Server, none of which don't seem to be our issue.

Does anyone have any ideas on how we might figure this out? We'd like to avoid completely changing our SQL Server infrastructure just to get past this when it's been working fine (including several SCCM upgrades previously)!

[anyweb]

I can check with the product group if you can wait on their reply ?

 

[hybrid]

I'd be very grateful!

[anyweb]

i've emailed them, let's see if they reply

[hybrid]

Possibly similar... the SMS_HIERARCHY_MANAGER's hman.log says:

The following port [1433,4022,] tcp firewall exception not active on SQL Server [DB-Cluster-SQL.*****].

At this exact time, the smsexec.exe with that same thread ID from hman.log above uses the named pipe to try and evaluate the firewall options on the wrong hostname again, just like the prereq check.

 

[anyweb]

no reply yet, i've emailed again...

[hybrid]

Don't try this at home -- obviously this is thoroughly unsupported.

I was able to use API Monitor to set a breakpoint on the RegConnectRegistryA API call being made by smsexec.exe and cmupdate.exe and patch the machine name that it's trying to connect to the registry at to point at DB-Cluster instead of DB-Cluster-SQL.

There were several calls to RegConnectRegistryA which caused the breakpoint to be hit. Each time, I expanded the string argument for lpMachineName and updated the value (fortunately a shorter string) to point to the correct machine.

The prereq check is now happy (albeit suggesting it's OS 6.3 i.e. Windows Server 2012 R2, which is perhaps because this is a legacy check?)!

We're obviously cagey about now doing the upgrade from this unsupported state, but I hope this demonstrates the issue really clearly — it is just this particular way of communicating with the registry on the SQL Server cluster that causes the prereq check to fail.

INFO: Prerequisite rule 'Unsupported site server operating system version for Setup' will run for easysetup upgrade.  $$<Configuration Manager Prereq><01-20-2020 10:16:43.071+00><thread=9968 (0x26F0)>
CurrentVersion = 6.3  $$<Configuration Manager Prereq><01-20-2020 10:16:48.468+00><thread=9968 (0x26F0)>
INFO: OS version:603, ServicePack:0.  $$<Configuration Manager Prereq><01-20-2020 10:16:48.484+00><thread=9968 (0x26F0)>
INFO: Target computer is a Windows server.  $$<Configuration Manager Prereq><01-20-2020 10:16:48.515+00><thread=9968 (0x26F0)>
DB-Cluster-SQL.xxxxxxxxxxxxxxxxx;    Unsupported site server operating system version for Setup;    Passed  $$<Configuration Manager Prereq><01-20-2020 10:16:48.515+00><thread=9968 (0x26F0)>

 

 

[hybrid]

A quick update on this — it seems likely that something is wrong with our SQL Server Cluster. I spun up a new one-node Failover Cluster to test this, and found that the PIPE\winreg endpoint did work on this new cluster. I think that makes it fairly clear that this should work and that the problem lies with our SQL Server cluster and not with ConfigMgr.

So, we will look at trying to fix the SQL Server Cluster!

[chrisjones123]

@hybrid you ever figure out how to get this working with the SQL Server cluster or what was the issue there?

[chrisjones123]

figure this out for anyone interested, found an article from 2012 that outlines some registry key changes you need to make on you cluster nodes.

https://forum.red-gate.com/discussion/15396/error-monitoring-clustered-sql-server

snippet taken from the article above.

Of the tests we conducted above the root cause of the short file name error during the Pre-req checks was found to be the fact that we were not able to remotely access the registry using the SQL Virtual name which we should have been able to do. On contacting Microsoft Support we were informed that there are known issues around NoRemap registry key needing to be set if you are using Network Name resource that is dependent on a separate new IP Address resource – see http://support.microsoft.com/?id=306985

The final solution was to add a new REG_MULTI_SZ registry key to BOTH cluster nodes called:-
NoRemapPipes to:-
HKLM\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters\

This key should contain the values of:-
WINREG
EVENTLOG
svcctl

After adding the above key and values we needed to reboot both cluster nodes and then we were able to connect to the SQL Virtual names (CLUSQL02 + CLUSQL01) using Regedit (Remote registry). Running the SCCM Pre –req checker now returns no errors.

Hope this soluton helps someone else.