Installation accounts (BigFix scenario)

Edit online

You can install all the infrastructure components as the administrative user. You can also install some components as a non-administrative user but some limitations apply.

Downgrading privileges

If you install a component by a user with administrative privileges or root, you cannot downgrade the user privileges after the installation nor change the user to one with non-administrative or non-root privileges. If the installation by a user with non-administrative or non-root privileges is supported for a particular component, you can uninstall the component and install it again by a user with non-administrative or non-root privileges.

Server-side components

Table 1. Installation accounts for the server-side components
Component	User on Linux	User on Windows
All-in-One	root	N/A
BigFix client	root The user cannot be a sudo user.	User with administrative privileges
BigFix server	root The user cannot be a sudo user.	User with administrative privileges
DB2®	root or non-root user For information about limitations that apply when you install DB2 as a non-root user, see the following links. Non-root installation overview DB2 in DB2 11.1 documentation Non-root installation overview DB2 in DB2 11.5 documentation Non-root installation overview DB2 in DB2 12.1 documentation For information about recommended ulimit values for non-root installations, see the following links. Operating system user limit requirements in DB2 11.1 documentation Operating system user limit requirements in DB2 11.5 documentation Operating system user limit requirements in DB2 12.1 documentation	N/A
License Metric Tool	root or non-root user The server must be upgraded by the same user that installed it. The server that is installed by a non-root user is registered as a local system service. It cannot be upgraded with a fixlet. It must be upgraded in interactive or silent mode.	User with local administrative privileges with the log on as a service permission. Windows authentication To use Windows authentication, the following requirements must be met. The user must have administrative privileges for the database and must be able to add, remove or alter database schema elements such as tables, triggers, functions, keys, indexes and other. This user needs to have the `dbcreator` or `sysadmin` rights in the MS SQL Server database. If your database server is remote, the user must be a domain user who can accesses the remote database.
MS SQL Server	N/A	User with local administrative privileges

Endpoint components

Table 2. Installation accounts for endpoint components
Component	User on UNIX	User on Windows
BigFix client	root The user cannot be a sudo user.	User with administrative privileges