> 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/business-units-ad.md).

# Business Units Using Active Directory

If you have Organization Units (OU) already set up in Active Directory (AD), you can use the ADInformation sensor in OneSite Patch to auto-populate new Business Units based on your OU settings. This sensor helps you align your patching, deployment, and reboot strategies.

This approach is particularly useful when you need to accomplish any of the following:

* Servers require different deployment windows
* Servers require different reboot windows
* Different user interaction settings are needed
* Devices must be grouped into logical patching waves or deployment rings

Proper planning of OU paths, operating conditions, and BU hierarchy is essential for accurate device assignment. For instance, a parent Business Unit must contain all devices that are intended to appear in its child Business Units. If a device is not included in the parent BU scope, it will not appear in any child Business Units, even if the child scope rules match.

{% hint style="info" %}
Adaptiva is not domain-specific and retrieves Active Directory information directly from the client. This lets you use the ADInformation sensor across multiple domains without requiring complex trust relationships or additional permissions.
{% endhint %}

## Prerequisites

* Devices must be joined to Active Directory
* Adaptiva Client must be installed and have completed initial synchronization of sensor data

## Use a Sensor to Map Your Organization Units to Business Units

As you create Business Units modeled on your Organization Unit hierarchy, be sure to add the ADInformation Sensor to each Business Unit you wish to populate with clients. Verify that the path pointing back to Active Directory is correct.

1. In OneSite Patch, select **Asset Management > Business Units** in the left side navigation.
2. Click **+ New**.

   ![Create new business unit](/files/kxsbB9DvbK022vHDt3AL)
3. Under **General Settings**, adjust any settings you want at this point; however, the minimum configuration is to add a Name, Description, and an Evaluation Schedule.
4. Scroll to the **Business Unit Scopes** section and click **Sensors**.

   ![Scopes option](/files/1P0i27faOtepiY0MdJ5L)
5. Click **+ Add Sensor Group Scope**.
6. Give this Sensor Group Scope a meaningful name and description.
7. Click **Browse**.
8. Select **ADInformation** (typically near the top of the list) and click **OK**.

   ![Sensor Group Scope screen with completed data](/files/wBvtKgstZDJkbRzcrReR)
9. On the **Sensor Group Scope** screen, click the ellipsis (…) next to the sensor.
10. Select **Add Operating Condition**.
11. For **Data Column**, select **Organizational Unit**.
12. For **Operating Condition**, select **Contains**. Contains is the most flexible as it includes both the specified OU and all child/sub-OUs beneath it.
13. For **Value**, enter the AD OU path, for example (in plain text): `[domain]\Servers\SQL`

    ![Completed operating condition](/files/3XwFaUhEVdaCwQj8EN51)
14. Confirm that the OU path has been entered correctly.
15. Click **OK**.

    ![Completed Sensor Group Scope](/files/gtK4f07PpEpnFiMxRmmr)
16. Click **OK**, and then click **Save**. (Note: the BU will run a membership evaluation according to the schedule configured.)

## Validation and Testing

Before you create another Business Unit, you should verify that this Business Unit contains the correct devices:

1. In OneSite Patch, select **Asset Management > Business Units** in the left side navigation.
2. Scroll to the **Business Unit Scopes** section and click **Show Members**.

   ![Show members button](/files/GehbfghlApLeqKabD7ty)
3. On the **Group Members** page, click **Evaluate Membership**.
4. If everything is set up correctly, you should see the client machines you are expecting to see.
5. Don't forget to go back and edit any configuration settings that you want for this Business Unit.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.adaptiva.com/patch/patching-fundamentals/business-units/business-units-ad.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.