Name Change Not Synchronized
Problem
A name change was made in the metadata. OneOffixx still displays the old/incorrect name. What could be the cause?
Solution
- The AD synchronization ensures that user fields in OneOffixx are populated with the current data from Active Directory.
There is a somewhat inconvenient behavior here that has been improved. The JobHost runs the AD sync for all users daily at 4:30 AM. Each user receives the current timestamp during AD sync. An additional setting in UserSync checks whether the user's timestamp is older than a certain interval – where the default is exactly one day. This causes approximately one quarter of users to be skipped by the AD sync each day.
Solution: Set the interval to half a day, which resolves this problem. - UserName
The UserName, displayed in the client with the label "AD User", behaves somewhat differently from the editable user fields. This has caused clients in the current version 3.8.10100 to not detect the change. Only by resetting the data source is the UserName updated.
Solution: This behavior is fixed in OneOffixx version 3.8.10110. - Profile Name
The profile name is yet another kind of "field". An automatic adjustment is practically impossible here. With only one profile that is never renamed, this is not easily noticed. It becomes clearer with an example involving multiple or renamed profiles. If you created a profile with the name "My Personal Profile" and change your name once, you probably don't want it to be reset to the default. If you have 10 profiles, they would all have the same name after a name change and you would lose track of their purposes.
→ Therefore, no adjustment to the software or configurations is expected here.