welcome to UCS@school. I guess it is very difficult to work with it, all the documentation being in German. Please keep the tone civil, as there is a good reason for everything and a solution to most problems. I will try to help you importing the users.
The first thing I need to better understand your problems is information:
- What version of UCS and UCS@school are you using? The command
univention-app info returns that information.
- How did you try to import users? Did you use the graphical UMC module or the command line tools?
- Where does the CSV come from? Will the source database be updated regularly, requiring a regular import → update of the users in UCS?
- It seems you wish to use the gapps connector. Should all users be synced to google or do you wish to select a group etc?
In http://docs.software-univention.de/ucsschool-import-handbuch-4.2.html#configuration:mapping there is an example of a CSV file. As classes are really groups, they must be unique throughout a domain. That is why their names are constructed like this:
<school name>-<class name>. To import a user into multiple classes (and possibly multiple schools), separate the class names by comma:
If you import a user into classes of multiple schools, you must list those schools in the
schools column of the CSV file. But the UMC module for CSV-import does currently not support users in multiple schools. You'd have to use the command line tools for that.
The email address (UDM attribute
mailAddress) will be set as the email address of that group in the google directory.
The gapps connector only syncs groups if the UCR variable
google-apps/groups/sync is enabled. If you change that after creating groups, they won't be synced. You can trigger the listener to resync all groups by running
univention-directory-listener-ctrl resync google-apps-group.
It is possible to import those. You'd have to use the new import script
/usr/share/ucs-school-import/scripts/ucs-school-user-import It can set all possible UDM attributes. The mapping of CSV columns to user attributes is defined in a JSON file.
It is however much safer and probably also much easier to let UCS@school create the users with fresh UIDs and unix homes and then move and chown existing user data into the new directories.
In UCS@school the directories used for user homes are separated by school name (OU) and user type. I don't think this is still strictly necessary, but I am not certain.
To import groups, there is a
import_group script in
The three email fields serve different purposes:
- Primary e-mail address (mailPrimaryAddress): the users mailbox, must be unique and the domain must be registered as mail domain in UCS → will be served if the mailserver app is installed
- Alternative e-mail address (mailAlternativeAddress): list of aliases, all mails to those addresses listed here will be delivered to the users mailbox (primary address), does not need to be unique but the domain must be registered as mail domain in UCS
- contact → E-mail address: a list of contact email addresses, can be external domains, just for the address book - will not be served by a UCS mailserver
- google email: that is the login for gapps. It is derived from the mailPrimaryAddress but the domain can be different, because its domain must be the one registered with google.
Four different purposes → four different fields.
You can - see above.