Univention Bugzilla – Bug 41515
User gets only materials from his original ou
Last modified: 2016-06-28 18:24:52 CEST
If a user is in more than one school he should be able to get material from multiple schools. But the user can only see material from his ou. Material gets copied into his my files share which only seems to exists for his ou. Tested on a Win8 client
If the user logs in at another school, it reuses the home share of the first school. We have bug 41396 do document home shares per school (in this case, file distribution will work as expected). Have you tested with a second windows client, that has been joined against a second school server for the second school?
(In reply to Sönke Schwardt-Krummrich from comment #1) > If the user logs in at another school, it reuses the home share of the first > school. We have bug 41396 do document home shares per school (in this case, > file distribution will work as expected). > > Have you tested with a second windows client, that has been joined against a > second school server for the second school? My setup: User under ou=schoolA with: ucsschoolSchool=SchoolA ucsschoolSchool=SchoolB The user logs into a windows client from schoolB. The user now see his home share from schoolA (as you said). The problem is material gets copied into his home share but only from schoolA. If a teacher from schoolB gives the user material it doesn't seem to be copied into the users home share on schoolA. Expected behavior in my opinion: The user should see the material assigned to him from both schools no matter if logged in on schoolA or schoolB.
(In reply to Jürn Brodersen from comment #2) > If a teacher from schoolB gives the user material it doesn't seem to be > copied into the users home share on schoolA. This is the intended behaviour. > Expected behavior in my opinion: > The user should see the material assigned to him from both schools no matter > if logged in on schoolA or schoolB. There will be 3 scenarios described in UCS@school admin manual that explain side effects of ou-overlapping user accounts: 1) One specific home share at "primary" school (Currently your tested default) There is only one home share on the fileserver of the "primary" OU. Files distributed in the primary school ("schoolA" in your case) will be correctly saved in the users home directory. Files distributed in any other school will not be saved in the users homedirectories. Pro: same files in home share in every school Con: file distribution in Distribution or Exam module does not (always) work 2) One specific home share on a central file server A hook script sets the home directory always to a specific URN on a central file server. In this scenario distributed files will never be saved in the users home directory. Pro: same files in home share in every school Con: file distribution in Distribution or Exam module does not work 3) One home share per school In this scenario, the file server of each school serves a separate home share. Pro: file distribution in Distribution or Exam module always works Con: having same files in home share in every school is not possible
Scenario 1 also means that a teacher from ou=schoolA can't see the mater
(In reply to Jürn Brodersen from comment #4) > Scenario 1 also means that a teacher from ou=schoolA can't see the mater Sorry Scenario 1 also means that a teacher from ou=schoolA can't see the material that was assigned for students from schoolB. I think we should at least add a warning there. Maybe it would be possible to add the home shares from the other schools as a normal network drive?
(In reply to Jürn Brodersen from comment #5) > (In reply to Jürn Brodersen from comment #4) > > Scenario 1 also means that a teacher from ou=schoolA can't see the mater > > Sorry > > Scenario 1 also means that a teacher from ou=schoolA can't see the material > that was assigned for students from schoolB. > > I think we should at least add a warning there. > > Maybe it would be possible to add the home shares from the other schools as > a normal network drive? On your DC Slave accidently all school were shown while only local school should be shown. svn r70084 fixed this. So it's not possible anymore to distribute materials at different schools. Put the user into a school class or working group of the local school to give him materials.
(In reply to Florian Best from comment #6) > (In reply to Jürn Brodersen from comment #5) > > (In reply to Jürn Brodersen from comment #4) > > > Scenario 1 also means that a teacher from ou=schoolA can't see the mater > > > > Sorry > > > > Scenario 1 also means that a teacher from ou=schoolA can't see the material > > that was assigned for students from schoolB. > > > > I think we should at least add a warning there. > > > > Maybe it would be possible to add the home shares from the other schools as > > a normal network drive? > > On your DC Slave accidently all school were shown while only local school > should be shown. svn r70084 fixed this. So it's not possible anymore to > distribute materials at different schools. Put the user into a school class > or working group of the local school to give him materials. I'm not exactly sure what that should have changed here? A teacher from ou=schoolA can still distribute material on schoolB (if the teacher has ucsschoolSchool=schoolB). My Problem was that the material gets than collected into schoolB but the teacher only sees collected material from schoolA. As discussed with Sönke the solution for now will be to to deactivate the module for the teacher on schoolB (done by the admin).
@Florian: In Jürn's scenario, the teacher "a.teacher" is enabled for school A and school B (ucsschoolSchool=schoolA, ucsschoolSchool=schoolB). The primary OU of the teacher is school A so, the home directory of a.teacher is /home/schoolA/teacher/a.teacher/ and the samba home path is \\dcschoolA\a.teacher. If a.teacher logs on on dcschoolB and distributes files to a class of school B and collects the results afterwards, the distribution module copies the results to the UNIX directory dcschoolB:/home/schoolA/teacher/a.teacher/. If a.teacher opens his home directory via windows client, the win client connects directly to \\dcschoolA\a.teacher. So, the relevant data is placed on dcschoolB but is not accessible via SMB. → for now, we are suggesting, that the affected UMC modules are deactivated if home directories are not configured "per site" (see Bug 41396).
UCS@school 4.1 R2 has been released: http://docs.software-univention.de/release-notes-ucsschool-4.1R2v1-de.pdf If this error occurs again, please use "Clone This Bug".