Bug 43020 - Exclude teacher's computer from exam mode
Exclude teacher's computer from exam mode
Status: RESOLVED WONTFIX
Product: UCS@school
Classification: Unclassified
Component: UMC - Exam mode
UCS@school 4.1 R2
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS@school maintainers
:
Depends on:
Blocks: 44157 49629
  Show dependency treegraph
 
Reported: 2016-11-21 15:20 CET by Jan Christoph Ebersbach
Modified: 2019-06-12 09:06 CEST (History)
2 users (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?: Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Christoph Ebersbach univentionstaff 2016-11-21 15:20:28 CET
A customer reported that the teacher's computer is also affected by exam mode preparations and limitations.  It would be helpful if it could be excluded from GPOs and other configurations.
Comment 1 Sönke Schwardt-Krummrich univentionstaff 2016-11-22 10:03:14 CET
The current problem is, that teacher computers are not specially tagged in LDAP. So there is at the moment no possibility to automatically detect a teacher's computer and exclude it automatically from all restriction.

But the GPOs are assigned via a GPO security filter and a group membership. I haven't checked it yet, but it should be possible to add an exception to the security filter to exclude explicitly defined teacher computers from that exam GPO. This way, only the internet and share filters are applied to the teacher.
Comment 2 Sönke Schwardt-Krummrich univentionstaff 2019-02-05 21:43:43 CET
This issue has been filled against UCS@school 4.1 (R2). The maintenance with
bug and security fixes for UCS@school 4.1 (R2) has ended on 5th of April 2018.

Customers still on UCS 4.1 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.