> For the complete documentation index, see [llms.txt](https://wiki.datadike.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.datadike.com/pam/administration/accounts/discovery-of-accounts.md).

# Collect accounts from an asset

Collect the accounts that already exist on an asset, classify the privileged ones, and bring them under management.

## What this is and when to use it

A collection task connects to an asset, lists the accounts that exist in its operating system, records their attributes, and classifies which of them hold administrative privilege.

Run it when onboarding an environment, to find out what is actually there rather than what the inventory claims — and run it periodically afterwards, so that accounts created outside the solution do not stay invisible.

## Before you start

* The host registered under **Environment › Assets** and reachable over SSH (Linux) or WinRM (Windows).
* An administrative account on the host, active in the solution and with enough permission to list system accounts.
* **Windows** — WinRM enabled and port 5985 open in the firewall.
* **Linux** — Python 3 installed on the target, normally at `/usr/bin/python3`.

{% hint style="warning" %}
**The account the solution connects with.** By default the solution uses the `administrator` account of the asset to run the collection. If that account has reduced permission, has no password stored in the solution, or is disabled in the operating system, **disable it in the solution** — otherwise every run fails on it.

Set it at **Environment › Assets › \<host> › Accounts › Administrator › Quick update › Active**.
{% endhint %}

## Steps

1. Open **Accounts › Automations › Gather accounts**.
2. Click **Create**.
3. Fill the basic configuration — see the field reference below.
4. Decide whether to turn on **Sync with asset**. With it on, collected accounts are registered against the asset automatically.
5. Set **Periodic execution** if the collection should repeat.
6. Save and run once by hand.

## What you should see

![The Gather accounts screen](https://1085357737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7xzJyi9JVzRwnV6JzUho%2Fuploads%2Fgit-blob-012e985d553b1296590ffc8e04a72163186498c2%2Faccount-collection.png?alt=media)

**1** How many collection tasks exist.

The run finishes and the task's **Executions** tab shows a log per host. The collected accounts appear against each asset, each with the date of the collection that found it.

## How to verify it worked

1. Open **Environment › Assets** and select one of the targets.
2. Open its **Accounts** tab. The accounts found in the operating system must be listed there, with the collection date.
3. Confirm that an account you know is privileged on that host carries the **privileged** marking. The classification is produced by the collection itself, not typed by an operator — if it is missing, the collection did not read the host's group membership.

## What is collected

For every account found, the task records:

| Group          | What it collects                                                                                                                                                                                       |
| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Attributes** | Username, UID or identifier, shell, home directory, and group membership                                                                                                                               |
| **Privilege**  | `root` and accounts holding administrative privilege — members of `root`, `wheel`, or `sudo`, and accounts listed in sudoers on Linux; `Administrator` and members of administrative groups on Windows |
| **Use**        | Last login, which separates accounts actually in use from accounts that exist but sit idle — the basis for reviewing and disabling orphaned accounts                                                   |

## What collection reaches, and what it does not

Automatic collection reads the account list from the operating system or the database engine. That is a narrower set than the assets the solution manages, and the difference matters when planning an onboarding.

| Asset category                                             | Accounts found automatically                                          | How credentials get in otherwise                                                        |
| ---------------------------------------------------------- | --------------------------------------------------------------------- | --------------------------------------------------------------------------------------- |
| **Host** — Linux, Unix, Windows                            | Yes                                                                   | —                                                                                       |
| **Database** — MySQL, MariaDB, PostgreSQL, Oracle, MongoDB | Yes                                                                   | —                                                                                       |
| **Database** — SQL Server                                  | No                                                                    | Registered by hand, or imported in bulk                                                 |
| **Device** — switches, routers, firewalls                  | No                                                                    | Registered by hand, or imported in bulk                                                 |
| **Web** — applications reached over HTTP or HTTPS          | No                                                                    | Registered by hand. The credential is then filled into the application's own login form |
| **Cloud**                                                  | The *assets* are discovered from the provider. Their accounts are not | Registered by hand, or collected once the asset is a managed host                       |

Two consequences worth planning around:

* **A category with no automatic collection is not a category the solution cannot manage.** A web application's credential is held, rotated on a schedule you set, and used to sign in without the user seeing it, exactly like a host account. What is missing is only the step that finds the accounts for you.
* **For everything not collected automatically, bulk import is the practical route.** Registering a few hundred network devices one screen at a time is how an onboarding stalls.

For finding the *assets* themselves, including from cloud providers, see [Discover assets on the network](https://wiki.datadike.com/pam/administration/assets/discovery.md).

## Common errors

| Symptom                                                       | Cause                                                                                                                                                                                  | Fix                                                                                                             |
| ------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- |
| `MODULE FAILURE` with empty `module_stdout`                   | The connection succeeded but the module could not start on the target. On Linux, Python missing or not at the expected path; on Windows, WinRM misconfigured or insufficient privilege | Install Python 3 on Linux; check WinRM authentication and privilege on Windows                                  |
| `Data could not be sent to remote host` / `Connection reset`  | SSH not running, a firewall closing the connection after the handshake, an IDS or IPS dropping it, or the wrong user                                                                   | Confirm the SSH service, the firewall, and the account used                                                     |
| `The connection plugin 'rdp' was not found`                   | The host has no SSH protocol registered, so the task has no management channel                                                                                                         | Add port 22 under **protocols** in the host's registration                                                      |
| `ntlm: the specified credentials were rejected by the server` | NTLM incompatibility, not a wrong password                                                                                                                                             | Check Windows event ID 4624 on the target — it shows the connection arrived and was blocked by NTLM negotiation |
| Every host fails on the same account                          | The `administrator` account is disabled, unprivileged, or has no password stored                                                                                                       | Disable that account in the solution, as described above                                                        |

{% hint style="info" %}
`rc: 0` in a `MODULE FAILURE` is misleading. It means the transport worked; the failure happened inside the target while starting the module.
{% endhint %}

## Field reference

| Field              | What it does                                                                                                    |
| ------------------ | --------------------------------------------------------------------------------------------------------------- |
| Name               | Identifies the collection. Required                                                                             |
| Node               | The folder of the environment where the operation runs                                                          |
| Devices            | The target assets                                                                                               |
| Periodic execution | Shows the scheduling fields — **crontab** and **interval**, default 24 hours. If both are set, **crontab wins** |
| Sync with asset    | Registers the collected accounts against the assets automatically                                               |
| Active             | Enables or disables the operation. On by default                                                                |
| Custodian          | The user responsible. Used only for email notification                                                          |
| Comment            | Free text                                                                                                       |

## Related pages

* [Managed accounts](https://wiki.datadike.com/pam/administration/accounts/managed-accounts.md)
* [Rotate credentials](https://wiki.datadike.com/pam/administration/accounts/rotation.md)
* [Discover assets on the network](https://wiki.datadike.com/pam/administration/assets/discovery.md) — finding the hosts, before finding their accounts
* [Asset inventory](https://wiki.datadike.com/pam/administration/assets/inventory.md)
