Bug 43683 - Add a hint about cleanup of AD DNS settings to rejoin a UCS system
Add a hint about cleanup of AD DNS settings to rejoin a UCS system
Status: CLOSED DUPLICATE of bug 43745
Product: Z_SDB
Classification: Unclassified
Component: New entries
unspecified
Other Linux
: P5 normal
: ---
Assigned To: Florian Best
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2017-03-01 12:22 CET by Nico Gulden
Modified: 2019-02-20 10:09 CET (History)
5 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 4: Minor Usability: Impairs usability in secondary scenarios
Who will be affected by this bug?: 3: Will affect average number of installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.137
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2017022421000167
Bug group (optional): External feedback
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nico Gulden univentionstaff 2017-03-01 12:22:57 CET
See user feedback at Ticket#2017022421000167.

Background: The user already had a UCS system joined into a Microsoft Active Directory domain. He deleted the system. The records in AD remained. The join of another system failed because of these left overs.

The forum has the solution: http://forum.univention.de/viewtopic.php?f=48&t=3889&p=14035#p14008

The documentation should be extended by a hint for testers to avoid a research and enable them to avoid this pitfall.
Comment 1 Arvid Requate univentionstaff 2017-03-07 11:31:57 CET
I'd rather see this in SDB.
Comment 2 Arvid Requate univentionstaff 2017-03-07 11:56:29 CET
To make this Bug findable in Bugzilla precise core keywords are essential:

If the SRV record _domaincontroller_master._tcp is already (or still) present in the DNS domain zone of the Active Directory nameserver, the setup of the AD connection (aka member mode) doesn't work.


We should improve the user experience though directly in the software to avoid this frustration factor right from the start. I've opened Bug 43745 for this.
Comment 3 Ingo Steuwer univentionstaff 2017-09-01 11:36:44 CEST
This happens fairly often, there are several reports on help.univention.com. Today we had a potential customer in sales with this problem.
Comment 4 Florian Best univentionstaff 2017-09-01 11:43:13 CEST
I think we will fix the real problem instead of showing a hint. Bug #42918
Comment 5 Florian Best univentionstaff 2017-11-06 17:30:43 CET

*** This bug has been marked as a duplicate of bug 43745 ***