LDAP not working with WS 2025 domain due to LDAP disable

**Bug description**
With Windows Server 2025 in a 2025 Domain Function Level LDAP is disabled and LDAP SSL is the only way.

So certain things like setspn does not work as it uses LDAP and not LDAP SSL. From a 2025 Computer the commands work fine but not from HCI 23h2.

**Repro steps**
Create a new 2025 domain and try setspn from a HCI node. The WSMAN spn records are not created. And setspn lookup or creation does not work,

**Expected behavior**
I expect that setspn and other LDAP functionality to work properly.

**Environment (please complete the following information):**
Latest 23h2 deployment with September patches.

**Screenshots**

Reproduce the failure by creating a Windows Server 2025 domain at the 2025 Domain Function Level and running setspn from an HCI 23H2 node. Compare the LDAP and LDAP SSL behavior; done means WSMAN SPN lookup and creation work, along with the other affected LDAP functionality.

Written by the indexing model from the issue text.