LDAP not working with WS 2025 domain due to LDAP disable

Open
#11 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
azure

Research direction

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.

Description

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
image

Dominant language
PowerShell
Stars
78
Forks
60
Avg merge
1d 6h
Merged PRs (30d)
5

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/AzureLocal-Supportability

All issues in Azure/AzureLocal-Supportability

Similar issues

More Security issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.