Hello. Is there a way to query for existing config options that are not reported by “mdatp health”? For example, maximum-on-demand-scan-threads is not reported by “mdatp health.”

The “mdatp config” command only lets you change the value, but doesn’t provide a way to determine its current value. For example:

$ mdatp config maximum-on-demand-scan-threads
Configure maximum number of threads used in on-demand scans:
–value arg Numerical value between 1 and 64

There appears to be a way to brute force it, by supplying all possible options until the command fails because the new setting is the same as the current setting:

$ sudo mdatp config maximum-on-demand-scan-threads –value 16
Configuration property updated.

$ sudo mdatp config maximum-on-demand-scan-threads –value 16
Configuration not updated
New setting value is the same as the current value

Is there any better way to learn the current value?

​Hello. Is there a way to query for existing config options that are not reported by “mdatp health”? For example, maximum-on-demand-scan-threads is not reported by “mdatp health.” The “mdatp config” command only lets you change the value, but doesn’t provide a way to determine its current value. For example: $ mdatp config maximum-on-demand-scan-threads
Configure maximum number of threads used in on-demand scans:
–value arg Numerical value between 1 and 64 There appears to be a way to brute force it, by supplying all possible options until the command fails because the new setting is the same as the current setting: $ sudo mdatp config maximum-on-demand-scan-threads –value 16
Configuration property updated.

$ sudo mdatp config maximum-on-demand-scan-threads –value 16
Configuration not updated
New setting value is the same as the current value Is there any better way to learn the current value?  Read More

​