Windows Networking

1. Windows Networking Lab: Share Folders on PC1 and Access from PC2

Objective

Create four di erent shared folders on PC1:

Folder Share Type

Test1 Full Permission

Test2 Read-Only Permission

Test3 Share Name = UsersData

Test4 Hidden Share

Then access all shares from PC2.

Lab Topology

Computer IP Address

PC1 [Link]

PC2 [Link]

Verify connectivity:

ping [Link]

Step 1: Create Folders on PC1

Create:

D:\Test1

D:\Test2

D:\Test3

D:\Test4

Step 2: Share Test1 with Full Permissions

Right-click:

D:\Test1
→ Properties → Sharing → Advanced Sharing

Check:

Share this folder

Share Name:

Test1

Permissions:

Everyone = Full Control

Apply → OK

Step 3: Share Test2 with Read-Only Permissions

Right-click:

D:\Test2

→ Sharing → Advanced Sharing

Share Name:

Test2

Permissions:

Everyone = Read

Remove:

Change

Full Control

Apply → OK

Step 4: Share Test3 with Share Name "UsersData"

Right-click:

D:\Test3

→ Sharing → Advanced Sharing

Share Name:

UsersData
Permissions:

Everyone = Full Control

Apply → OK

Access path becomes:

\\PC1\UsersData

Step 5: Create Hidden Share Test4

Right-click:

D:\Test4

→ Sharing → Advanced Sharing

Share Name:

Test4$

The $ makes it hidden.

Permissions:

Everyone = Full Control

Apply → OK

Access path:

\\PC1\Test4$

Step 6: Verify Shares on PC1

Run:

net share

Expected:

Test1

Test2

UsersData

Test4$
Step 7: Browse Shares from PC2

Open Run:

Windows + R

Browse Test1:

\\PC1\Test1

Create, modify, and delete files.

Browse Test2:

\\PC1\Test2

Try creating a file.

Expected:

Access Denied

because it is Read-Only.

Browse Test3:

\\PC1\UsersData

You should have full access.

Step 8: Browse Hidden Share

Open Run:

\\PC1\Test4$

Direct access works.

Now browse:

\\PC1

You will see:

Test1

Test2

UsersData
but Test4$ will not be visible.

Step 9: Access via Command Line

List shares:

net view \\PC1

Map Test1:

net use Z: \\PC1\Test1

Map UsersData:

net use Y: \\PC1\UsersData

Map Hidden Share:

net use X: \\PC1\Test4$

View mappings:

net use

Expected Results

Share Browse Visible Read Write

\PC1\Test1 Yes Yes Yes

\PC1\Test2 Yes Yes No

\PC1\UsersData Yes Yes Yes

\PC1\Test4$ No Yes Yes

This lab demonstrates:

 Standard file sharing

 Full Control permissions

 Read-only permissions

 Custom share names

 Hidden shares ($)

 Accessing shares from another Windows computer.

 2. Enable Remote Desktop on PC1 & PC2 and Connect from PC1 to PC2

Objective

 Enable Remote Desktop (RDP) on both PCs.

 Allow remote connections.

 Connect PC2 remotely from PC1.

Network Topology

Computer IP Address

PC1 [Link]

PC2 [Link]

Verify connectivity:

ping [Link]

Step 1: Enable Remote Desktop on PC2

On PC2:

1. Press Windows + R

2. Type:

[Link]

3. Click Remote tab.

4. Under Remote Desktop, select:

Allow remote connections to this computer

5. Click Apply → OK

Step 2: Allow Users for RDP

On PC2:

1. Click:

Select Users
 2. Add user:

Administrator

or

nipuna\user1

3. Click Check Names

4. Click OK

Members of the local Administrators group already have RDP access.

Step 3: Enable Firewall Rule

Open Command Prompt as Administrator:

netsh advfirewall firewall set rule group="Remote Desktop" new enable=Yes

Verify:

netsh advfirewall firewall show rule name="Remote Desktop (TCP-In)"

Step 4: Start Remote Desktop Services

Open Services:

[Link]

Ensure:

Remote Desktop Services

Status:

Running

Startup Type:

Automatic

Step 5: Find PC2 IP Address

On PC2:

ipconfig

Example:
IPv4 Address . . . . . . : [Link]

Step 6: Connect from PC1 to PC2

On PC1:

Press:

Windows + R

Type:

mstsc

Remote Desktop Connection opens.

Enter:

[Link]

Click:

Connect

Step 7: Enter Credentials

For a local account:

PC2\Administrator

For a domain account:

nipuna\user1

Enter password and click OK.

Step 8: Accept Certificate Warning

Click:

Yes

You should now see the desktop of PC2.

Command-Line Method

Connect directly:
mstsc /v:[Link]

Or by hostname:

mstsc /v:PC2

Verify RDP Port

Check if port 3389 is listening:

netstat -an | find "3389"

Expected:

TCP [Link]:3389 LISTENING

Troubleshooting

Test Connectivity

ping [Link]

Test RDP Port

Test-NetConnection [Link] -Port 3389

Expected:

TcpTestSucceeded : True

Check Firewall

[Link]

Verify Remote Desktop (TCP-In) is enabled.

Domain Environment (Recommended)

If PC1 and PC2 are joined to [Link], grant RDP access through Group Policy:

Computer Configuration

└─ Policies

└─ Windows Settings

└─ Security Settings

└─ Local Policies
 └─ User Rights Assignment

Add users/groups to:

Allow log on through Remote Desktop Services

Example:

IT

Domain Users

Then run:

gpupdate /force

3. Lab Exercise: Configure Local Printer on PC1 and Add Network Printer on
PC2

Objective

1. Install and configure a Local Printer on PC1.

2. Share the printer on the network.

3. Connect to the shared printer from PC2.

4. Print a test page from both PCs.

Lab Topology

Computer Role

PC1 Printer Host

PC2 Printer Client

Printer Connected to PC1 (USB or Virtual Printer)

Part 1: Configure Local Printer on PC1

Step 1: Open Printers & Scanners

1. Open Control Panel.

2. Navigate to:

Hardware and Sound

→ Devices and Printers

3. Click:

Add a printer

Step 2: Add a Local Printer

Select:

The printer that I want isn't listed

Choose:

Add a local printer or network printer with manual settings

Click Next.

Step 3: Select Printer Port

Choose:

Use an existing port

Example:

LPT1:

or

USB001

Click Next.

Step 4: Install Printer Driver

Select:

Example:

Manufacturer: HP

Printer: HP LaserJet Series

or use:

Microsoft Print to PDF

Click Next.
Step 5: Name the Printer

Example:

O icePrinter

Click Next.

Printer installation completes.

Part 2: Share Printer on PC1

Step 1: Open Printer Properties

Right-click:

O icePrinter

Select:

Printer Properties

Step 2: Enable Sharing

Open:

Sharing Tab

Check:

Share this printer

Share Name:

O icePrinter

Click:

Apply → OK

Step 3: Verify Share

Open Run:

\\PC1

You should see:

O icePrinter

Part 3: Add Network Printer on PC2

Method 1: GUI Method

Step 1

Press:

Windows + R

Type:

\\PC1

Click OK.

Step 2

Double-click:

O icePrinter

Windows automatically installs the printer.

Step 3

Open:

Control Panel

→ Devices and Printers

Verify:

O icePrinter on PC1

appears.

Method 2: Add Printer Wizard

Open:

Devices and Printers

→ Add Printer
Choose:

Add a network printer

Select:

\\PC1\O icePrinter

Click:

Next

Finish installation.

Method 3: Using Run Command

On PC2:

\\PC1\O icePrinter

Press Enter.

The printer installs automatically.

Verify Printer Connection

Open Command Prompt:

wmic printer get name

Expected:

O icePrinter

O icePrinter on PC1

Print Test Page

On PC1

1. Right-click printer.

2. Select:

Printer Properties

3. Click:

Print Test Page

On PC2

1. Right-click:

O icePrinter on PC1

2. Select:

Printer Properties

3. Click:

Print Test Page

Troubleshooting

Enable Network Discovery

Control Panel

→ Network and Sharing Center

→ Advanced Sharing Settings

Enable:

Turn on Network Discovery

Turn on File and Printer Sharing

Allow Through Firewall

Enable:

File and Printer Sharing

in:

Windows Defender Firewall

Test Access

From PC2:

ping PC1

and
net view \\PC1

Expected output should list:

O icePrinter

4. Radmin Server and Radmin Viewer Configuration

Introduction

Radmin (Remote Administrator) is a remote-control software that allows

administrators to remotely access and manage computers over a network.

Components

1. Radmin Server

o Installed on the computer to be controlled.

o Runs as a Windows service.

o Accepts remote connections.

2. Radmin Viewer

o Installed on the administrator's computer.

o Used to connect and manage remote computers.

Lab Topology

Device Hostname IP Address

Administrator PC PC1 [Link]

Remote PC PC2 [Link]

Software Required

 Radmin Server

 Radmin Viewer

O icial website:

Radmin Technologies

Module 1: Install Radmin Server

Step 1: Download Radmin Server

Download from:

Radmin Server Download

Step 2: Install on PC2

Run setup:

Radmin_Server_Setup.exe

Click:

Next

I Agree

Install

Finish

Step 3: Verify Service

Open:

[Link]

Locate:

Radmin Server 3

Status:

Running

Startup Type:

Automatic

Module 2: Configure Radmin Server

Open Radmin Server Settings

Open:

Start

→ Radmin Server
→ Radmin Server Settings

Configure Port

Default:

4899

Verify:

Options

→ Network Settings

Port:

4899

Module 3: Configure User Permissions

Open:

Permissions

Select:

Radmin Security

Click:

Add User

Example:

Username: admin

Password: P@ssw0rd123

Assign Rights

Enable:

Full Control

View Screen

File Transfer

Telnet
Voice Chat

Text Chat

Shutdown

Click:

OK

Module 4: Configure Windows Firewall

Open CMD as Administrator:

netsh advfirewall firewall add rule name="Radmin" dir=in action=allow

protocol=TCP localport=4899

Verify:

netstat -an | find "4899"

Expected:

TCP [Link]:4899 LISTENING

Module 5: Install Radmin Viewer

Install on PC1.

Run:

Radmin_Viewer_Setup.exe

Click:

Next

Install

Finish

Module 6: Connect to Remote Computer

Open:

Radmin Viewer

Click:
Connection

→ New Connection

Enter Details

Connection Name : PC2

IP Address : [Link]

Port : 4899

Click:

OK

Module 7: Remote Control

Double-click:

PC2

Select:

Full Control

Enter:

Username : admin

Password : P@ssw0rd123

Click:

OK

You should now see PC2's desktop.

Module 8: View Only Mode

Select:

View

Features:

 Monitor screen

 No keyboard access
  No mouse access

Used for monitoring users.

Module 9: File Transfer

Select:

File Transfer

Two-pane file manager opens.

Example:

PC1 <----> PC2

Transfer files:

Copy

Move

Delete

Rename

Module 10: Text Chat

Select:

Text Chat

Communicate with remote users.

Example:

Administrator: Hello

User: Hi

Module 11: Telnet Session

Select:

Telnet

Run commands remotely.

Example:
ipconfig

hostname

systeminfo

Module 12: Remote Shutdown

Select:

Tools

→ Shutdown

Options:

Shutdown

Restart

Logo

Power O

Module 13: Active Directory Environment

If PCs belong to:

[Link]

Use:

NT Security

instead of Radmin Security.

Add:

Domain Admins

IT Group

Permissions:

Full Control

Troubleshooting

Ping Test
ping [Link]

Verify Service

sc query r_server

Status:

RUNNING

Verify Port

netstat -an | find "4899"

Test Connectivity

From PC1:

Test-NetConnection [Link] -Port 4899

Expected:

TcpTestSucceeded : True

Firewall Check

[Link]

Allow:

Radmin Server

TCP 4899

Security Best Practices

Use Strong Passwords

Example:

N1puna@2026!

Restrict IP Access

Allow only:
[Link]/24

Enable Logging

Radmin Server Settings

→ Options

→ Logging

Limit User Rights

Helpdesk:

View Only

File Transfer

Administrators:

Full Control

Advantages of Radmin

 Fast remote access

 Low bandwidth consumption

 Secure encrypted communication

 File transfer support

 Text and voice chat

 Active Directory integration

 Multi-user management

Lab Verification Checklist

Task Status

Install Radmin Server on PC2 ✓

Configure Security ✓

Open Firewall Port 4899 ✓

Install Radmin Viewer on PC1 ✓

Create Connection ✓

Full Control Access ✓

File Transfer ✓

Text Chat ✓

Remote Shutdown ✓

Active Directory Integration ✓

Expected Result

 PC1 successfully controls PC2 remotely.

 Secure authentication is enforced.

 File transfer and chat functions work.

 Remote administration tasks can be performed across the network using

Radmin Server and Viewer.
 Windows Server Configurations
5. Active Directory Domain Services (AD DS) Installation and Configuration

Create a New Root Domain: [Link]

Objective

Install Active Directory Domain Services (AD DS) and promote a Windows Server as
a Domain Controller for a new forest root domain named [Link].

Lab Environment

Server Role
DC01 Domain Controller
OS Windows Server 2019/2022/2025
Domain Name [Link]
IP Address [Link]

Step 1: Configure Static IP Address

Open:

Control Panel → Network and Sharing Center

→ Change Adapter Settings

Configure:

Setting Value

IP Address [Link]

Subnet Mask [Link]

Default Gateway [Link]

Preferred DNS [Link]

Verify:

ipconfig /all

Step 2: Rename Server

Open:

Server Manager
→ Local Server

→ Computer Name

Rename:

DC01

Restart the server.

Verify:

hostname

Expected:

DC01

Step 3: Install Active Directory Domain Services

Using Server Manager

Open:

Server Manager

→ Manage

→ Add Roles and Features

Select:

Role-based or feature-based installation

Choose:

DC01

Select role:

Active Directory Domain Services

Click:

Add Features

Next

Install

Wait for installation to complete.

Step 4: Promote Server to Domain Controller

After installation:

Click notification flag:

Promote this server to a domain controller

Deployment Configuration

Select:

Add a new forest

Root Domain Name:

[Link]

Click:

Next

Domain Controller Options

Select:

Domain Name System (DNS) Server

Global Catalog (GC)

Set DSRM Password:

P@ssw0rd123

Click:

Next

DNS Options

Ignore warning:

A delegation for this DNS server cannot be created.

Click:

Next
NetBIOS Name

Automatically generated:

NIPUNA

Click:

Next

Database Locations

Default:

Database : C:\Windows\NTDS

Logs : C:\Windows\NTDS

SYSVOL : C:\Windows\SYSVOL

Click:

Next

Review and Install

Click:

Install

The server will restart automatically.

Step 5: Verify Domain Controller

Login using:

NIPUNA\Administrator

or

Administrator@[Link]

Step 6: Verify Active Directory

Open:

Server Manager
→ Tools

→ Active Directory Users and Computers

Verify:

[Link]

appears.

Step 7: Verify DNS

Open:

Server Manager

→ Tools

→ DNS

Expand:

Forward Lookup Zones

Verify:

[Link]

exists.

Step 8: Verify SYSVOL and NETLOGON

Run:

net share

Expected:

NETLOGON

SYSVOL

Step 9: Verify Domain Health

Run:

dcdiag

Expected:
Passed Test

Step 10: Create Organizational Unit (OU)

Open:

AD Users and Computers

Right-click:

[Link]

→ New

→ Organizational Unit

Create:

IT

HR

Finance

Computers

Servers

Step 11: Create Domain User

Open:

AD Users and Computers

Right-click OU:

IT

→ New

→ User

Example:

First Name : Test

Last Name : User

Logon Name : testuser

Password:
P@ssw0rd123

Finish.

Step 12: Create Domain Group

Navigate:

IT OU

→ New

→ Group

Configure:

Group Name : IT

Group Scope: Global

Group Type : Security

Click:

OK

Add users to the group.

PowerShell Installation Method

Install AD DS:

Install-WindowsFeature AD-Domain-Services -IncludeManagementTools

Create Forest:

Install-ADDSForest `

-DomainName "[Link]" `

-DomainNetbiosName "NIPUNA" `

-InstallDNS `

-Force

The server will restart automatically.

Verify Domain Information

Run:

systeminfo | findstr /B /C:"Domain"

Expected:

Domain: [Link]

Verify FSMO Roles

Run:

netdom query fsmo

Expected:

Schema Master

Domain Naming Master

PDC Emulator

RID Master

Infrastructure Master

all hosted on:

[Link]

Useful Commands

Force Group Policy Update

gpupdate /force

Verify DNS Registration

nslookup [Link]

Check Replication

repadmin /replsummary

Check Domain Controller

nltest /dsgetdc:[Link]
 6. Create a Domain User in Windows Server (Active Directory)

Method 1: Using Active Directory Users and Computers (GUI)

Prerequisites:

 Active Directory Domain Services (AD DS) installed

 Server promoted as a Domain Controller

 Logged in with Domain Administrator account

Step 1: Open Active Directory Users and Computers

1. Click Start

2. Select Server Manager

3. Go to Tools

4. Click Active Directory Users and Computers

Step 2: Select the Organizational Unit (OU)

1. Expand your domain (e.g., [Link])

2. Select the Users container or a custom OU

Step 3: Create New User

1. Right-click the OU or Users container

2. Select New → User

Step 4: Enter User Information

Example:

Field Value

First Name John

Last Name Smith

User Logon Name [Link]

Click Next

Step 5: Set Password

Enter:

 Password

 Confirm Password
Options:

 ☑ User must change password at next logon

 ☑ Password never expires (optional)

 ☑ User cannot change password (optional)

Click Next

Step 6: Finish

Review details and click Finish

The domain user is now created

7. To create a Domain Group named "IT" in Windows Server Active Directory,

follow these steps:

Method 1: Using Active Directory Users and Computers (GUI)

1. Open Server Manager.

2. Click Tools → Active Directory Users and Computers.
3. Expand your domain (e.g., [Link]).
4. Select the Users container or the OU where you want to create the group.
5. Right-click → New → Group.
6. Enter:
o Group Name: IT
o Group Scope: Global
o Group Type: Security
7. Click OK.

The domain group IT is now created.

8. Add Domain Users to the IT Group

Method 1: Active Directory Users and Computers (GUI)

1. Open Server Manager → Tools → Active Directory Users and Computers.

2. Navigate to your domain.
3. Open the IT group.
4. Select the Members tab.
5. Click Add.
 6. Enter the usernames you want to add (e.g., user1, user2, user3).
7. Click Check Names.
8. Click OK → Apply → OK.

9. Permissions to the IT group in both Default Domain Policy and Default Domain
Controllers Policy

1. Add IT Group to Default Domain Policy

Open Group Policy Management

1. Open Server Manager → Tools → Group Policy Management.

2. Expand your domain.

3. Right-click Default Domain Policy → Edit.

Navigate to:

Computer Configuration

└─ Policies

└─ Windows Settings

└─ Security Settings

└─ Local Policies

└─ User Rights Assignment

Configure:

Allow Interactive Logon

Open:

Allow log on locally

Click Add User or Group and add:

IT

Allow Remote Desktop Logon

Open:

Allow log on through Remote Desktop Services

Add:

IT
2. Add IT Group to Default Domain Controllers Policy

1. In Group Policy Management, right-click Default Domain Controllers Policy →

Edit.

Navigate to:

Computer Configuration

└─ Policies

└─ Windows Settings

└─ Security Settings

└─ Local Policies

└─ User Rights Assignment

Configure:

Allow Local Logon on Domain Controllers

Allow log on locally

Add:

IT

Allow RDP Logon on Domain Controllers

Allow log on through Remote Desktop Services

Add:

IT

3. Update Group Policy

Run on Domain Controllers and Domain Computers:

gpupdate /force

Verify:

gpresult /r

PowerShell Verification
Check members of the IT group:

Get-ADGroupMember -Identity "IT"

Recommended Microsoft Practice

Instead of modifying the built-in Default Domain Policy and Default Domain
Controllers Policy, create a new GPO such as:

IT-Login-Permissions

and link it to the required OU(s). This prevents issues during troubleshooting and future
policy maintenance.

Typical Permissions for IT Sta

User Right Add IT Group

Allow log on locally Yes

Allow log on through Remote Desktop Services Yes

Access this computer from the network Yes

Log on as a service (if required) Optional

Log on as a batch job (if required) Optional

After replication and policy refresh, users who are members of the IT group will be able
to log on locally and via RDP according to the computers to which the policies apply.

9. User Profiles in Windows Server

Windows Server supports three main user profile types:

1. Local Profile

2. Roaming Profile

3. Mandatory Profile

1. Local User Profile

A Local Profile is stored on the computer where the user logs in.

Create a Local User Profile

Step 1: Create a User

Open:

Server Manager → Tools → Active Directory Users and Computers

Create a user:

Users → New → User

Example:

Username: user1

Password: P@ssw0rd123

Step 2: Log In

1. Join a client PC to the domain.

2. Log in as:

DOMAIN\user1

Windows automatically creates:

C:\Users\user1

This is a Local Profile.

Characteristics

 Stored locally.

 Settings remain only on that computer.

 Does not follow the user to other PCs.

2. Roaming Profile

A Roaming Profile follows the user to any domain-joined computer.

Step 1: Create a Shared Folder

On the server:

Create:

D:\Profiles

Share it as:

Profiles$

(The $ hides the share.)

Share Permissions

Everyone = Full Control

NTFS Permissions

Administrators = Full Control

SYSTEM = Full Control

Authenticated Users = Create Folder/Append Data

Creator Owner = Full Control (Subfolders Only)

Step 2: Configure User Profile Path

Open:

Active Directory Users and Computers

Select user → Properties → Profile

Enter:

\\SERVER01\Profiles$\%username%

Example:

\\DC01\Profiles$\%username%

Click:

Apply → OK

Step 3: Test

Log in from PC1:

DOMAIN\user1

A profile folder is created:

\\DC01\Profiles$\user1

Create files on Desktop.

Log in from PC2.

The same Desktop and settings appear.

Characteristics
  Profile stored on server.

 Available from any PC.

 Increased logon/logo time for large profiles.

3. Mandatory Profile

A Mandatory Profile is a read-only roaming profile.

Users can make changes during a session, but changes are discarded after logout.

Step 1: Create a Template User

Create:

mandatoryuser

Log in once.

Customize:

 Desktop

 Wallpaper

 Start Menu

 Applications

Log o .

Step 2: Copy Profile

Open:

System Properties

→ Advanced

→ User Profiles

→ Settings

Select:

mandatoryuser

Click:
Copy To

Copy to:

\\DC01\Profiles$\Mandatory.v2

Allow:

Everyone

Step 3: Convert to Mandatory Profile

Open:

\\DC01\Profiles$\Mandatory.v2

Rename:

[Link]

to

[Link]

This makes the profile mandatory.

Step 4: Assign Mandatory Profile

Open:

ADUC

→ User Properties

→ Profile

Profile Path:

\\DC01\Profiles$\Mandatory.v2

Apply and OK.

Step 5: Test

Log in as the user.

Change:

 Desktop background
  Icons

 Files

Log o and log in again.

All changes are discarded.

Characteristics

 Centralized profile.

 Read-only.

 Ideal for labs, training rooms, kiosks, classrooms, and shared systems.

Profile Comparison

Feature Local Roaming Mandatory

Stored on Local PC Yes No No

Stored on Server No Yes Yes

Follows User No Yes Yes

Saves User Changes Yes Yes No

Central Management No Yes Yes

Best For Individual PCs O ice Users Labs/Classrooms

Useful Commands

View profiles:

net user

Update policies:

gpupdate /force

Check applied policies:

gpresult /r

List profile folders:

dir \\DC01\Profiles$
These procedures work on Windows Server 2012/2016/2019/2022/2025 with Active
Directory Domain Services (AD DS).

If you want to automatically open Calculator ([Link]) whenever a domain user logs
in, create a Logon Script and assign it to the user or through Group Policy.

10. Logon Script

Method 1: User Logon Script (Recommended)

Step 1: Create the Script

On the Domain Controller, open Notepad and create a file named:

[Link]

Add:

@echo o

start [Link]

Save it in:

C:\Windows\SYSVOL\sysvol\<yourdomain>\scripts

Example:

C:\Windows\SYSVOL\sysvol\[Link]\scripts\[Link]

Step 2: Assign the Script to a User

1. Open Active Directory Users and Computers.

2. Right-click the user → Properties.

3. Select the Profile tab.

4. In Logon Script, enter:

[Link]

5. Click Apply → OK.

Step 3: Test

Log in as the user:

nipuna\user1

Calculator should open automatically after logon.

Method 2: Assign via Group Policy

Create Script

Create:

@echo o

start [Link]

Save as:

\\<domain>\SYSVOL\<domain>\scripts\[Link]

Configure GPO

Open Group Policy Management.

Edit the desired GPO:

User Configuration

└─ Policies

└─ Windows Settings

└─ Scripts (Logon/Logo )

└─ Logon

Click:

Add → Browse → [Link] → OK

Apply the GPO to the users or OU.

Update policy:

gpupdate /force

Method 3: PowerShell Logon Script

Create calc.ps1:

Start-Process [Link]

Assign it as a Logon Script through Group Policy.

Launch Multiple Applications at Logon

Example [Link]:

@echo o

start [Link]

start [Link]

start [Link]

When the user logs in, Calculator, Notepad, and Paint will open automatically.

Verify Logon Script

Check the assigned script:

net user user1 /domain

or in ADUC:

User Properties → Profile → Logon Script

This is a common Active Directory lab exercise for demonstrating user logon scripts.

Active Directory Lab Exercise – User Home Folder Configuration

Objective

Configure a Home Folder for a domain user so that when the user logs in, a personal
network drive is automatically mapped.

Lab Topology

Device Hostname Role

Windows Server DC01 Domain Controller

Windows Client PC01 Domain Joined Client

Domain [Link] Active Directory Domain

Step 1: Create a Shared Folder on the Server

On DC01:

Create a folder:

D:\HomeFolders

Step 2: Share the Folder

Right-click:

D:\HomeFolders

Select:

Properties → Sharing → Advanced Sharing

Check:

Share this folder

Share Name:

HomeFolders$

($ makes the share hidden)

Step 3: Configure Share Permissions

Click Permissions.

Add:

Everyone

Allow:

Full Control

Click Apply → OK

Step 4: Configure NTFS Permissions

Open:

Properties → Security → Advanced

Recommended permissions:
 Principal Permission

SYSTEM Full Control

Administrators Full Control

Creator Owner Full Control (Subfolders Only)

Authenticated Users Create Folder / Append Data

Apply changes.

Step 5: Create Domain User

Open:

Server Manager

→ Tools

→ Active Directory Users and Computers

Create:

Username: user1

Password: P@ssw0rd123

Step 6: Configure Home Folder

Open:

ADUC

→ User Properties

→ Profile Tab

Under Home Folder:

Select:

Connect

Choose drive letter:

H:

Folder Path:

\\DC01\HomeFolders$\%username%
Example:

\\DC01\HomeFolders$\user1

or use:

\\DC01\HomeFolders$\%username%

Click:

Apply → OK

Step 7: Log In from Client PC

Login as:

nipuna\user1

Windows automatically:

1. Creates:

\\DC01\HomeFolders$\user1

2. Maps:

H:

drive to the user's home folder.

Step 8: Verify

Open:

This PC

You should see:

H: on DC01

Create a file:

[Link]

Verify it appears in:

D:\HomeFolders\user1

on the server.
Step 9: Test from Another Computer

Login to another domain-joined PC using:

nipuna\user1

The same drive:

H:

will be mapped automatically.

Useful Commands

Check Shared Folders

net share

View Mapped Drives

net use

Map Manually

net use H: \\DC01\HomeFolders$\user1

Remove Mapping

net use H: /delete

Update Policies

gpupdate /force

Expected Result

After successful configuration:

 User logs into the domain.

 Personal folder is created automatically.

 Drive H: is mapped.

 User can store files centrally on the server.

 Files are accessible from any domain-joined computer.

Join a Windows Client Computer to the Domain [Link]

Objective

Join a Windows 10/11 client computer to the Active Directory domain [Link] and
log in using a domain user account.

Prerequisites

Domain Controller (DC01)

 Active Directory Domain Services installed

 Domain Name:

[Link]

 DNS configured correctly

 Domain Controller IP:

[Link]

Client Computer (PC01)

Example settings:

Setting Value

Computer Name PC01

IP Address [Link]

Subnet Mask [Link]

Default Gateway [Link]

Preferred DNS [Link]

The client must use the Domain Controller's IP as its DNS server.

Step 1: Verify Network Connectivity

On the client, open Command Prompt:

ping [Link]

Expected:

Reply from [Link]

Test DNS:

nslookup [Link]

Expected result:

Name: [Link]

Address: [Link]

Step 2: Verify Domain Discovery

Run:

nslookup

set type=SRV

_ldap._tcp.dc._msdcs.[Link]

Expected:

[Link]

If this fails, check DNS settings.

11. Step 3: Join the Domain (GUI Method)

Open:

Settings → System → About

Click:

Rename this PC (Advanced)

or

Control Panel → System → Advanced System Settings

Select:

Computer Name → Change

Choose:

Member of: Domain

Enter:

[Link]
Click:

OK

Step 4: Enter Domain Administrator Credentials

When prompted, enter:

Username: Administrator

Password: ********

or

nipuna\Administrator

Click:

OK

Step 5: Successful Join

You should receive:

Welcome to the [Link] domain.

Click:

OK

Restart the computer.

Step 6: Log In Using a Domain User

At the login screen choose:

Other User

Enter:

nipuna\user1

or

user1@[Link]

Enter the password.

Step 7: Verify Domain Membership

Open Command Prompt:

systeminfo | findstr /B /C:"Domain"

Expected:

Domain: [Link]

Or:

echo %logonserver%

Example:

\\DC01

Step 8: Verify Computer Object in Active Directory

On the Domain Controller:

Open:

Server Manager

→ Tools

→ Active Directory Users and Computers

Navigate to:

Computers

You should see:

PC01

PowerShell Method

Run PowerShell as Administrator:

Add-Computer -DomainName "[Link]" -Credential nipuna\Administrator -Restart

Common Troubleshooting

DNS Issue

Check:
ipconfig /all

DNS should point to:

[Link]

(not [Link] or other public DNS servers)

Force DNS Registration on DC

On the Domain Controller:

ipconfig /registerdns

net stop netlogon

net start netlogon

Test Secure Channel

Test-ComputerSecureChannel -Verbose

Expected Result

Client PC joined to [Link]

Computer object created in Active Directory
Domain users can log in
Group Policies apply automatically
Home folders, roaming profiles, and logon scripts work for domain users

This is the standard Active Directory domain join procedure used in Windows Server
2012, 2016, 2019, 2022, and 2025 environments.

12. DHCP Installation and Configuration in Windows Server

Objective

Install the DHCP Server Role, create a DHCP scope, and automatically assign IP
addresses to client computers.

Lab Environment
 Device Role IP Address

DC01 AD DS + DNS + DHCP Server [Link]

PC01 DHCP Client Automatic

Domain [Link] Active Directory

Step 1: Configure Static IP on Server

Before installing DHCP, configure a static IP.

Example:

Setting Value

IP Address [Link]

Subnet Mask [Link]

Default Gateway [Link]

Preferred DNS [Link]

Verify:

ipconfig /all

Step 2: Install DHCP Server Role

Using Server Manager

1. Open Server Manager.

2. Click Manage → Add Roles and Features.

3. Select:

o Role-based or feature-based installation

o Select server: DC01

4. Check:

DHCP Server

5. Click Add Features.

6. Click Next → Install.

Step 3: Complete DHCP Post-Install Configuration

After installation:

1. Click the notification flag.

2. Select:

Complete DHCP Configuration

3. Click Next.

4. Use Domain Administrator credentials.

5. Click Commit.

6. Click Close.

This authorizes the DHCP server in Active Directory.

Step 4: Open DHCP Console

Open:

Server Manager

→ Tools

→ DHCP

You should see:

[Link]

Step 5: Create a New DHCP Scope

Expand:

IPv4

Right-click:

New Scope

Click Next.

Scope Information
Name:

O ice Network

Description:

DHCP Scope for LAN Users

Click Next.

IP Address Range

Example:

Start IP:

[Link]

End IP:

[Link]

Subnet Mask:

[Link]

Click Next.

Exclusions (Optional)

Reserve server addresses:

[Link] - [Link]

or leave blank.

Click Next.

Lease Duration

Default:

8 Days

Click Next.

Configure DHCP Options

Select:

Yes, I want to configure these options now

Click Next.

Step 6: Configure Gateway

Router IP:

[Link]

Click:

Add

Next.

Step 7: Configure DNS

Parent Domain:

[Link]

DNS Server:

[Link]

Click:

Add

Next.

Step 8: Configure WINS

Usually not required.

Click:

Next

Step 9: Activate Scope

Select:

Yes, I want to activate this scope now

Finish.

Step 10: Verify Scope

You should see:

IPv4

└─ O ice Network

Subfolders:

Address Pool

Address Leases

Reservations

Scope Options

Step 11: Configure Client PC

On PC01:

Open:

Network Adapter Properties

Select:

Internet Protocol Version 4 (TCP/IPv4)

Choose:

Obtain an IP address automatically

Obtain DNS server address automatically

Click OK.

Step 12: Renew DHCP Lease

On PC01:

ipconfig /release

ipconfig /renew

Verify:
ipconfig /all

Expected:

IPv4 Address : [Link]-200

DHCP Server : [Link]

DNS Server : [Link]

Step 13: Create a DHCP Reservation

To always assign the same IP to a device:

1. Open DHCP Console.

2. Expand:

IPv4

→ O ice Network

→ Reservations

3. Right-click:

New Reservation

Example:

Field Value
Reservation Name PC01
IP Address [Link]
MAC Address 00-11-22-33-44-55
Click Add.

Step 14: View Active DHCP Leases

Open:

IPv4

→ O ice Network

→ Address Leases

You will see:

IP Address Client Name

 [Link] PC01

[Link] PC02

PowerShell Installation

Install DHCP:

Install-WindowsFeature DHCP -IncludeManagementTools

Authorize DHCP:

Add-DhcpServerInDC -DnsName "[Link]" -IPAddress [Link]

Create Scope:

Add-DhcpServerv4Scope `

-Name "O ice Network" `

-StartRange [Link] `

-EndRange [Link] `

-SubnetMask [Link]

Configure Gateway:

Set-DhcpServerv4OptionValue `

-Router [Link] `

-DnsServer [Link] `

-DnsDomain [Link]

Useful DHCP Commands

View DHCP Server:

Get-DhcpServerInDC

View Scopes:

Get-DhcpServerv4Scope

View Leases:

Get-DhcpServerv4Lease -ScopeId [Link]

View Reservations:
Get-DhcpServerv4Reservation -ScopeId [Link]

Troubleshooting

Check DHCP Service

[Link]

Verify:

DHCP Server

Status:

Running

Test Client

ipconfig /renew

Check Authorization

In DHCP Console, server icon should have a green check mark.

Expected Result

DHCP Server role installed

DHCP server authorized in Active Directory
Scope created ([Link]–[Link])
Gateway and DNS configured
Clients receive IP addresses automatically
Reservations can be configured for fixed IP assignments
DHCP integrates with [Link] Active Directory environment.