When the "Collect Time-Critical Inventory" policy is enabled and runs on a managed machine the logging SEVERITY reg key value is changed to 63 for a short period of time and then it switches back to what it was previously set to - before the policy finishes running.
Message seen in the logs:
Cound not find the "verboseLogging" attribute, verbose logging will be on
Priority: 8, Source: CInvTaskConfig::IsVerboseLoggingEnabled()
NOTE: There are no negative effects of this happening to any part of ITMS or our Solutions.
ITMS 8.6 RU2
Steps to duplicate:
1) Enable the "Collect Time-Critical Inventory" policy
2) Target the policy to a single machine or two
3) Have regedit open to the HKLM\Software\Altiris\eXpress\Event Logging\LogFile\Severity
4) While the policy is running press F5 continually (to refresh) and you'll see the value switch to 63 and then you'll see it switch back to what it was previously set to. This all happens in less than 30-40 seconds.
This has been duplicated, reported to development, and is resolved in RU3.
NOTE: This issue does slow down some Thycotic processes as their agent(s) historically have used the Sym Agent logs and the associated registry keys, but they released a new agent the week of April 25, 2022 that no longer uses the Sym Agent logs and this resolves their issues.