Active Directory Installation and Configuration on Windows Server 2019


Here is a step-by-step guide to install and configure Active Directory (AD) on Windows Server 2019:


### 1. **Prepare the Server**

   - Ensure the server has a **static IP address**.

   - Set the appropriate **server name** to reflect its role (e.g., `DC1` for the first domain controller).

   - Update Windows to the latest version and install necessary drivers.


### 2. **Install Active Directory Domain Services (AD DS) Role**

   1. Open **Server Manager**.

   2. In the **Dashboard**, click **Add roles and features**.

   3. In the **Add Roles and Features Wizard**, follow these steps:

      - Choose **Role-based or feature-based installation**.

      - Select your server from the list.

      - In the list of roles, check **Active Directory Domain Services**.

      - A window will pop up to install the required features. Click **Add Features**.

      - Continue through the wizard and click **Install**.

   4. After installation, do not close the wizard. Click on the link to **Promote this server to a domain controller**.


### 3. **Promote Server to Domain Controller**

   1. In the **Active Directory Domain Services Configuration Wizard**:

      - Choose **Add a new forest** if this is your first domain controller, and specify the **Root domain name** (e.g., `mydomain.local`).

   2. Select the **Domain Controller Options**:

      - Choose **Forest functional level** and **Domain functional level** (usually Windows Server 2016 or later).

      - Ensure **Domain Name System (DNS) server** and **Global Catalog (GC)** options are checked.

      - Provide a **DSRM password** (used for Directory Services Restore Mode).

   3. Review the **DNS Options**.

   4. Continue through the **Additional Options** (the default NetBIOS name is automatically filled based on the domain name).

   5. Choose the paths for **AD DS database**, **log files**, and **SYSVOL** (defaults are typically fine).

   6. Review the configuration, then click **Next** and install.


   The server will restart after completing the promotion.


### 4. **Verify Active Directory Installation**

   1. Once the server has rebooted, log in and open **Server Manager**.

   2. Go to **Tools** and select **Active Directory Users and Computers**. You should see the domain you created.

   3. In **DNS Manager**, ensure the DNS entries for your new domain controller are correct.

   4. Use the command prompt to run `ipconfig /all` and verify that the server’s IP configuration lists the domain controller as the preferred DNS server.


### 5. **Configure Active Directory**

   1. **Create Organizational Units (OUs)**:

      - Open **Active Directory Users and Computers**.

      - Right-click the domain and select **New > Organizational Unit**.

      - Name the OU (e.g., `Users`, `Computers`).

   2. **Create Users**:

      - In **Active Directory Users and Computers**, right-click an OU (e.g., `Users`) and choose **New > User**.

      - Enter the user details and set a password.

   3. **Create Groups**:

      - Right-click the domain or an OU, select **New > Group**, and configure it (e.g., security groups for file permissions).

   4. **Join Computers to the Domain**:

      - Go to the **System Properties** on each computer.

      - Under **Computer Name**, click **Change**, select **Domain**, and enter your domain name.

      - Restart the computer when prompted.

   5. **Assign Roles and Permissions**:

      - Use **Group Policy Management** to set policies for users and computers across the domain (e.g., password policies, login restrictions).


### 6. **Configure DNS (Optional)**

   - If you chose to install DNS during AD DS setup, you may need to configure DNS zones and records.

   - Open **DNS Manager**, right-click the server, and create **Forward Lookup Zones** for your domain.


This completes the installation and configuration of Active Directory on Windows Server 2019. Your server is now a Domain Controller, managing users, computers, and resources within the network.

Comments

Post a Comment

Popular posts from this blog

How to install VNX Launcher that has embedded java and Firefox

Image
  Alternative for Adobe Flash Player to access Unisphere. Symptoms VNXe Unisphere in older OE revisions is not accessible after December 31, 2020. The Adobe Flash Player plug-in is no longer supported in browsers. VNXe Unisphere used to require a browser with the Flash Player plug-in. Cause When VNXe is running an older OE revision, Adobe Flash Player is required by Unisphere. Refer: https://elabnavigator.emc.com/vault/pdf/EMC_VNXe_ESSM.pdf?key=1588743011568 Adobe has expired Flash Player as of December 31, 2020.   Details: https://www.adobe.com/products/flashplayer/end-of-life.html Resolution Newer VNXe OE revisions support HTML5. Once the VNXe is upgraded, Unisphere will work. Since December 31, 2020 browsers do not support Adobe Flash Player. Most browsers support HTML5. VNXe Unisphere must also support HTML5 in order to use VNXe Unisphere. HTML5 support is delivered in these VNXe revisions:       ...
Read more

DHCP FAILED APIPA IS USED

Image
Hi to all, In a Cisco packet tracer while i am trying to connect the dhcp server to pc it will getting the error like dhcp failed. APIPA is being used. For this issues this is also one reason.dhcp is not configured correctly. If we create a  vlan's in the switch's and we configured dhcp server in the layer 3 switch or layer 2 switch or in router. VLAN 10 NAME SALES VLAN 20 NAME DATA We created two vlan's now creating dhcp server for that  Switch(config)#ip dhcp pool name sales (should be the vlan name. not any other name.) Switch(Dhcp-config)#network 192.168.10.0 255.255.255.0  Switch(dhcp-config)#default-router 192.168.10.1 Switch(dhcp-config)#exit Swithc(config)#ip dhcp pool name data Switch(dhcp-config)#network 192.168.20.0 255.255.255.0 Switch(dhcp-config)#default-router 192.168.20.1 Switch(dhcp-config)#exit
Read more

Zabbix Server is not working: the information dispaly may not be current

Image
  Details  Cannot display item queue. Connection to Zabbix server "localhost:10051" refused. Possible reasons: 1. Incorrect "NodeAddress" or "ListenPort" in the "zabbix_server.conf" or server IP/DNS override in the "zabbix.conf.php"; 2. Security environment (for example, SELinux) is blocking the connection; 3. Zabbix server daemon not running; 4. Firewall is blocking TCP connection. Connection refused Observation:- In Centos 9 [root@nmtool ~]# systemctl status zabbix-server.service ● zabbix-server.service - Zabbix Server      Loaded: loaded (/usr/lib/systemd/system/zabbix-server.service; enabled; vendor preset: d>     Active: activating (auto-restart) (Result: exit-code) since Fri 2023-02-03 10:36:52 IST;>    Process: 57289 ExecStart=/usr/sbin/zabbix_server -c $CONFFILE (code=exited, status=0/SUCC>    Process: 57295 ExecStop=/bin/kill -SIGTERM $MAINPID (code=exited, status=1/FAILURE)    Main PID: 57291 (cod...
Read more