Welche Auswirkungen hat die Kennungsverschmelzung für die Nutzung von Diensten durch die einzelnen Benutzer?

A distinction must be made here as to which of the two accounts - the LMU user ID or the LRZ account - continues to exist after the merger, i.e. is the "winning account". 

  • If the service is attached to the "winning account", nothing changes. For example, the "winning account" is always the LRZ account if it has Exchange permission.
  • If the service is attached to the LMU user ID and it is an LMU-internal service, the login is done as before with the LMU user ID (i.e. usually with firstname.lastname). 
    However, the password may change to the password of the previous LRZ account (if this is the login account for PCs or Exchange). In this case, the users are explicitly informed of this in the announcement e-mail.
  • If the service is connected to the "loser account", the login is carried out with the new LMU/LRZ account and the password taken over from the "winner account". 
    This affects the services provided at the LRZ:
    • Cloud Storage, Sync+Share, GitLab or CampusLMU Mailbox if the LMU user ID is the "loser account",
    • Standard Mail, if the LRZ account is the "loser account".

N.B.: The Personal Cloud Storage service has previously been assigned to both LRZ accounts and LMU user IDs, and therefore a user may have permission on both accounts. In such cases, the personal storage area that previously belonged to the LMU user ID is automatically moved to a subdirectory called "Backup account" of the other storage area.

Institutional Cloud Storage: If access rights to Shares (project storage) were assigned directly to accounts instead of (ADS)-groups, previous permissions in the storage for the "loser account" must also be entered for the respective "winner account" before the account merge.

Good to know: In (ADS)-groups, all "loser accounts" as members are automatically replaced by the respective winner accounts as members.