Windows server 2019 failover cluster validation issue

Charles Thivierge 4,171 Reputation points
2021-02-10T08:50:57.86+00:00

We are using Windows Server 2019 Failover Cluster for SQL AlwaysOn. There is no shared disks in the cluster.
The failover cluster validation takes long time to finish but it seems to be related to the software update validation.

Our servers does not have access to Internet but they are able to resolve DNS name.

Is that possible in this case that the software update validation step during the failover cluster creation could takes longer time that is supposed to ?

I can see in network traces i've took on the cluster nodes that they try to reach several MSFT sites and because my server does not have access to Internet, it takes a while to complete the failover cluster validation. As you can see in the next image, the server is not able to connect to Internet but the validation process try to reach update.microsoft.com (and many other MSFT web sites).

66342-failoverclustervalidation.png

Is there a way to reduce the number of retry if Internet is not available ?

Thanks!

Windows for business | Windows Server | Storage high availability | Clustering and high availability
Windows for business | Windows Server | User experience | Other
{count} votes

Accepted answer
  1. Xiaowei He 9,936 Reputation points
    2021-02-15T02:42:14.45+00:00

    Hi,

    If i add the following registry key, the validation is a lot faster
    reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v DoNotConnectToWindowsUpdateInternetLocations /t REG_DWORD /d 1 /f

    Thanks for sharing the information with us.

    But my question is if we add this configuration on our server and the validation pass. Does the cluster is still supported?

    As far as I'm concerned, the registry key won't affect the cluster creation. The cluster is still supported. While if we add the registry key, it's recommended to update the cluster nodes manually.

    Thanks for your time!
    Best Regards,
    Anne

    -----------------------------

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

2 additional answers

Sort by: Most helpful
  1. Xiaowei He 9,936 Reputation points
    2021-02-11T02:38:24.983+00:00

    Hi,

    Is that possible in this case that the software update validation step during the failover cluster creation could takes longer time that is supposed to ?

    If we run Cluster validation before creating the cluster, when creating the cluster, we may skip the validation, so that we may not worry about the validation takes a long time in cluster creation.

    Is there a way to reduce the number of retry if Internet is not available ?

    As far as I know, we may not have a method to increase the time to run validation. As a workaround, we may uncheck the update settings in cluster validation.

    66749-image.png

    Thanks for your time!
    Best Regards,
    Anne

    -----------------------------

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  2. Charles Thivierge 4,171 Reputation points
    2021-02-11T04:18:42.46+00:00

    Thanks for the answer.

    It's weird that this is only happening with the Windows 2019 Core edition. I've done a test with the same Windows updates parameters with a 2-nodes cluster (Windows 2019 Core Edition) and a 2-nodes cluster (Windows 2019 Full Desktop experience)

    The Windows 2019 Full desktop experience takes about 1 to 2 min to complete the validation steps
    The Windows 2019 Core takes more than 12 min to complete the validation steps.

    If i add the following registry key, the validation is a lot faster
    reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v DoNotConnectToWindowsUpdateInternetLocations /t REG_DWORD /d 1 /f

    But my question is if we add this configuration on our server and the validation pass. Does the cluster is still supported ?

    Thanks!

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.