Network Management

Check permissions using the SolarWinds Platform Permission Checker

This article provides brief information and steps on using the SolarWinds Platform Permission Checker, which checks key locations on the SolarWinds Platform server to ensure all file system permissions are set correctly. It also repairs locations, providing proper access to the SolarWinds Platform server.

First published date

10/23/2018 8:10 PM

Last published date

8/26/2025 8:59 PM

Overview

The SolarWinds Platform Permission Checker checks key locations on the SolarWinds Platform Server to ensure all file system permissions are set correctly. It also repairs location permissions, providing proper access to the SolarWinds Platform Server.

SolarWinds recommends using a local administrator account. When the SolarWinds Platform is installed using a domain account that has restricted Group Policy settings, the logs may reflect that a service cannot access or write a file.  You will also see a note inside the Configuration Wizard logs advising that domain accounts are not supported with this tool. The Configuration Wizard logs are located on the Orion Server in the following location:

  • %ProgramData%\SolarWinds\Logs\Orion\ConfigurationWizard.log

You can always disable or remove the local server administrator account after making the changes.

Product section

Network Performance Monitor

Cause

Typically, this is caused by Group Policies applied to the domain account used to log on to the SolarWinds Platform Server.

Resolution

Next to the Check button, the Repair button can perform a repair, but when the domain Group Policy settings are restricted, a manual repair is required. This is a common routine for locked-down or hardened environments where the domain environment and group policies can cause conflict issues with the software changes.

Test the SolarWinds Platform permissions using the SolarWinds Platform Permission Checker 

  1. RDP to the SolarWinds Platform server.
  2. Open the SolarWinds Platform Permission Checker as Administrator (Default location: C:\Program Files (x86)\SolarWinds\Orion\OrionPermissionChecker.exe). If running a fresh install of 2022.1 and newer the default location is C:\Program Files\SolarWinds\Orion\OrionPermissionChecker.exe.
    image.png
  3. Click Check.
    image.png
  4. If any row shows FAILED as the Result, click Repair to set the correct permissions in place.
Note: A Group Policy might set the new permissions and undo the Repair performed by the tool. The best and most permanent way to fix permissions issues is to manually assign the appropriate permissions to the folder and to make sure they align with the Group Policy configuration.
  1. Click Check again to confirm that the Repair has applied the permissions. If the action failed please make sure the tool is running as Administrator.
  2. If the repair did not work, manually assign the required permissions to the folder. Use the SolarWinds Platform Permission Checker results to determine which permissions are required.

Manually repair permissions 

  1. Target Directories:  
    Volume:\InetPub\SolarWinds\
%ProgramData%\SolarWinds\
%ProgramFiles(x86)%\Common Files\SolarWinds\
%ProgramFiles(x86)%\Microsoft SQL Server\
%ProgramFiles(x86)%\SolarWinds\
%WinDir%\Temp
%WinDir%\Microsoft.NET\Framework\
%WinDir%\Microsoft.NET\Framework64\
%ProgramFiles%\SolarWinds\Orion\Web
  2. Right-click on each of the target directories and select Properties.
  3. Click Security.
  4. Check the Group of the user names list. If it does not exist, you must set the location and add the new principal accounts:
    1. Click Edit
    2. Click Add, and enter the Principal name. The Principal listed in the SolarWinds Platform Permission Checker should exist in this list and must have full control. 
    3. Click Check Names, and click OK.
    4. Select Full Control, and click OK to complete.
  5. Repeat sub-steps (a) to (d) for all rows that do not exist in the SolarWinds Platform Permission Checker.
  6. Re-run the SolarWinds Platform Permission Checker to confirm all users have full control.
Note: Allow an hour before re-running the SolarWinds Platform Permission Checker. The Group Policy in a domain setting may affect permissions.

Other Considerations to avoid this in the future: 

  1. Use a Local Administrator account (or create one for SolarWinds Admin access) to RDP into the server and do not use a domain account. Every domain account is still subject to the Groups Policies and can be limiting the SolarWinds Platform from accessing the required folders.

Note: Please consider that the Group Policy can either be Computer Configuration or User Configuration. Even if the SolarWinds Platform Permission Checker is running as a Local Administrator account, if the Group Policy is already applied via Computer configuration it will not be able to repair the permissions:

  • Computer Configuration: These policies apply to the local computer, and do not change per user.
  • User Configuration: These policies apply to users on the local machine, and will apply to any new users in the future, on this local computer.