Greg.Sweet · Technical Support Representative · ✭✭✭✭✭

make sure the server name is showing when you click on "Register App" on the login screen. I had it blanked out in our lab environment after doing the upgrade. Otherwises, please open a support case as suggested by Keshav.

No worries, that's why I get the big bucks! (I wish!).

Hi Jordan, Leave it exactly as shown in the support article. It's more of a generic reference. I've had customers change as you suggested, but then it doesn't work. We can schedule a live support call and review if you'd prefer. You can respond on the open support case and I'll be picking that up soon.

For Sharepoint Online, you need these permissions: You also need to add the XML permissions shown here on the Sharepoint Admin site learn.microsoft.com/.../security-apponly-azureacs Please open a support case if you need more assistance. Edit: I see you have a related case open already. If the information above doesn't…

Not a problem. I'm looking forward to that issue being resolved as well, I know it's been a large problem, both for customers and support.

That issue is still outstanding as of 2025.1

ARM 2025.1.0.82 (released 14 Jan 2025) documentation.solarwinds.com/.../arm_2025-1_release_notes.htm

Updated original post for ARM 2024.3.2.35 release on 10 Dec 2024. documentation.solarwinds.com/.../arm_2024-3-2_release_notes.htm

Hi Juan, The logbook is populated mostly by the AD Logga scan, so ensure you have that set up, and it remains running https://documentation.solarwinds.com/en/success_center/arm/content/configure-adtive-directory-ad-logga.htm If you still have issues, please open a support case.

I agree completely! I'm somewhat surprised that there isn't a notice sent to all active license holders when a new release is available, but I'm just tech support! ‍♂️

I will see if they can keep that more up to date. I don't have permission to post there, it's a restricted forum.

Hi Christian, This is a false positive due to changes made in the ARM 2024.3.0.298 release. If you upgrade to the newer 2024.3.1.28 release, this alert will be eliminated. More information here, there are still some issues with the 2024 versions that are being worked on thwack.solarwinds.com/.../arm-2024-3-1-28-information

Make sure the account you are using for the scan has the correct permissions. https://documentation.solarwinds.com/en/success_center/arm/content/system_requirements/arm_2024-3-1_system_requirements.htm#arm-service-account-permissions Also check the ARM Configuration application > Jobs Overview > Failed to see what the…

New hotfix available for the Exchange scan and scripting issue (Note5 in original post). Please open a new support case if you'd like to receive this. It will be included in the next ARM update as well. Unfortunately the Hotfix isn't working for some installations so it is being tested further.

New release today 12 September 2024, some issues have been resolved. Original post updated. ARM 2024.3.1.28 Release Notes documentation.solarwinds.com/.../arm_2024-3-1_release_notes.htm

Please see Note 4 in my post about this latest update. thwack.solarwinds.com/.../arm-2024-3-0-298-information You can reconnect the collectors in the Collector window in the ARM Configuration by right-clicking and choose Restart Service for each collector. This issue should be resolved in the next ARM update but we have…

added the FQDN requirement for collectors. ARM will sometimes work with only the server name, but FQDN is preferred, and sometimes required.

small update to Note 5: you may use other accounts than the service account to process scans, so you may need to have this account logged in on your ARM server so the scans or scripts will process normally. Example:

I'll note this to our dev team. thank you.

Thanks for explaining this... you're hired!

Updated original post with Note 5: Exchange scan and scripting temporary fix

We had a live support session and found a temporary resolution for this issue: Log into the ARM server with the same account that is configured for the Exchange Scan, in this case it is the ARM service account. This may also need to be the account that installed the ARM software, which should also be used in the Exchange…

updated today: if you can't see the 'connection security' in web console settings, we have a fix for that. open a support case for assistance.

No updates on a service release/patch yet. Most of the time they just drop it and we find out at the same time its available on the customer portal. I will update this post when it does arrive.

Please check this article to see if it resolves the issue: ARM collectors do not connect after the update to ARM 2024.3 support.solarwinds.com/.../ARM-collectors-do-not-connect-after-the-update-to-ARM-2024-3

Hi Mike, The collector security message is no longer relevant due to the changes in the latest version, so you can safely ignore it. It will be removed in a hotfix release coming out soon. You may need to manually update the collectors to resolve the other issue. I'm going to make a post regarding the latest update and…

You need to log in to the Web client with an admin-level user to see Settings > Connection Security There are some instances where the collectors will not update automatically. If you still have issues, please open a support case.

Hi Marcus, You can use the following support article to resolve this issue. Use the web client to get the init code for the rich client on remote workstations. https://support.solarwinds.com/SuccessCenter/s/article/How-to-register-the-ARM-clients Please open a support ticket if you need more assistance. There were a lot of…

note the finest print at the end 

I'm getting the same error in Chrome, even after clearing cache. MS Edge works though...