(imported topic written by JamesN91)
Lets say you have Domain Toyota.
There are within Toyota OU’s of Tundra, Camry, Supra.
How can I write analysis to only target OU Tundra of Toyota?
(imported topic written by JamesN91)
Lets say you have Domain Toyota.
There are within Toyota OU’s of Tundra, Camry, Supra.
How can I write analysis to only target OU Tundra of Toyota?
(imported comment written by MattBoyd)
Would something like this work for you?
(it as uppercase ends with "OU=CAMRY,DC=TOYOTA" OR it as uppercase ends with "OU=TUNDRA,DC=TOYOTA") OF (distinguished name of local computer of active directory)
I’m considering buying a Tundra. I love Toyota.
(imported comment written by JamesN91)
Thank you
I tried that and plugged in my propper domain info into the debugger.
I get this error…
Error: No inspector context.
(imported comment written by MattBoyd)
Yeah I got that too when I tried it on the latest version of the relevance debugger (7.2.5.22) … but when I tried using the previous version (7.2.1.357) it worked fine…
I thought it might have something to do with the fact that I’m running a Win7 x64 machine, but maybe that’s not it. Either way, that relevance should work…
(imported comment written by jessewk)
Certain inspectors don’t work outside of the client, or if the user context doesn’t have enough permissions.
Some examples are “relevant fixlets” , “logged on user”, and the domain inspectors. You need to either create the property in the console and see what the client’s report, or in some cases you can run the relevance debugger with elevated privileges.