Sub-domain scanning doesn't work for security group after update to 2024.3.0.298

Hi there,

we have several domains in the tree which are being scanned by ARM. Every scanning configuration has own service account to perform scanning. Recently we had updated to 2024.3.0.298 and since that my users noticed that if account was added to the security group directly through "computers and users" and not via ARM, then ARM doesn't show this changes after even next the scanning. The scanning is processing well without any errors.

I tried to do "deep deleting and re-install" of collector, creating resource configuration from scratch and even note 5 from (+) ARM 2024.3.0.298 information - Forum - Access Rights Manager (ARM) - THWACK (solarwinds.com), but it didn't solve my problem. I've issued a technical support request, but I am just wondering if somebody else has/had the same problem and maybe you could share guidance how to proceed.

Thanks.

Ro

Parents Reply Children
No Data