Bug 36651 – Create DCs in cn=dc container by default

Bug 36651 - Create DCs in cn=dc container by default


Summary:	Create DCs in cn=dc container by default

Status:	RESOLVED DUPLICATE of bug 46919

Product:	UCS
Classification:	Unclassified
Component:	UMC - Computers
Version:	UCS 4.0
Hardware:	All Linux

Importance:	P5 normal (vote)
Target Milestone:	UCS 4.0-x
Assigned To:	UMC maintainers
QA Contact:

URL:
Keywords:

Depends on:	36644
Blocks:
	Show dependency tree / graph

Reported:	2014-11-13 16:05 CET by Philipp Hahn
Modified:	2019-03-10 16:28 CET (History)
CC List:	2 users (show)

See Also:	42904
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
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 Philipp Hahn

2014-11-13 16:05:42 CET

+++ This bug was initially created as a clone of Bug #36644 comment 1 +++

> > ldap_dn="cn=h72,cn=computers,dc=phahn,dc=pt"
> It should be cn=h72,cn=dc,cn=computers,dc=phahn,dc=pt"

Manually added DC should be created in the cn=dc container by default as this leads to strange bugs afterwards.

Comment 1 Stefan Gohmann

2019-01-03 07:17:29 CET

This issue has been filled against UCS 4.0. The maintenance with bug and security fixes for UCS 4.0 has ended on 31st of May 2016.

Customers still on UCS 4.0 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

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

Comment 2 Florian Best

2019-03-10 16:28:08 CET


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