trn
July 18, 2020, 11:43am
12
Interesting information here from AlanM
Bump?
This isn’t the the thread I saw, but does note the bug
Alan,
It does correctly work if done in the client context via Fixlet Debugger – the info above is from Fixlet Debugger in Client Context.
The results however also mirror what I’m seeing in my analyses:
[image]
The relevance from the domain groups column is:
(name of it, names of groups of it) of (logged on users of active directory)
Bill
This is the post I recalled, and agrees with the problems I have had (on more recent version of the client) with the cached information being removed on clients that can’t see a DC when they query AD
How can I test for the condition where the AD cache has been overwritten and the cache file for the logged on user has the error message:
Failed to get attribute "distinguishedName" : Windows Error 0x8007054b: The specified domain either does not exist or could not be contacted.
It appears that this relevance may work:
concatenation of (unique values of values of components whose (type of it="CN") of distinguished names (distinguished names of (groups of local users of active directory))) != …