Converge Domain Pre-check might fail when PSC is added to child domain
search cancel

Converge Domain Pre-check might fail when PSC is added to child domain

book

Article ID: 321261

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

Symptoms:
When adding a Platform Services Controller (PSC) to a child domain, you experience these symptoms:
  • The Converge Pre-check fails.
  • You see the errors similar to:

    2019-05-06 11:34:55,526 - vCSACliConvergeLogger - ERROR - PSC is joined to AD Identity store: ssolabs.com
    2019-05-06 11:34:55,526 - vCSACliConvergeLogger - INFO - ================ [FAILED] Task: PrecheckSameDomainTask: Running PrecheckSameDomainTask execution failed at 11:34:55 ================
    2019-05-06 11:34:55,531 - vCSACliConvergeLogger - DEBUG - Task 'PrecheckSameDomainTask: Running PrecheckSameDomainTask' execution failed because [ERROR: Template AD info not correct.], possible resolution is [Refer to the log for details]
    2019-05-06 11:34:55,531 - vCSACliConvergeLogger - INFO - ================================================================================
    2019-05-06 11:34:55,692 - vCSACliConvergeLogger - ERROR - Error occurred. See logs for details.
    2019-05-06 11:34:55,692 - vCSACliConvergeLogger - DEBUG - Error message: com.vmware.vcsa.installer.converge.prechecksamedomain: ERROR: Template AD info not correct.

    2019-05-06 11:34:55,693 - vCSACliConvergeLogger - INFO - =================================== 11:34:55 ===================================
    2019-05-06 11:34:55,696 - vCSACliConvergeLogger - INFO - Result and log file information...
    2019-05-06 11:34:55,697 - vCSACliConvergeLogger - INFO - WorkFlow log directory: C:\Users\pdpuser\AppData\Local\Temp\vcsaCliInstaller-2019-05-06-11-34-i_lr2z_n\workflow_1557142468027


    Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.


Environment

VMware vCenter Server 6.7.x
VMware vCenter Server 6.5.x

Resolution

This is a known issue affecting VMware vCenter Server 6.5.x and 6.7.x.

Currently, there is no resolution.

Workaround:
To work around this issue:

Performing convergence operation using the User Interface (UI)

  1. Check the option "Skip Domain Join" .
  2. After the converge, join the vCenter Server to the domain manually.
  3. Reboot the vCenter Server Appliance (VCSA).

Performing Converge operation using the Command Line Interface (CLI)

  1. While performing convergence operation using CLI, pass the argument "--skip-domain-handling".
  2. After the converge, join the vCenter Server to the domain manually.
  3. Reboot the vCenter Server Appliance (VCSA).