> For the complete documentation index, see [llms.txt](https://docs.adaptiva.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adaptiva.com/patch/patching-fundamentals/business-units/epel-integration.md).

# Extra Packages or Enterprise Linux (EPEL) devices

To ensure your devices running EPEL are correctly monitored and patched by OneSite Patch, review these setup steps, understand the metadata loading times, and follow the troubleshooting procedures below.

## How EPEL Integration Works

OneSite Patch automatically detects any properly configured EPEL device and adds it to the EPEL Business Unit. In most cases, no manual configuration is required within the Adaptiva server.

* **Deployment Flexibility:** You can enable EPEL either before or after installing the OneSite Patch client on the device - the order does not matter.
* **Metadata Loading Warning:** The Adaptiva server does not store EPEL metadata by default. It will automatically pull this data when the first EPEL client is detected. **Plan for a delay of 30–60 minutes** while the system downloads all necessary information.

## Verifying detection in OneSite Patch

To confirm that your EPEL device have been successfully registered, check the device membership within the EPEL Business Unit:

* From the left menu, select **Asset Management > Business Units**.
* In the Business Units list, navigate to **All Clients Business Unit > Operating System > Operating System - Linux > Operating System - EPEL**.
* Click on the action menu (**...**) to the right of **Operating System - EPEL**, and select **Show Members**.
* Confirm that your EPEL devices are listed in the members table.

## Troubleshooting

If your EPEL device is not detected by the Adaptiva Server, try the following steps:

### 1. Verify that EPEL is enabled on the device:

Ensure EPEL is properly installed and enabled on the target Linux machine. Run the following command:

```bash
sudo dnf repolist enabled | grep epel
```

**Expected Output:** You should see output listing the active EPEL repositories, such as `epel/x86_64/10/updates`.

**If you see no output:** Follow your Linux distribution's official documentation to enable the EPEL repository.

### 2. If the device has EPEL enabled but is missing from the EPEL BU membership

If the device has EPEL enabled but is not appearing in the EPEL Business Unit, **do NOT manually trigger membership**. Instead, use the built-in sensor reset tool:

1. Navigate to **Assets > Devices** under Platform Features.
2. Locate the client in the device list. Click the action menu (**...**) and select **Reset Sensors for Group**. (This opens the **Reset Sensors** dialog.)
3. Toggle on **Send Immediately**.
4. In the **Sensors** field, click **+ Browse**.
5. Select **Sensors > Static**, search for `EpellInstalled`, and select it.
6. Click **OK**.
7. Click **OK** again to restart the sensors on the device, then wait approximately 5 minutes.

The device should now appear correctly in the EPEL BU membership list.