RN version 7.0.21248.1

Published: KW 24.2021

General notice:

Implementation of an interface for importing / exporting data owner information in the migRaven Database for the connection of IAM systems. If you have any questions, please contact our support.

Rich clients:

changes:

AD Scan: Extension of the Active Directory attributes that are read in by the AD Scan. The following attributes are used by migRaven read in:

• name
• cn
• distinguished name
• objectGUID
• objectSID
• sAMAccountName
• sAMAccountType
• group type
• useraccountcontrol
• accountExpires
• givenName
• lastLogon
• lastLogonTimestamp
• primaryGroupID
• sn
• ADsPath
• userPrincipalName
• Description
• display name
• whencreated
• when changed
• sIDHistory
• department
• proxyAddresses
• manager
• employeeID
• title
• ou
• company
• info
• departmentNumber
• division
• telephoneNumber
• mobile devices
• roomNumber
• mail
• employeeNumber
• employeeType

Fixed bugs:

File server scan: Fixed an error in which data owner assignments to a directory were not correct in the database if the directory can be reached via two different DFS paths. The correct assignment is now guaranteed and the data owner is assigned to the directory, regardless of the path via which in migRaven is navigated.

Web client:

changes:

Data owner configuration: The dialog for setting a data owner on a directory has been revised. The dialog is now a sidebar and offers a complete history of the changes. It can therefore at any time from migRaven Administrator can see who has added or removed which data owner. The last three changes are displayed in the sidebar itself. The complete history can be viewed by clicking on "Show history". (2562)



Scenario analyzes (explanation also in Release Notes Version 6.9.2120x.1 ):
Various small improvements and enhancements, among others

• Central filter (3554)
• Renaming of the "Release" column to "Description" (3781)
• Adjustment which columns are displayed in the standard. (3803)
• Installation of the option to sort the table according to status (traffic light). In addition, after loading the table is automatically sorted according to the status of the traffic light, in the order red (error), yellow (warning) and green (ok). (3819)
• Extension by the column "Last change". The date of the last change to the directory manager or the tasks is displayed here. (3823)
• Task analysis: Extension of the columns "Dependent applications", "Migration path" and "Original path". The “Original Path” column shows the path where the directory was when the task was created. Thus, in connection with the "UNC path" column, it can be identified whether the directory has been renamed or moved. (3995)

Fixed bugs:

• Data retention: Implementation of an additional way of reading the authorizations of the source system and, if configured accordingly, of copying them to the target system. In rare cases the authorizations in the source could not be read with the previous implementations and an empty ACL was written on the target directory. (3365)
• Folder Self-Service: Fixed a typo in the e-mail notification when a directory was deleted via the desktop client. (3932)
• Directory Tasks: Fixed a bug that prevented new tasks from being created or existing tasks not being able to be edited. (4013)
• Directory tasks: Fixed a bug that caused the original creator of a task to be entered as the last editor, although the tasks were edited by another user. (4025)
• Directory tasks: Fixed a bug that prevented a task from being created if a migration path was entered when it was created. (4034)

Known bugs:

• Obsolete data analysis: The obsolete data analysis can display incorrect data if a symlink is contained in the project directory (3202)
• No distinction is made between the data statuses in the productive directory area and the data in the archive area. This may lead to inaccurate evaluations of the data age.
• Web client: The pinned navigation menu overlays the content of the page (3201)
• Data retention: If a directory should be deleted according to the "archiving job" and a "thumbs.db" file is in the corresponding directory, the corresponding directory may not be deleted. This is always the case when the thumbs.db is blocked by a process.
• Data Retention: It is possible that the corresponding directory is not deleted when the DR workflow is carried out, although the option has been selected.
  Workaround: After archiving, delete the directory directly via the desktop client.
• HTTPS binding in IIS configuration: When updating to a newer version, a second HTTPS binding is entered in IIS. As a result, the website cannot start.
  Solution: Remove the HTTPS binding without a certificate in the IIS configuration.
• AD Scan: In older versions it can happen that the group of administrators is saved in the database with the wrong SID "S-1-5-32-54" instead of the correct SID "S-1-5-32-544" became. The error has been corrected, but may have to be corrected manually in the database in existing installations. Our support will be happy to assist you with this.