vSphere 7.0 Join AD Error Code 1225

This post is applicable to customers using VMware vSphere 7.0 trying to join AD 2016 running on Windows Server 2019.

Problem:

  1. When trying to join AD from vCenter Server 7.0 via the vSphere Client, the error message “lcm client exception: Error trying to join AD, error code [1225], user [xyz], domain [xyz], orgUnit [xyz]” is reported. When using the “/opt/likewise/bin/domainjoin-cli join <domain> <user>” command, the error message “ERROR_CONNECTION_REFUSED code 0x4c9” is reported. The same domainjoin-cli message is also reported by ESXi. Note that 1225 is 0x4c9 in hexadecimal.

Solution:

  1. The AD Windows Servers need to have the Network Ethernet properties set to include the “Client for Microsoft Networks” and “File and Printer Sharing for Microsoft Networks” options enabled.
  2. Execute the Join AD procedure again and it will complete successfully.

Background:

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Website Powered by WordPress.com.
%d bloggers like this: