(imported topic written by SystemAdmin)
After going through the tedious process of changing a few client settings in groups, I wanted to save time by creating a single, dynamic relevance that would derive the correct entry for that machine. I made the change and sent an action to run last night, but this morning I noticed that none of the machines (400+) had reported in. They were not showing ‘Failed’, not showing ‘Not relevant’…just not reported.
I rechecked the relevance, and created an analysis to prove it works on those machines (which it did) and then I tried editing a machine where the entry already exists. I selected ‘Edit Computer Settings’ on the machine, entered the relevance, clicked Ok and suddenly an error message popped up telling me the setting relevance cannot be more than 256 characters. Ah, that’s why…{sigh}
Based on this experience, I have a question about the 256 char limit and also wanted to highlight the issue where the console seems to be missing the error checking code in some places. This has been tested on 7.1.1315 and 8.0.584.0.
-
Is there a reason that Client Setting values are limited to 256 characters? This is a very low limit if you need to create any relevance that has a reasonable amount of logic/testing to come up with the correct value. Is this set quite low to keep it below 512 chars (or some other value), as you also add a chunk of relevance to the setting which will be an extra n chars as well?
-
If the setting value exists, when you edit the field value, the error checking code tests whether the entry is > 256 characters. If the entry does not exist (or you go to ‘More Options’ to add it to multiple machines), and you Add the entry, then there is no error checking on the length of the Custom setting field.
-
I’m not sure where the error was triggered, but if a lengthy relevance slips through the net someplace, I would have thought some type of error would be generated, rather than the action just listing it as ‘Not reported’.
-Jim