> For the complete documentation index, see [llms.txt](https://ajmal-anwar.gitbook.io/zyberspace-by-ajmal/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ajmal-anwar.gitbook.io/zyberspace-by-ajmal/zyberlab/02-active-directory-basics/explore-active-directory-users-computers.md).

# Explore Active Directory Users and Computers

## Objective

Become familiar with **Active Directory Users and Computers (ADUC)** before creating lab identities.

ADUC is one of the main graphical tools used to view and manage users, computers, groups, and organizational units in a traditional Active Directory environment.

## Open ADUC

On `DC01`:

1. Open **Server Manager**.
2. Select **Tools**.
3. Select **Active Directory Users and Computers**.

You should see the domain:

```
zyberlab.test
```

Expand it.

## What You Will See

Some default containers and objects will already exist.

Common examples include:

* **Builtin**
* **Computers**
* **Domain Controllers**
* **Users**

You will also see `DC01` under the **Domain Controllers** organizational unit.

## Container vs Organizational Unit

At a beginner level, both can appear like folders, but they are not exactly the same.

An **Organizational Unit (OU)** is designed to organize directory objects and can be used as a target for Group Policy and administrative delegation.

For ZyberLab, create two simple OUs so later objects remain easy to understand.

## Create Lab OUs

Right-click the domain `zyberlab.test` and select:

**New → Organizational Unit**

Create:

```
Lab Users
```

Then create:

```
Lab Groups
```

Keep **Protect container from accidental deletion** selected.

Your simple structure should now look similar to:

```
zyberlab.test
│
├── Domain Controllers
│    └── DC01
│
├── Lab Users
│
└── Lab Groups
```

`CLIENT01` will be added later when it joins the domain.

## Why Organize Objects?

A directory becomes difficult to manage when every user, computer, and group is placed together without structure.

OUs help administrators organize objects based on purpose and later make it possible to apply policies to selected parts of the directory.

## Security Relevance

Active Directory structure affects administration and security. OUs can be used for:

* Group Policy targeting
* delegated administration
* separating different types of systems or users
* making important objects easier to manage and monitor

For now, keep the structure very small. We will add complexity only when a lab needs it.

## Checkpoint

Confirm that you can see:

```
Lab Users
Lab Groups
Domain Controllers → DC01
```

The next lab will create the first normal domain user.