Bug 44964 – No info regarding active directory takeover in domain settings

Bug 44964 - No info regarding active directory takeover in domain settings


Summary:	No info regarding active directory takeover in domain settings

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	UCS Installer
Version:	UCS 4.2
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2017-07-11 11:50 CEST by Stephan Luft
Modified:	2020-07-03 20:51 CEST (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	Feature Request
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 Stephan Luft

2017-07-11 11:50:47 CEST

If you are interested in migrating a Microsoft AD to UCS you will end up in our documentation (http://docs.software-univention.de/manual-4.2.html#windows:adtakeover). But this not clearly defines which domain settings you have to choose during the installation.

On the other hand there is no reference in the installation chapter (http://docs.software-univention.de/manual-4.2.html#installation:Dom%C3%A4neneinstellungen) to the AD Takeover.

The best and most user friendly solution (in my opinion) would be a separate selection in domain settings "Takeover an existing Active Directory Domain"

A new and interested IT system provider asked for the missing information and ended up in several attempts to achieve a takeover.

Comment 1 Ingo Steuwer

2020-07-03 20:51:20 CEST

This issue has been filed against UCS 4.2.

UCS 4.2 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.