Unable to join second StoreFront server after upgrade, with error "Error getting replication keys"

Unable to join second StoreFront server after upgrade, with error "Error getting replication keys"

book

Article ID: CTX236738

calendar_today

Updated On:

Description

Follow are the symptoms:

1) StoreFront join operation fails with following error:

User-added image

2) If we enable Audit for logon failure and success, you will observer following event on the Joiner:

Log Name:      Security
Source:        Microsoft-Windows-Security-Auditing
Date:          XXXXXXXXXXXXXXXXXXX
Event ID:      4625
Task Category: Logon
Level:         Information
Keywords:      Audit Failure
User:         XXXXXXXXXXXXXXXXXXX
Computer:     XXXXXXXXXXXXXXXXXXX
Description:
An account failed to log on.
 
Subject:
                Security ID:                         NULL SID
                Account Name:                 -
                Account Domain:                              -
                Logon ID:                             0x0
 
Logon Type:                                       3
 
Account For Which Logon Failed:
                Security ID:                       NULL SID
                Account Name:                 XXXXXXXXXXXXXXXXXXX
                Account Domain:              XXXXXXXXXXXXXXXXXXX
 
Failure Information:
                Failure Reason:                 The user has not been granted the requested logon type at this machine.
                Status:                                  0xc000015b
                Sub Status:                         0x0
 
Process Information:
                Caller Process ID:              0x0
                Caller Process Name:      -
 
Network Information:
                Workstation Name:         -
                Source Network Address:             -
                Source Port:                       -
 
Detailed Authentication Information:
                Logon Process:                  Kerberos
                Authentication Package:               Kerberos
                Transited Services:          -
                Package Name (NTLM only):        -
                Key Length:                        0
 
This event is generated when a logon request fails. It is generated on the computer where access was attempted.
 
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
 
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
 
The Process Information fields indicate which account and process on the system requested the logon.
 
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
 
The authentication information fields provide detailed information about this specific logon request.
                - Transited services indicate which intermediate services have participated in this logon request.
                - Package name indicates which sub-protocol was used among the NTLM protocols.
                - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.

Configuring Audit Policy: https://technet.microsoft.com/en-us/library/dd277403.aspx
4625(F): An account failed to log on: https://docs.microsoft.com/en-us/windows/security/threat-protection/auditing/event-4625

3) Store creation may also fail with the above error.
4) If we enable StoreFront verbose logs and check the Debug view logs, we will find error "Error getting replication keys" on the Authorizer.

How to Enable StoreFront Verbose Logging: https://support.citrix.com/article/CTX139592

Resolution

The policy "Access this computer from the network" with location "Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment", needs to have at least following groups by default:

Everyone
Administrators
Users
Backup Operators

The following table lists the actual and effective default policy values for the most recent supported versions of Windows. Default values are also listed on the policy’s property page.
 
Server type of GPODefault value
Default domain policyNot defined
Default domain controller policyEveryone, Administrators, Authenticated Users, Enterprise Domain Controllers, Pre-Windows 2000 Compatible Access
Stand-alone server default settingsEveryone, Administrators, Users, Backup Operators
Domain controller effective default settingsEveryone, Administrators, Authenticated Users, Enterprise Domain Controllers, Pre-Windows 2000 Compatible Access
Member server effective default settingsEveryone, Administrators, Users, Backup Operators
Client computer effective default settingsEveryone, Administrators, Users, Backup Operators

Access this computer from the network - security policy setting: https://docs.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/access-this-computer-from-the-network

Problem Cause

This issue occurs because the Authorizer is unable to logon to the Joiner with logon type as Network (3), to update the Joiner that the Authorizer was able to configure itself. This is basically a Windows Communication Foundation (WCF) Authentication failure, which is captured by Audit logon failure event in security log mentioned in the symptoms. 

Issue/Introduction

Unable to join second storefront server after upgrade, with error "Error getting replication keys"