INSTALLATION GUIDE

Access Rights Manager

Version 9.2

Last Updated: Monday, April 29, 2019

© 2019 SolarWinds Worldwide, LLC. All rights reserved.

This document may not be reproduced by any means nor modified, decompiled, disassembled, published
or distributed, in whole or in part, or translated to any electronic medium or other means without the prior
written consent of SolarWinds. All right, title, and interest in and to the software, services, and
documentation are and shall remain the exclusive property of SolarWinds, its affiliates, and/or its
respective licensors.

SOLARWINDS DISCLAIMS ALL WARRANTIES, CONDITIONS, OR OTHER TERMS, EXPRESS OR IMPLIED,

STATUTORY OR OTHERWISE, ON THE DOCUMENTATION, INCLUDING WITHOUT LIMITATION
NONINFRINGEMENT, ACCURACY, COMPLETENESS, OR USEFULNESS OF ANY INFORMATION CONTAINED
HEREIN. IN NO EVENT SHALL SOLARWINDS, ITS SUPPLIERS, NOR ITS LICENSORS BE LIABLE FOR ANY
DAMAGES, WHETHER ARISING IN TORT, CONTRACT OR ANY OTHER LEGAL THEORY, EVEN IF SOLARWINDS
HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

The SolarWinds, SolarWinds & Design, Orion, and THWACK trademarks are the exclusive property of
SolarWinds Worldwide, LLC or its affiliates, are registered with the U.S. Patent and Trademark Office, and
may be registered or pending registration in other countries. All other SolarWinds trademarks, service
marks, and logos may be common law marks or are registered or pending registration. All other
trademarks mentioned herein are used for identification purposes only and are trademarks of (and may
be registered trademarks) of their respective companies.

page 2
Table of Contents
Access Rights Manager Installation Guide 4

The components that make up the Access Rights Manager architecture 5

System requirements 6

ARM Server requirements 6

ARM Collector requirements 7

ARM GUI application requirements 8

SQL Server requirements 8

File server requirements 9

Web components and web interface requirements 10

Network requirements and firewall settings 10

ARM service account permissions 11

Download and install Access Rights Manager 13

After installation 14

page 3
INSTALLATION GUIDE: ACCESS RIGHTS MANAGER

Access Rights Manager Installation Guide

Use the information in this guide to prepare your environment and install SolarWinds Access Rights
Manager.

Review the section on The components that make up the Access Rights Manager architecture and check
the System requirements for each component prior to starting the installation. Then follow the step-by-
step walkthrough to download and install ARM.
After completing the installation, check out the ARM Getting Started Guide for basic configuration tips and
to learn how to start using ARM.

page 4
The components that make up the Access Rights
Manager architecture
The ARM component architecture allows you to run installations across a variety of remote resources in an
extremely efficient manner. All individual components connect with each other via network interfaces. You
can also run several components on the same computer.

The ARM suite is comprised of the following components:

Required components
Included with the ARM installation package:
 l The ARM Server - to process new data and requests from the main application including the first
Collector to connect your resource and data systems
 l The ARM application - The front-end GUI for using ARM
 l The ARM Configuration application - The front-end GUI for configuring ARM

Included with the ARM installation package:

 l Microsoft SQL Server Express database server - use an existing MS SQL Server instance or install
the included Express Edition to store ARM's collected information

Optional components
Included with the ARM installation package:
 l Additonal ARM Collectors - install more collectors to balance loads in large environments
 l Web Components - Web client and Web API for accessing and using ARM

page 5
INSTALLATION GUIDE: ACCESS RIGHTS MANAGER

System requirements
The following table lists hardware and software system requirements for your SolarWinds Access Rights
Manager installation.

ARM Server requirements

Hardware requirements for the ARM Server vary depending on several factors:

 l the number of users in Active Directory (AD)

 l the number of file servers and directories monitored by ARM
 l the ARM Server's data storage settings

Installing ARM onto a server that has an Orion Platform installation will cause a conflict with the
RabbitMQ service. To avoid this, ARM and Orion Platform products must be installed on separated
servers. Note that ARM is not an Orion Platform product.

HARDWARE/SOFTWARE REQUIREMENTS
Operating System  l Windows Server 2008 R2
 l Windows Server 2012
 l Windows Server 2012 R2
 l Windows Server 2016
 l Windows Server 2019

CPU (number of processor

ACTIVE DIRECTORY USERS NUMBER OF CORES
cores)
up to 1,000 2

up to 4,000 4

4,000+ 4

Intel Itanium platforms are not supported.

Hard drive space

ACTIVE DIRECTORY USERS DISK SPACE
up to 1,000 30 GB

up to 4,000 40 GB

4,000+ 40 GB

page 6
 HARDWARE/SOFTWARE REQUIREMENTS
Memory
ACTIVE DIRECTORY USERS RAM
up to 1,000 4 GB

up to 4,000 8 GB

4,000+ 16 GB

.NET Framework .NET 3.5 SP1 and

.NET 4.5.2 (or higher)

Access rights The service account requires local administrator rights on the ARM
server.

Other The ARM server must be a member of an Active Directory domain.

Clusters are not supported.

Server Core is not supported.

ARM Collector requirements

HARDWARE/SOFTWARE REQUIREMENTS
Operating System  l Windows Server 2008 R2
 l Windows Server 2012
 l Windows Server 2012 R2
 l Windows Server 2016
 l Windows Server 2019

CPU (number of processor 2

cores)
Intel Itanium platforms are not supported.

Hard drive space 5 GB

Memory 4 GB

.NET Framework .NET 3.5 SP1 and

.NET 4.5.2 (or higher)

Other ARM collectors can be installed on a member server (node) of a cluster.

ARM collectors cannot be used as a cluster for Windows Server Failover

Clustering manager.

page 7
INSTALLATION GUIDE: ACCESS RIGHTS MANAGER

ARM GUI application requirements

These requirements are for both the main ARM application and the ARM Configuration application.

HARDWARE/SOFTWARE REQUIREMENTS
Operating System  l Windows Server 2008 R2
 l Windows Server 2012
 l Windows Server 2012 R2
 l Windows Server 2016
 l Windows Server 2019
 l Windows Vista
 l Windows 7
 l Windows 8
 l Windows 10

CPU (number of processor 2

cores)

Hard drive space 500 MB

Memory 2 GB

.NET Framework .NET 3.5 SP1 and

.NET 4.5.2 (or higher)

Graphics Graphic card supporting DirectX 10

Screen resolution Minimum: 1280x1024

Recommended: 1920x1080 (1080p)

SQL Server requirements

HARDWARE/SOFTWARE REQUIREMENTS
Microsoft SQL Server (32-bit  l SQL Server 2008 SP1
and 64-bit)  l SQL Server 2012
 l SQL Server 2014
 l SQL Server 2016
 l SQL Server 2017

CPU (number of processor 2

cores)
Intel Itanium platforms are not supported.

page 8
 HARDWARE/SOFTWARE REQUIREMENTS
Hard drive space (Database
ACTIVE DIRECTORY USERS STORAGE SPACE
storage)
up to 1,000 10 GB

up to 4,000 30 GB

4,000+ 50 GB

Memory 4 GB

.NET Framework .NET 3.5 SP1 and

.NET 4.5.2 (or higher)

Access rights  l If you don't already have a database for use with ARM, ARM setup
requires the role "dbcreator" on the SQL server.
 l If you've already created a database for use with ARM, ARM
requires the role "dbowner" for the database.

Other SQL Server Express Edition can be used but has the following limitations:

 l 10 GB maximum database size: Only a limited number of scans

can be stored
 l ca. 1 GB maximum RAM use: Loss of performance in large
environments
 l 4 maximum CPU cores: Loss of performance in large environments

File server requirements

HARDWARE/SOFTWARE REQUIREMENTS
Operating System  l Windows Server 2008 R2
 l Windows Server 2012
 l Windows Server 2012 R2
 l Windows Server 2016
 l Windows Server 2019

Supported types of file  l Domain-integrated or stand-alone DFS file servers.

servers  l CIFS-based shares on NetApp file servers.
 l CIFS-based shares on EMC file servers.

Windows Server Failover Clustering (WSFC) is supported.

page 9
INSTALLATION GUIDE: ACCESS RIGHTS MANAGER

Web components and web interface requirements

HARDWARE/SOFTWARE REQUIREMENTS
Operating System  l Windows Server 2008 R2
 l Windows Server 2012
 l Windows Server 2012 R2
 l Windows Server 2016
 l Windows Server 2019

.NET Framework .NET 3.5 SP1 and

.NET 4.5.2 (or higher)

Internet Information Services  Version 7.5 or higher

(IIS)

Supported browsers  l Google Chrome 54 or higher

 l Mozilla Firefox 49 or higher
 l Microsoft Edge 38.14383 or higher
 l Microsoft Internet Explorer 11.0.22 or higher

Cookies and Javascript must be enabled.

Other  

Network requirements and firewall settings

PORT SERVICE/PROCESS PURPOSE AND DESCRIPTION
389 LDAP Active Directory scanning

139 NetBIOS File server scanning

445 Microsoft DS (CIFS)

135+ Local users/groups

dynamic* (WMI/DCOM/RPC)

1433 MS SQL Server ARM uses this port for all communication between the
ARM server and the SQL server.

Collectors communicate only with the ARM server and do

not communicate with the SQL server

88 Kerberos Authentication

page 10
 PORT SERVICE/PROCESS PURPOSE AND DESCRIPTION
55555+ ARM components standard ARM components standard port
dynamic* port
ARM uses this port for all communication between the
ARM server and client (GUI applications).

*SolarWinds recommends defining application-based rules for services that use dynamic ports because of
the possibility of random high-numbered ports being used.

ARM service account permissions

SolarWinds recommends using service accounts (dedicated user accounts) for ARM. This ensures that:

 l The access rights of the service accounts are used only by ARM.
 l It is easy to identify whether an action was performed by an ARM service account or by a domain
admin.
 l If the domain admin's password changes, the ARM configuration is unaffected.
 l Restrictions are avoided through activity limits (for example, Exchange Online allows only three
parallel requests).

FEATURE REQUIRED ACCESS RIGHTS

ARM server A service account requires local administrator rights on the ARM server.

If a service account is a member of the domain Admin group, then this

requirement is automatically fulfilled. If a server computer becomes a
member of the domain (domain join) then the group Domain Admins will
become a member of the local administrator group.

SQL Server  l If you don't already have a database for use with ARM, ARM setup
requires the role "dbcreator" on the SQL server.
 l If you've already created a database for use with ARM, ARM requires
the role "dbowner" for the database.

Active Directory (AD)-Scan Every user account requires at least read-only rights in order to be able to
generate an Active Directory scan.

If you utilize delegation in your organization, then you must add the
service account to the group that can read the required OUs.

AD Modify If you work with delegation in your company, you must assign service
accounts to a group that is allowed to change the relevant OUs.

Without delegation: Service accounts become a member of the Domain

admin group.

page 11
INSTALLATION GUIDE: ACCESS RIGHTS MANAGER

FEATURE REQUIRED ACCESS RIGHTS

File server (FS)-Scan User accounts require access rights in order to be able to read NTFS
permissions as well as traverse folders.

Service accounts can become a member of the domain admin group.

If the domain admin account does not have access to all folders (for
example, user folders) then add service accounts to the backup operators
on the file server.

page 12
Download and install Access Rights Manager
These instructions provide installation steps for installing SolarWinds Access Rights Manager.

The ARM installer is an all-in-one installation package that you can use to install ARM's components: The
ARM Server, Collector, GUI applications, and Web interface components.

You can use an existing Microsoft SQL Server instance or install Microsoft SQL Server Express during
the basic configuartion.

1. Verify that all Check the system requirements for all ARM components.
system
requirements have
been met for each
component of your
ARM installation.

2. Download  1. Go to customerportal.solarwinds.com.

installation files  2. In the Log In tab, enter your organization's SWID and your email
from Customer address.
Portal
 3. In the Latest Downloads table, click Choose Download for the
installation files for your product.

If you have not yet created a SolarWinds account, see Access the
Customer Portal to create an account.

3. Run the  1. Copy the ARM setup.exe to a local folder.

installation file  2. Run setup.exe with administrator rights.

The setup language is automatically selected to match the language of

operating system for the following languages: German, English, and
French. Otherwise, English is selected.

4. Select the For a new ARM installation, you must select the ARM Server and Collector as
components to well as both User Interface applications.
install
Select the Web client and Web API Web component to install ARM Web
functionality. Unselect this option if you want to install the Web components
to a different server.

5. Agree to the If you agree with the License Terms, check the box for "I agree to the License
License Terms Terms", then click Install.

page 13
INSTALLATION GUIDE: ACCESS RIGHTS MANAGER

6. Install missing During installation, ARM setup will automatically check for missing required
components components.
(optional)
If any required components are missing, ARM setup will show you a list of the
missing components.

You can install any missing components manually, then restart the
installation process, or you can select Install missing components and select
Try Again.

Installation will not continue until all required components have been
installed.

7. Complete the When all chosen components have been installed successfully, the
installation installation dialog will let you know that setup has been successful.

Close the dialog when you're ready.

After installation
After you have successfully installed Access Rights Manager, check out the ARM Getting Started Guide,
which will walk you through basic configuration steps, activating your license, logging in, and setting up
your first Active Directory and file system scanners.

page 14