CAS

1. Configure and Administer Server

2. PART 1: Software Server Preparation & Installation
1. Hardware Specification Table
No Item Specification Quantity Estimated Unit
Price
Total Price
1 Server Machine Intel Xeon Quad
Core, 16GB RAM,
2TB HDD, Dual
NIC, RAID
controller
1 $1,200 $1,200
2 Client PCs Intel i5, 8GB RAM,
500GB HDD,
Gigabit Ethernet
10 $500 $5,000
3 Network Switch 24-Port Gigabit
Switch
1 $150 $150
4 Wireless Router Dual-Band Gigabit
Router
1 $100 $100
5 Patch Panel 24-Port with Cable
Management
1 $75 $75
6 Network Cables Cat6 Ethernet
Cable – 3m each
20 $5 $100
7 UPS (Server) 1500VA Smart UPS 1 $300 $300
8 Monitor +
Keyboard
22” Monitor with
USB
Keyboard/Mouse
Set
1 $200 $200
Total Cost $7,125

3. 2. Software Specification Table
No Item Specification/
License Info
Quantity Estimated Unit
Price
Total Price
1 Windows Server
2008 R2
Standard Edition –
64-bit
1 $600 $400
2 Windows Server
CALs
10 Client Access
Licenses
10 $30 $150
3 Antivirus Software Enterprise Edition 11 $30 $330
4 Backup Software Windows Backup /
Third-party (e.g.
Veeam)
1 $100 $200
5 Office Suite for
Clients
Microsoft Office
Home & Business
10 $170 $1500
6 Remote Desktop
Licenses
RDS CALs for
Admin Access
2 $100 $200
7 Network
Monitoring Tool
Open-source (e.g.
PRTG / SolarWinds
Free)
1 $0 $0
8 PDF Reader &
Utilities
Freeware (Adobe
Reader, etc.)
10 $0 $0
Total Cost $3,680

4. • RAM: 32 GB
• CPU: Intel Xeon E5 Series (8-Core, 3.2GHz)
• Storage: 2 TB HDD + 256 GB SSD (for OS)
3. Confirm Server Specification

5. 4. Install and configure Windows Server OS.
Step 1:Boot from DVD/USB with Windows Server 2008 R2 ISO
• Insert the installation media for
Windows Server 2008 R2. After
the installer runs, the Install
Windows screen appears.

6. Step2:Select Windows Server 2008 R2 Enterprise
(Full Installation) and click Next.

7. Step3:The installer asks you which type of installation.
For a new installation, click Custom (advanced).

8. Step4:The installer asks for disk location information. Make your selection and click Next.

9. Step5:The installation process begins.

10. 5. Assign a static IP address
• Open the Network and Sharing Center
• Click start >control panel>Network
and sharing center
• Open Properties of the Network
Adapter
• Right click on local area
connection>properties Select and
Configure internet protocol v4

11. 6. Set the name of the server
• 1. Open System Properties Click Start > Right-click Computer > Select Properties
• 2. Access Advanced Settings On the left side, click “Advanced system settings”
• 3. Go to the Computer Name Tab In the System Properties window, go to the “Computer Name” tab🔹
• 4. Click on “Change…”You’ll see the current computer name and a button labeled “Change…”Click it
• 5. Enter the New Server Name In the Computer Name field, enter your desired name :IT-HNS-1 You can also set
the domain later after configuring ADDS

12. ✅ Server Hardware/Software Compatibility for Windows
Server 2008
Component Minimum Requirement
(Win Server 2008)
Recommended for 10-
user Environment
Verification Method
Processor (CPU) 1 GHz (x86) or 1.4 GHz
(x64)
Quad-core 2.0 GHz or
higher
Use msinfo32 to check CPU
model and architecture
RAM (Memory) 512 MB (minimum), 2 GB
(recommended)
4–8 GB DDR3 or higher Check under System
Properties or msinfo32
Storage (HDD/SSD) 10 GB minimum (40 GB
recommended)
100–250 GB, SSD
preferred
Use Disk Management or
BIOS storage summary
Network Adapter Ethernet (100 Mbps
minimum)
Gigabit Ethernet (1000
Mbps)
Device Manager Network
→
Adapters
Display SVGA (800x600) SVGA or higher
(1024x768+)
Physically verify or check
Display Adapter in Device
Manager
BIOS/Firmware Must support Server 2008
boot requirements
Updated BIOS with
virtualization support
Access BIOS menu or use
manufacturer update tools
System Architecture x86 or x64 supported x64 recommended for
performance
Use msinfo32 System Type
→
Driver Support Drivers available for all
critical components
Windows Server 2008
certified drivers
Check Windows Server
Catalog or manufacturer
website
Software Compatibility Essential apps and
antivirus compatible
Confirm compatibility with
vendor
Research or test install in
VM or test environment

13. 1. ADDS (Active Directory Domain Services)
Main Role:
• ADDS is the core service in Windows Server that allows centralized
management of users, computers, and resources in a network.
• It provides authentication (login validation) and authorization
(access control) services.
Key Functions:
• Stores information about user accounts, computers, groups, and
organizational units (OUs).
• Enables administrators to enforce policies and deploy software across
multiple computers.
• Supports single sign-on (SSO) for users across the network.
Example:
• When a user logs in to their PC in a domain, ADDS checks their
credentials before giving access to shared files, printers, etc.

14. 2. DC (Domain Controller)
Main Role:
• A Domain Controller is a server that runs ADDS.
• It is responsible for authenticating and authorizing
all users and computers within the domain.
Key Functions:
• Controls access to domain resources.
• Enforces security policies.
• Hosts the AD database (NTDS.dit).
Example:
• The DC ensures that only registered domain users can log
into domain-connected machines.

15. 3. DHCP (Dynamic Host Configuration Protocol)
Main Role:
• DHCP automatically assigns IP addresses and network
configuration (subnet mask, gateway, DNS) to client devices.
Key Functions:
• Reduces manual IP address configuration.
• Prevents IP address conflicts.
• Helps efficiently manage IP address distribution using IP
scopes.
Example:
• When a client PC starts, it sends a DHCP request. The DHCP
server responds with an IP address (e.g., 192.168.1.10) and
other network info.

16. 4. DNS (Domain Name System)
Main Role:
• DNS translates domain names (like xyzcompany.com) into
IP addresses that computers can understand.
Key Functions:
• Resolves hostnames to IP addresses.
• Allows users to access websites and network resources using
human-readable names.
• Works closely with ADDS, as AD relies on DNS to locate
domain controllers.
Example:
• When a user types server01.xyzcompany.com, DNS resolves
this name to 10.20.30.1

17. Install and configure roles:
Step 1: Open Server Manager
• Click Start Search for
→ Server Manager.
• It may open automatically on login
Active Directory Domain Services (ADDS)
ADDS

18. Step 2: Start Role Installation
• In Server Manager, click “Manage” (top-right) → “Add Roles and Features”
• This opens the Add Roles and Features Wizard
• Role-Based Installation
• On the "Before You Begin" screen Click
→ Next
• Choose "Role-based or feature-based installation" Click
→ Next

19. • Step 7: Confirm & Install
• Review selections
• Click Install
• Wiat for the installation to complete — DO NOT restart yet

20. • Step 1: Open Server Manager
• Click Start > Server Manager
• Or press Windows + R, type ServerManager, hit Enter
• Step 2: Promote Server to Domain Controller
• In Server Manager, click the flag icon
⚑ (top-right)
• Select “Promote this server to a domain controller”
2. Domain Controller (DC)

21. • Step 3: Choose Deployment Operation
• You’ll see Deployment Configuration screen:
• Select: “Add a new forest”
• Enter Root domain name e.g.,
→ xyzcompany.local
• Click Next
• Step 4: Set Domain Controller Options
• Leave default:
▫ Domain Name System (DNS) Server ✔
▫ Global Catalog (GC) ✔
• Set Directory Services Restore Mode (DSRM) password
This is used in safe mode (write it down!)
• Click Next

22. • Step 6: Additional Options
• NetBIOS domain name will auto-fill (e.g., XYZCOMPANY)
• Click Next
• Step 7: Specify Paths
• Leave default paths unless you have specific needs:
• Database folder
• Log files folder
• SYSVOL folder
Click Next

23. • Step 8: Review & Install
• Review all settings
• Click View script (optional, saves a PowerShell install script)
• Click Next → Install
• Step 9: Reboot Automatically
• The server will reboot automatically after installation
• After reboot, it becomes a Domain Controller
• Step 10: Verify
• After login:
• Open Server Manager > Tools > Active Directory Users and Computers
• You’ll see:
▫ Your domain (e.g., xyzcompany.local)
▫ Default containers: Users, Computers, Domain Controllers

24. • Step 1:On the Select Server Roles page check the box next to
DHCP Server then click Next.
3. DHCP (with IP scope setup)

25. • Step 2: Add DHCP Role
• Click Manage (top-right) > Add Roles and Features
• Click Next until you reach “Server Roles”
• Check the box for DHCP Server
• A window will pop up Click
→ Add Features
• Click Next

26. • • Step 3:Click the Add button to create our first
scope. A scope is a range of IP addresses and
gateway configuration that DHCP will provide to
clients. Give the scope a name, provide the IP rage
addresses and gateway information, then click
OK.

27. • Step5:At the end, choose “Yes, I want to
activate this scope now.”
• Click close

28. DNS
Step 1:Open Server Manager
• • Click Start → Administrative Tools →
Server Manager. Step 2:Add DNS Server

29. Create an Organizational Unit (OU)
• Step 1: Open Active Directory Users and Computers
• Go to Server Manager
• Click Tools (top-right)
• Select Active Directory Users and Computers
• Step 2: Create an OU Named CompanyStaff
• In the left pane, right-click your domain name (e.g., xyzcompany.local)
• Select New > Organizational Unit
• Name it: CompanyStaff
• Click OK

30. • Step 3: Create Two Groups (e.g., IT and MSM)
• Right-click the CompanyStaff OU > New > Group

31. • 1. Log in to your Windows Server.
• 2. Right-click in the directory, select New, and then click **Folder**.
• 3. Name the folder
• Step 2: Share the Folder
• 1. Right-click on the folder you just created and select.
• 2. Go to the Sharing tab.

32. • Step one: Open Server Manager
• • Step 2:Enable Remote Desktop:
• In Server Manager, click on “Enable Remote Desktop" (or)
• Right-click on Computer select
→ Properties click
→ Remote settings on the
left. Under Remote Desktop, select:
• Allow connections from computers running any version of Remote Desktop

34. Testing & Troubleshooting
1. Test between server and clients to ensure connectivity.
• Ping Server from Client
• Open CMD on client:
ping 192.168.1.10
If replies received connection is OK
→
• Ping by Server Name
• ping SERVER01
Confirms DNS is working
• Check Client IP Settings
• ipconfig /all
IP should be in DHCP range, DNS = Server IP
• Test Shared Access
• In Run: SERVER01
Shows shared folders if connected properly
• If Failed
• Check cable/Wi-Fi, DHCP, firewall, and same subnet

35. 13. Check the DHCP lease information from a client.
• On client PC, open Command Prompt
• Type: ipconfig /all
• Look for these fields:
▫ DHCP Enabled: Yes
▫ DHCP Server: (e.g., 192.168.1.10)
▫ Lease Obtained / Expires: Shows lease time
info
• Confirms client received IP from the DHCP
server.

36. 14. Log in to a client PC with a domain user.
• On the client PC, click Switch User or Log
Out.
• At login screen, click Other User.
• Enter:
▫ Username: xyzcompanyjsmith
▫ Password: (set during user creation)
• Click Enter
If successful, the domain login works.
• Make sure the PC is joined to the domain first.

37. 15. Document any issues encountered and how you solved them.
• Issue 1: Client not receiving IP address
Cause: DHCP service not running
Solution: Restarted DHCP service on server and
reconnected client
• Issue 2: Ping to server failed
Cause: Windows Firewall blocking ICMP
Solution: Allowed ICMP Echo in server firewall settings
• Issue 3: Cannot access shared folders
Cause: Incorrect folder permissions
Solution: Updated NTFS and share permissions for
user group