Bug 34794 – Maintain all client settings in LDAP and don't rely on PXE boot settings

Bug 34794 - Maintain all client settings in LDAP and don't rely on PXE boot settings


Summary:	Maintain all client settings in LDAP and don't rely on PXE boot settings

Status:	NEW

Product:	Z_Univention Corporate Client (UCC)
Classification:	Unclassified
Component:	General
Version:	unspecified
Hardware:	Other Linux

Importance:	P5 enhancement
Target Milestone:	UCC 2.x
Assigned To:	UCC maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:	30392
	Show dependency tree / graph

Reported:	2014-05-09 14:18 CEST by Moritz Muehlenhoff
Modified:	2015-11-23 17:14 CET (History)
CC List:	1 user (show)

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):	Roadmap discussion (moved)
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 Moritz Muehlenhoff

2014-05-09 14:18:12 CEST

Some options are currently configurable via PXE options; a series of PXE UCR settings allow the configuration of the bootsplash.

Some of these settings are changes based on what we implemented in UCS TCS and which were ported to UCC 1.0. UCC how grown several features and we should streamline the whole boot options approach in a future release.

UCC can also be updated if not booting from PXE (e.g. if the BIOS has been reconfigured to not use PXE or with the new local boot option in UCC 2.0). But in such cases the client potentially behaves differently depending on whether booted per PXE (where the PXE UCR variables are set) and via local boot (where these settings are not present). In that case we would only have a rollout via PXE and everything else (updates, regular boot) would be identical.

We should configure all these settings via the LDAP. That way we have fixed boot behaviour independent of the startup method. It also allows to simplify the boot options available in the UMC and make the configuration of the UCC client more user-friendly (if it's available in the UMC).