Bug 47075 – AD member join: Wrong password error with Windows Server 2012 R2 domain

Bug 47075 - AD member join: Wrong password error with Windows Server 2012 R2 domain


Summary:	AD member join: Wrong password error with Windows Server 2012 R2 domain

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	AD Connector
Version:	UCS 4.3
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	Samba maintainers
QA Contact:	Samba maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2018-05-25 10:10 CEST by Nico Gulden
Modified:	2021-05-14 16:34 CEST (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	6: Setup Problem: Issue for the setup process
Who will be affected by this bug?:	2: Will only affect a few installed domains
How will those affected feel about the bug?:	4: A User would return the product
User Pain:	0.274
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2018052321000152
Bug group (optional):	Appliance, Error handling
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Nico Gulden

2018-05-25 10:10:44 CEST

The join into an existing AD domain provided by Windows Server 2012 R2 does not work. Error message said the password was wrong, which was not according to the user.

The join was executed from the installer / system setup with UCS 4.3.

Comment 1 Erik Damrose

2018-05-25 12:02:18 CEST

Need more info: English or german W2k12r2?
Installed from ISO, UCS Appliance or App Appliance?
Was there already a UCS Master joined into the AD (the ticket mentions a 'member' server)?

Comment 2 Nico Gulden

2018-05-28 09:35:48 CEST

* The Windows system was setup in German.
* The UCS system was installed from ISO image.
* It could be possible that another UCS master already was joined. I cannot be excluded 100% and it cannot be validated 100% for the moment.

Comment 3 Ingo Steuwer

2021-05-14 15:13:12 CEST

This issue has been filed against UCS 4.3.

UCS 4.3 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.