Hi Dojo,
Spotted a group of local users that will need credentials redefined - handling this outside of DM,
since these security criteria are defined at OS/GPO layer - but I would like to retrieve some more info on the midnight sync: how many times the DMS routine will attempt synchronizing a given user?
In the example below, the alarm console is reporting a failed attempt every minute or so, after the first midnight sync over the "uto2" user (only DMA1 is reporting this): notices are no longer generated after 1 hour or so - can this be configured in DM? E.g. so that when the first SYNC is unsuccessful, the notice is produced but the DMS will stop trying more times?
The "culprit" group of users isn't that big (30-40 local users - we are addressing this), yet if nearly ~70 attempts are done for each single account, and each one is generating a notice, we end up with a list of events that is quite big - hence checking if I can tune this in our system (running DM v 10.5-CU4).
Any steer will be helpful - thanks
Hello Alberto,
Apologies for the delayed response.
At a first glance, it’s not entirely clear why you are seeing so many repeated notices, all related to the same user and DMA. My initial assumption is that the number of agents in the DMS could be influencing this. For instance, if there are 20 agents and they all attempt to synchronize the same user to the agent where the user is missing, it could theoretically result in up to 19 creation attempts, although it’s unclear how this would escalate to 70 attempts per user !?
Is this still happening?
If so, I would consider opening a ticket with our TechSupport team so that we can investigate further.
Cheers,
Paulo