Hi Roland, very well done.
Hi roland.meier3! How would you suggest to set up a lab environment for the user exclusion parameters (MOSTFREQUENTUSER_EXCLUSION, MOSTRECENTUSER_EXCLUSION, USER_EXCLUSION)? One of our customers is very diverse - they have a large variety of user names. Therefore, it is time consuming and error prone when modifying these paremeters, and then wait for the Data Update Job to run.
I cannot see all of the users in that system now, but my standard suggestion is to remove all non human/double users, such as administrators (%adm%), external users (%ext%), system users (%sys% and/or %srv%) and/or special accounts (%nologgedonuser% and/or all customer specific ones). These would then also not be taken into consideration for the most frequent and most recent users, thus would speed up the DUJ.
Additionally, when the lab/test environment does not require any user history, possible consider changing the user quarantine to delete all users that have not registered within a short period of time, for example 1 day or 1 week.
We have a customer that has a lot of subsidiaries, so their exclusion list is quite long. The pain point for me is trying to keep the exclusion list up to date and correct.
Right now the exclusion list looks like this:
The problem is that we still see users like this:
What I'm after is really a way of testing whether the exclusion list will match an unwanted user - I don't want to change the exclusion list, and then check the next day if it worked.
Hi Jonas!Just wondering if you ever resolved the issue of still seeing users like: ad.companyname.com\root and domain\_example?I am currently having the same issue despite having both %\[_]% and %\rootThanks,Gemma
Hi Gemma! We're using the following string, and are happy with it:
Thank you thank you thank you Roland! Been looking for this sort of information for a while.
Retrieving data ...