Bug 27548 – UCS@school 3.0 Slave DCs registrieren sich als PDC und GC bei samba3upgrade

Bug 27548 - UCS@school 3.0 Slave DCs registrieren sich als PDC und GC bei samba3upgrade


Summary:	UCS@school 3.0 Slave DCs registrieren sich als PDC und GC bei samba3upgrade

Status:	RESOLVED WONTFIX

Product:	UCS@school
Classification:	Unclassified
Component:	Samba 4 - Slave PDC
Version:	UCS@school 3.0
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2012-06-12 12:52 CEST by Arvid Requate
Modified:	2019-02-05 21:49 CET (History)
CC List:	0 users

See Also:
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 Arvid Requate

2012-06-12 12:52:17 CEST

In einer Umgebung, in der per samba3upgrade die UCS@school 3.0 Slave DCs auf Samba4 upgedated wurden (Anleitung an Bug 27027), sind für jeden Slave die PDC und GC SRV/CNAME-DNS-Records gesetzt. Ich vermute, dass samba-tool samba3upgrade das macht. AD-konform sollte nur ein System die PDC und GC-Rolle haben.

Comment 1 Sönke Schwardt-Krummrich

2019-02-05 21:49:47 CET

This issue has been filled against UCS@school 3. The maintenance with
bug and security fixes for the last UCS@school version for UCS 3.x 
(→ UCS@school 3.2) has ended on Dec 31, 2016.

Customers still on UCS 3.x are encouraged to update to UCS 4.3 (or later). 
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.