Bug 50568 - UCR Variable ucsschool/exam/windows_profile_path is without effect
UCR Variable ucsschool/exam/windows_profile_path is without effect
Status: RESOLVED WONTFIX
Product: UCS@school
Classification: Unclassified
Component: UMC - Exam mode
UCS@school 4.4
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS@school maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2019-11-27 09:48 CET by Christina Scheinig
Modified: 2023-10-26 14:44 CEST (History)
2 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?: 3: Will affect average number of installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.103
Enterprise Customer affected?:
School Customer affected?: Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2019112621000866
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 Christina Scheinig univentionstaff 2019-11-27 09:48:44 CET
THe ucr variable 'ucsschool/exam/windows_profile_path' is without effect

ucsschool/exam/windows_profile_path: <empty>
Specifies the source path of windows profiles for exam users.

The customers wish:
Unfortunately, this variable has never worked for me before, but I would love to use an empty string as profile path for exam users, so that they get normal local user profiles on their computers. Instead, the same profile path is used as for normal users (from ucsschool/import/set/serverprofile/path). It would be nice if this were fixed in an upcoming release.


We have this Issue for a long time:
See also Bug 36002
Comment 1 Jan-Luca Kiok univentionstaff 2023-10-26 14:44:05 CEST
This issue has been filed against UCS@school 4.4.

UCS@school 4.4 is out of maintenance and components may have vastly changed in later releases. Thus, this issue is now being closed.

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