Security Compliance

Members of ARM groups are missing in the Permissions view

This article will help you mitigate a problem with the members of ARM groups not showing in the Permissions view in ARM.

First published date

4/8/2022 3:06 PM

Last published date

6/9/2025 9:51 AM

Overview

The following highlighted part might be missing:

However, the .id.8man file is only responsible for the representation of the members of an ARM group on a certain permission set, as illustrated above. The permissions themselves are set in the NTFS filesystem.

Product section

Access Rights Manager

Cause

The id.8.man file in the related folder is corrupted or deleted. This can happen in case of a migration, damaged permissions or other causes.

Resolution

1. Go to the folder where the problem is and activate hidden system files and delete the id.8man file in it, if found.
2. Now do a simple permission change on the folder like adding a test user.
3. Afterwards rescan only the related folder from the Resources view in the Rich client and check the correct Member view after the scan.

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.