jwolff ✭✭✭✭✭

Please take a look at this link: https://documentation.solarwinds.com/en/success_center/arm/content/configure-ad-scans.htm As you can see, when setting up the AD resource, there is an option called “Changes will be done using account ...” I think you need to enter the service user you want to use here.

Oh yes, please add the possibility to adjust scheduled reports afterwards!

This is the solution: https://support.solarwinds.com/SuccessCenter/s/article/How-to-include-new-user-or-computer-object-created-outside-ARM-in-the-ARM-database

The workaround does not seem to work because the ‘domain computer’ group is not monitored by AD Logga.

Work around: Set a "group memberships changed" alert on "domain computers" group.

In ARM 2022.2? :-)

Hi Andreas, yes, I have seen this possibility before, but I could not really look into it too much yet. Nevertheless, I think it would be useful to have this possibility in the fat client, too, to have all functions in one place. Many greetings Jonas

I would appreciate it if this type of report would not only list the biggest directories, but (if necessary) the size of all directories.

Does the service user have local admin rights on the ARM or collector server?

You need to add the following section to your template: /* In the Modules section Exchange settings are done for e-mail activating the group (create a distribution group). Delete the "Modules" section if you want the user to create a group without e-mail functionality.*/ "Modules" : [ { // (required) Name of the module as…

Isn't it enabled by default as long as you don't manually set the email addresses in the template? See here: /* (optional) Set creation and validation rules for e-mail-addresses. If you delete/disable the following section Exchange default policies are used to create e-mail-adresses.*/ { "Name": "emailaddresses",…

Unfortunately, I can't find a working link. However, I think the relevant trigger is this one in the pnserver.config.xml file: <tracer.adlogga.forwarding.ComputerCreated.enabled type="System.Boolean">true</tracer.adlogga.forwarding.ComputerCreated.enabled>

This one helps: support.solarwinds.com/.../How-to-include-new-user-or-computer-object-created-outside-ARM-in-the-ARM-database

Unfortunately, the solution does not work as hoped. Apparently the AD Logga does not log any changes to the ‘domain computer’ group. Is there a switch that can be set in the pnServer.config to force the group to be monitored?

Thank you both, That sounds like a good solution: Set an alert on the 'domain computers' group so that the AD scan script is triggered when a change is detected. The only downside is that the script will also be triggered if an object is removed from the group. But this is fine.

Well, thank you. I will submit a feature request. On the other hand, that means that there is no quick solution, I guess. :')

Thank you for the clarification.

Hello, Could you confirm whether the issue of scripts only being executable when the corresponding user is logged in via RDP remains unresolved in this version?

I have opened a support case some time ago in hope of getting new information, but unfortunately Solarwinds cannot say when to expect a new fix. They promise to work hard on this topic, but it's very unsatisfying.

Hello, I opened a support case on Monday, but have not received the hotfix yet. The first reaction was: ‘What hotfix?’ Can you provide the hotfix here, please?

As this is a public forum, unfortunately it is to some extent. No need to be offended.

Hi Allmecht, I can understand your anger, because I'm annoyed by all these problems too. Besides, the ARM is very expensive, so you can expect fast support. However, I would like to point out that your posts often appear very rude. I don't want to lecture you, but maybe you'll think about it. Sorry for off topic.

Please note that if you use more than one service account for different purposes, it is not enough if only the primary ARM service account is logged in. For example, the service account that performs the Exchange Scan must also be logged in if it is a different account. The same also applies if another account is used to…

Thank you very much! Since we have separate service accounts for the ARM installation and the Exchange scan, I had to set up an RDP session with both accounts. I also had to change the logins stored for the script executions, because by default the account which is used for changing the AD is used for the scripts - which…

Thanks for the information. Are you referring to the issue of scripts not running? Or is this suggested solution about the Exchange scans not working? I am surprised that the same user should be used for the Exchange scan as for the ARM installation. I always understood that separate service accounts should be used for the…

Hi Keshav, I have tried the workaround with the Windows Task. Before, I got this error when I started the Exchange Scan: Now I no longer get this error. However, 0 items are scanned: Do you have any other idea? If I use the account that was also used for the ARM installation, then I would have to give it additional rights,…

Regarding 2) This will be due to the “Comfort Feature”. See here under “Use the convenience feature”: documentation.solarwinds.com/.../basic-settings.htm Regarding 3) That is strange. In my understanding, the group behavior should be the same, regardless of whether the permissions are assigned directly or via a user order.…

When I come across errors in ARM, I try to look for clues in the ARM logs. You can find them here: C:\ProgramData\protected-networks.com\8MAN\log However, I don't know which log is most likely to provide clues about the message queue. Perhaps the pnAlert.log or the armServer.log. You can open the files with a text editor…

Hi Florian, don't take it for granted, but I believe the message queue is part of the RabbitMQ component. You could check your ARM server to see if the RabbitMQ service is running when the error occurs. If the RabbitMQ service is not running - well, then the question is why it is stopping. The Windows event log may give a…

Hi Florian, it might not answer your question, but have you already restarted the ARM service or the whole server and checked if the error still persists? Kind regards Jonas