4.all Chapters

IMPLEMENTAION OF WINDOWS DEPLYOMENT SERVICES IN INTRANET
CHAPTER – 1
1.1 INTRODUCTION
1.2 BENEFITS
LKC/DCS-IT/MSC-N&PD/21151500009/MAY-2017 1
1.1 INTRODUCTION TO THE PROJECT:

The Project is “IMPLEMENTAION OF WINDOWS DEPLYOMENT SERVICES IN
INTRANET”. In this project, we will manage the whole network of a college by using layer-
3devices and servers.
5.2 Benefits
1) Centralization: Unlike P2P, where there is no central administration, here in this

architecture there is a centralized control. Servers help in administering the whole
set-up. Access rights and resource allocation is done by Servers.
2) Proper Management : All the files are stored at the same place. In this way,
management of files becomes easy. Also it becomes easier to find files.
3) Back-up and Recovery possible: As all the data is stored on server it’s easy to make
a back-up of it. Also, in case of some break-down if data is lost, it can be recovered
easily and efficiently. While in peer computing we have to take back-up at every
workstation.
4) Up gradation and Scalability in Client-server set-up: Changes can be made easily by

just upgrading the server. Also new resources and systems can be added by making
necessary changes in server.
5) Accessibility: From various platforms in the network, server can be accessed

remotely.
6) As new information is uploaded in database, each workstation need not have its
own storage capacities increased (as may be the case in peer-to-peer systems). All the
changes are made only in central computer on which server database exists.
7) Security: Rules defining security and access rights can be defined at the time of set-
up of server.
8) Servers can play different roles for different clients.
CHAPTER 2
PROJECT REQUIREMENTS
2.1 SOFTWARE
2.2 HARDWARE
2.1 Software
2.1.1 VMware
Fig:6.1
VMware vSphere leverages the power of virtualization to transform datacenters into

simplified cloud computing infrastructures and enables IT organizations to deliver flexible and
reliable IT services. Vmware vSphere virtualizes and aggregates the underlying physical
hardware resources across multiple systems and provides pools of virtual resources to the
datacenter.
As a cloud operating system, VMware vSphere manages large collections of infrastructure
(such as CPUs, storage, and networking) as a seamless and dynamic operating environment,
and also manages the complexity of a datacenter. The following component layers make up
VMware vSphere:
Infrastructure Services: Infrastructure Services are the set of services provided to abstract,
aggregate,and allocate hardware or infrastructure resources. Infrastructure Services canbe
categorized into:n VMware vCompute—the VMware capabilities that abstract away from
underlying disparate server resources. vCompute services aggregate these resources across
many discrete servers and assign them to applications. VMware vStorage the set of
technologies that enables the most efficient use and management of storage in virtual
environments. VMware vNetwork—the set of technologies that simplify and enhance
Networking in virtual environments.
Application Services: Application Services are the set of services provided to ensure availabi
lity, security, and scalability for applications. Examples include HA and Fault Tolerance.
VMware vCenter Server: VMware vCenter Server provides a single point of control of the
datacenter. It provides essential datacenter services such as access control, performance
monitoring, and configuration.
Clients Users can access the VMware vSphere datacenter through clients such as the vSphere
Client or Web Access through a Web browser.
2.1.2 GNS3
Fig: 6.2
GNS3 is a Graphical Network Simulator that allows emulation of complex networks. You
may be familiar with VMWare or Virtual PC that are used to emulate various operating
systems in a virtual environment. These programs allow you to run operating systems such as
Windows XP Professional or Ubuntu Linux in a virtual environment on your computer. GNS3
allows the same type of emulation using Cisco Internetwork Operating Systems. It allows you
to run a Cisco IOS in a virtual environment on your computer. GNS3 is a graphical front end
to a product called Dynagen. Dynamips is the core program that allows IOS emulation.
Dinesen runs on top of Dynamo ips to create a more user friendly, text-based environment. A
user may create network topologies using simple Windows ini-type files with Dynagen
running on top of Dynamics. GNS3 takes this a step further by providing a graphical
environment.
GNS3 allows the emulation of Cisco IOSs on your Windows or Linux based computer.
Emulation is possible for a long list of router platforms and PIX firewalls. Using an
EtherSwitch card in a router, switching platforms may also be emulated to the degree of the
card’s supported functionality. This means that GNS3 is an invaluable tool for preparing for
Cisco certifications such as Network Associates and Network Professionals. There are a
number of router simulators on the market, but they are limited to the commands that the
developer chooses to include. Almost always there are commands or parameters that are not
supported when working on a practice lab. In these simulators you are only seeing a
representation of the output of a simulated router. The accuracy of that representation is only
as good as the developer makes it. With GNS3 you are running an actual Cisco IOS, so you
will see exactly what the IOS produces and will have access to any command or parameter
supported by the IOS. In addition, GNS3 is an open source, free program for you to use.
However, due to licensing restrictions, you will have to provide your own Cisco IOSs to use
with GNS3. Also, GNS3 will provide around 1,000 packets per second throughput in a virtual
environment. A normal router will provide a hundred to a thousand times greater throughput.
GNS3 does not take the place of a real router, but is meant to be a tool for learning and testing
in a lab environment. Using GNS3 in any other way would be considered improper.
2.1.3 Operating system

Client:-win7/win8/win10
Server:-2003/2008/2008R2/2012
2.1.4 Putty
PuTTY is a free and open-source terminal emulator, serial console and network file transfer
application. It supports several network protocols, including SCP, SSH, Telnet, rlogin, and
raw socket connection. It can also connect to a serial port. The name "PuTTY" has no
definitive meaning.
PuTTY was originally written for Microsoft Windows, but it has been ported to various other
operating systems. Official ports are available for some Unix like platforms, with work-in-
progress ports to Classic Mac OS and macOS, and unofficial ports have been contributed to
platforms such as Symbian, Windows Mobile and Windows Phone.
2.1.5 Packet Tracer

Packet Tracer is a cross-platform network simulator designed by Cisco Systems to run on Mac
OS, Linux and Microsoft Windows. A similar Android app is also available. Packet Tracer
allows users to create simulated network topologies by dragging and dropping routers,
switches and various other types of network devices. A physical connection between devices
is represented by a "cable" item. Packet Tracer supports an array of simulated Application
Layer protocols, as well as basic routing with RIP, OSPF, EIGRP, BDP, to the extents
required by the current Cisco Certified Network Associates curriculum. As of version 5.3,
Packet Tracer also supports the Border Gateway Protocol.
Version 6.0 added support for IOS version 15 and Hot Standby Routing Protocol. Version
6.1.1 added support for various DHCP, EIGRP and OSPF commands, improved support for
Zone-Based Firewall policies. As of version 6.2, Packet Tracer supports an embedded web
server with JavaScript and CSS support. The command line can be used for creating a router-
to-pc connection.
2.2 Hardware Requirement:
2.2.1 Server
In computing, a server is a computer program or a device that provides functionality for
other programs or devices, called "clients". This architecture is called the client–server
model, and a single overall computation is distributed across multiple processes or
devices. Servers can provide various functionalities, often called "services", such as
sharing data or resources among multiple clients, or performing computation for a client.
A single server can serve multiple clients, and a single client can use multiple servers. A
client process may run on the same device or may connect over a network to a server on a
different device. Typical servers are database servers, file servers, mail servers, print
servers, web servers, game servers, and application servers.
Client–server systems are today most frequently implemented by (and often identified
with) the request–response model: a client sends a request to the server, which performs
some action and sends a response back to the client, typically with a result or
acknowledgement. Designating a computer as "server-class hardware" implies that it is
specialized for running servers on it. This often implies that it is more powerful and
reliable than standard personal computers, but alternatively, large computing clusters may
be composed of many relatively simple, replaceable server components.
Server type Purpose Clients

Application Hosts web apps (computer programs that run Computers with a web
server inside a web browser) allowing users in the browser
network to run and use them, without having
to install a copy on their own computers.
Unlike what the name might imply, these
servers need not be part of the world wide
web; any local network would do.
Catalog server Maintains an index or table of contents of Any computer program
information that can be found across a large that needs to find
distributed network, such as computers, something on the network,
users, files shared on file servers, and web such a Domain member
apps. Directory servers and name servers are attempting to log in, an
examples of catalog servers. email client looking for an
email address, or a user
looking for a file
Communications Maintains an environment needed for one Communication endpoints
server communication endpoint (user or devices) to (users or devices)
find other endpoints and communicate with
them. It may or may not include a directory
of communication endpoints and a presence
detection service, depending on the openness
and security parameters of the network
Computing Shares vast amounts of computing resources, Any computer program
server especially CPU and random-access memory, that needs more CPU
over a network. power and RAM than a
personal computer can
probably afford. The client
must be a networked
computer; otherwise, there
would be no client–server
model.
Database server Maintains and shares any form of database Spreadsheets, accounting
(organized collections of data with software, asset
predefined properties that may be displayed management software or
in a table) over a network. virtually any computer
program that consumes
well-organized data,
especially in large
volumes
Fax server Shares one or more fax machines over a Any fax sender or
network, thus eliminating the hassle of recipient
physical access
File server Shares files and folder, storage space to hold Networked computers are
files and folders, or both, over a network the intended clients, even
though local programs can
be clients
Game server Enables several computers or gaming Personal computers or
devices to play multiplayer games gaming consoles
Mail server Makes email communication possible in the Senders and recipients of
same way that a post office makes snail mail email
communication possible
Media server Shares digital video or digital audio over a User-attended personal
network through media streaming computers equipped with a
(transmitting content in a way that portions monitor and a speaker
received can be watched or listened as they
arrive, as opposed downloading a whole
huge file and then using it)
Print server Shares one or more printers over a network, Computers in need of
thus eliminating the hassle of physical access printing something
Sound server Enables computer programs of a computer to Computer programs of the

play sound and record sound, individually or same computer
cooperatively
Proxy server Acts as an intermediary between a client and Any networked computer
a server, accepting incoming traffic from the
client and sending it to the server. Reasons
for doing so includes content control and
filtering, improving traffic performance,
preventing unauthorized network access or
simply routing the traffic over a large and
complex network.
Web server Hosts web pages. A web server is what Computers with a web
makes world wide web possible. Each browser
website has one or more web servers.
Table: Servers
2.2.2 Router
A router is a networking device that forwards data packets between computer networks.
Routers perform the traffic directing functions on the Internet. A data packet is typically
forwarded from one router to another router through the networks that constitute the
internetwork until it reaches its destination node.
A router is connected to two or more data lines from different networks. When a data
packet comes in on one of the lines, the router reads the address information in the packet
to determine the ultimate destination. Then, using information in its routing table or
routing policy, it directs the packet to the next network on its journey. This creates an
overlay internetwork.
TYPES OF ROUTER
STATIC DYNAMIC
We can`t add or remove the ports We can add or remove the ports.
Because Router having a fix number
of ports
for e.g.:- Cisco 2500 series for e.g.cisco 1700,
3600, 7200 etc.
2.2.3 Switch
It is intelligent device because it knows the physical address (MAC Address)
It performs broadcasting only first time.
It operates over a full duplex.
It is layer 2 & layer 3 devices.
No chance of collision
ASIC = Application Specific Integrated Circuit
It store MAC Address in CAM Table (Contained Address Memory)
TYPES OF SWITCH
Manageable Unmanageable
It is also called Configurable switch It is also called plug & play
switch
Layer 2 Layer 3(router)
It know mac address It know both addresses

MAC Address (Physical address)
IP Address (logical address)
For e.g.: - For e.g.: -

Cisco 2900, 1900 CISCO 3550, 3560,3570,4000,8500 etc.
CHAPTER 3
DOMAIN NAME SYSTEM
3.1 INTRODUCTION
3.2 INSTALLATION OF DNS SERVER
3.3 CONFIGURATION OF DNS SERVER
3.4 DNS COMMANDS
3.1 DNS (DOMAIN NAME SYSTEM):

DNS is a protocol in the TCP/IP suite of protocols. It helps in translating computer names into
ip addresses.DNS is a standard technology for name resolution, i.e., translating names into
ip.DNS is widely used in Internet and also in private networks for Name resolution.DNS is
also used in providing and locating network services in a network. In Internet, DNS translates
website names or Internet domain names into ip addresses.
DNS IN PRIVATE NETWORKS/LANs: In a private network or LAN. you can use

DNS to connect computers through names instead of using ip addresses. In a network, PCs
connect to each other through name by using broadcasting. Before DNS, hosts file was used
for name resolution. Hosts file is a text file containing list of names and ip addresses.
DNS is the best solution for name resolution in a network because broadcasting produces
network traffic and it is difficult to maintain Hosts file.
DNS NAMESPACE
DNS has a hierarchical structure. This means, in DNS, we use a main or root name and under
this root name, we can have many sub-names or child names.DNS name structure can be
compared with a tree, having root and then branches. In DNS, we use a special namespace
called DNS DOMAIN NAME in the format xyz.abc. For example, intel.com, nokia.com etc.
The dot represents Root Name. Use of Domain name helps in creating unique computer names
and two networks can use the same names but their full DNS names will always be different.
Domain Names are like area codes in the telephone network.
DNS NAMESPACE IN INTERNET

In Internet, DNS NAME starts with a dot or period called 'ROOT DOMAIN’. Under root
domain, we have top-level domain names like com, org, gov, mil etc.
What is a ZONE in DNS ?

Zone is a database containing list of names and ip addresses. In other words, Zone refers to a
DNS domain name over which DNS server has the full authority.
Zone is of two types:
Forward-Lookup Zone : DNS server having this zone can translate names into ip addresses.
Reverse-Lookup Zone: DNS server having this zone can translate ip addresses into names.
This zone is used for troubleshooting DNS service.
TYPES OF DNS SERVERS
1. Primary DNS server : It is also called Master DNS server. This DNS server had the full
authority over the zone created in it and any change can be made in the zone. The zone in this
server is called primary zone.
2. Secondary DNS server : The zone present in this server is the copy of the zone present in
the Primary DNS server. No change can be made in the secondary zone. Secondary DNS
servers are created for offering fault-tolerance and load-balancing for the DNS service.
3. Active Directory-Integrated DNS server: This DNS server is created as the result of Active
Directory Installation and it is used to provide active directory service to the clients.
4. Caching-only DNS server : This server does not contain any zone. It just stores the DNS
queries made by the clients to the other main DNS servers. When main DNS servers are not
available, clients refer to the caching-only DNS server for name resolution.
Any computer providing domain name service is a DNS server. DNS server converts host
name FQDN into IP address and IP address into host name FQDN.
Components of the DNS Server :---
DNS Query:
DNS Server Cache:
DNS Zone:
DNS Resource Record:
DNS Query:- DNS is a request for name resolution that is send to DNS server by the client
in a network. A client can send query to a DNS server or DNS server can also send a DNS
query to another DNS server.
DNS Query Are Of Two Types:
1) Recursive DNS Query: In this query DNS server did not take responsible to find best
answer for client. DNS server can forward this query to next another DNS server.
2) Iterative DNS Query: Is a query in which the client accept the best available answer
from the DNS server. In case if the server does not know the answer , it may direct
forward this query another DNS server. All Burdon on local DNS server.
DNS Server Cache: Is the temporary storage area in the DNS server that store the most
frequently or recently access records. This cache is clear when DNS service is
stopped.
DNS Resource Record:

1) Start of Authority (SOA) Record:- The first record in any database is represents the
SOA record.
2) Name Server (NS) Records:- Name server (NS) record contain the domain name
server.
3) Host (AorAAAA) Resource Records:- These record map the DNS domain name of
the computer (or host) with their IP address. Exp….. If the host name server1.abc.com
has the IP address is 192.168.0.10 server1 A 192.168.0.10
4) Alias (CNAME) Records:- This is the short name of the FQDN like this
pc1.row1.lab18.floor2.o7services.com these IP address is 50.0.0.1 this CNAME is
www.o7services.com these IP 50.0.0.1
5) Mail Exchange (MX) Record:- Used by e-mail applications to locate mail servers
with in zone.
6) Pointer (PTR) Records:- Used only to support reverse lookup zone. It converts IP
address into host name.
Note: - WINS (Windows Internet Naming Server) it convert NetBIOS into IP address. WINS
is old version of the DNS server
3.2 INSTALLATION OF DNS SERVER

1. Open Server Manager. To open Server Manager, click Start, and then click Server Manager.
Figure: Server manager
2. In the results pane, under Roles Summary, click Add roles.
Figure: Choosing DNS Server
3. Select DNS server from the list and click on next.
Figure: Overview of DNS Server
4. Click on install
Figure: Confirmation of installation
The process would take a few seconds to be installed
Figure: Installation Process
5. Click on close.
Figure: Installation Results
4.3 CONFIGURATION OF DNS SERVER

1. Open DNS server management console and right click on forward lookup zone.
2. Give the zone name e.g. lkc.local
3. Click on next.
Figure: DNS Server manager
The new Zone wizard would ask whether to create a new zone or to use an existing
one. We are creating a new zone.
4. Choose the first radio button.
5. Click on next
Figure: Adding a New Zone.
6. Click on allow both unsecure and secure updates.

7. Click on next.
Figure: Confirmation of installation selections
1) Confirm the DNS new zone selections (on the screen below) and click on finish.
Figure: Confirmation of new zone selections
8. Add all of the resource records
Figure: Resource Records
The records would be like as shown under.
Figure: Created Records
4.4 DNS COMMANDS

C:>tracert www.yahoo.com :--Command is use to check the path a data packet follow
from one router to another router.
C:>Nslookup :-- Command is display the Domain name with IP.
C:>Ipconfig /all :-Display the IP address with FQDN, IP address MAC address.
C:>ipconfig /flushdns :- Flush and reset the DNS resolver cache
C:>ipconfig /displaydns :- Display the contents of DNS resolver cache.
C:>ipconfig /registerdns :- Register any DNS names.
1. Open CMD MODE and run nslookup command
Figure: Running nslookup
2. ping the domain lkc.local
Figure: Pinging lkc.local
3. Type ipconfig /displaydns to check the DNS specifications.
Figure: DNS configurations
CHAPTER –4
DYNAMIC HOST CONFIGURATION PROTOCOL
4.1 DHCP
4.2WORKING OF DHCP SERVER
4.3 INSTALLATION OF DHCP SERVER
4.4 CONFIGURATION OF DHCP SERVER
4.1 Dynamic Host Configuration Protocol (DHCP)

DHCP (Dynamic Host Configuration Protocol) is a protocol that lets network administrators
manage centrally and automate the assignment of IP (Internet Protocol) configurations on a
computer network. When using the Internet's set of protocols (TCP/IP), in order for a
computer system to communicate to another computer system it needs a unique IP address?
Without DHCP, the IP address must be entered manually at each computer system. DHCP lets
a network administrator supervise and distribute IP addresses from a central point. The
purpose of DHCP is to provide the automatic (dynamic) allocation of IP client configurations
for a specific time period (called a lease period) and to eliminate the work necessary to
administer a large IP network.
IP Address is a logical address of the computer. It use for identify of computer this is unique
same as telephone number. IP is a 32 bit address. Computer networking are depend on ip
address.
IP Address are two types: --------
• STATIC IP: - Provide by User this IP cannot change automatically.
• DYNAMIC IP: - Provide by DHCP Server this is can be change automatically.
STATIC IP DYNAMIC IP
• Required more time to fill ip address • Required less time to fill ip address
• IP List maintain by user • IP List maintain by DHCP Server
• Human Error • No chance
• PC shuffle Problem • No Problem
Why Is DHCP Important

When connected to a network, every computer must be assigned a unique address. However,
when adding a machine to a network, the assignment and configuration of network (IP)
addresses has required human action. The computer user had to request an address, and then
the administrator would manually configure the machine. Mistakes in the configuration
process are easy for novices to make, and can cause difficulties for both the administrator
making the error as well as neighbors on the network. Also, when mobile computer users
travel between sites, they have had to relive this process for each different site from which
they connected to a network. In order to simplify the process of adding machines to a network
and assigning unique IP addresses manually, there is a need to automate the task.
The introduction of DHCP alleviated the problems associated with manually assigning TCP/IP
client addresses. Network administrators have quickly appreciated the importance, flexibility
and ease-of-use offered in DHCP.
4.2 Working of DHCP Server:

1. DHCP Scope
2. DHCP Super Scope
3. Exclusion ip range
4. DHCP Lease Time
5. IP reservation
1. DHCP Scope :- Scope having the range of ip address for provide dynamic ip address to
other computer. A group of ip address within a subnet is called as a scope.
2. DHCP Super Scope:- A super scope can be used to combine two or more scope each
serving different different network.
3. Exclusion IP Range :- If you want to reserve some IP for any computer.
4. DHCP Lease Time:- DHCP lease time is validity of IP address. By default DHCP lease
time 8 days minimum 1 day
maximum 999 days, 23 Hours, 52 minute.
With in 8 days
after 50% of days client demand the new ip, some time server refuse the client request, After
87.5% of day it will retry. If server did not give the new ip address than client receive APIPA
address
Automatic Private IP Address
Exp:- IP Address 169 . 254 . *. *
Subnet Mask 255. 255 . 0 . 0
3. IP Reservation:- We can reserve IP address with the help of MAC address for
particular computer
DHCP Lease Process:
The DHCP lease process consists of a four packet conversations between the DHCP
Server and DHCP Client. We called DORA system to this conversation
Automatic IP Configuration
DHCP supports Automatic Private IP Addressing (APIPA), which enables computers running
Windows 2000, Windows XP, and Windows Server 2003 to configure an IP address and
subnet mask if a DHCP server is unavailable at system startup and the Automatic private IP
address Alternate Configuration setting is selected. This feature is useful for clients on small
private networks, such as a small-business office or a home office.
The DHCP Client service on a computer running Windows XP and Windows Server 2003
uses the following process to auto-configure the client:
1. The DHCP client attempts to locate a DHCP server and obtain an IP address and
configuration.
2. If a DHCP server cannot be found or does not respond after one minute, the DHCP
client checks the settings on the Alternate Configuration tab of the properties of the
TCP/IP protocol.
If Automatic private IP address is selected, the DHCP client auto-configures its IP

address and subnet mask by using a selected address from the Microsoft-reserved
Class B network, 169.254.0.0, with the subnet mask 255.255.0.0. The DHCP client
tests for an address conflict to ensure that the IP address is not in use on the network. If
a conflict is found, the client selects another IP address. The client retries auto-
configuration up to 10 times.
If User Configured is selected, the DHCP client configures a static IP address
configuration. The DHCP client tests for an address conflict to ensure that the IP
address is not already in use on the network. If a conflict is found, the DHCP client
indicates the error condition to the user.
3. When the DHCP client succeeds in self-selecting an address, it configures its network
interface with the IP address. The client then continues to check for a DHCP server in
the background every five minutes. If a DHCP server responds, the DHCP client
abandons its self-selected IP address and uses the address offered by the DHCP server
(and any other DHCP option information that the server provides) to update its IP
configuration settings.
If the DHCP client obtained a lease from a DHCP server on a previous occasion, and the lease
is still valid (not expired) at system startup, the client tries to renew its lease. If, during the
renewal attempt, the client fails to locate any DHCP server, it attempts to ping the default
gateway listed in the lease, and proceeds in one of the following ways:
 If the ping is successful, the DHCP client assumes that it is still located on the same
network where it obtained its current lease, and continues to use the lease as long as
the lease is still valid. By default the client then attempts, in the background, to renew
its lease when 50 percent of its assigned lease time has expired.
 If the ping fails, the DHCP client assumes that it has been moved to a network where a
DHCP server is not available. The client then auto-configures its IP address by using
the settings on the Alternate Configuration tab. When the client is auto-configured, it
attempts to locate a DHCP server and obtain a lease every five minutes.
4.3 INSTALLATION OF DHCP SERVER

To start the DHCP installation process, you can click Add Roles from the Initial
Configuration Tasks window or from Server Manager / Roles / Add Roles. When the add
roles Wizard comes up,we can click Next on that screen.
2) First of all we have to select the role ie. DHCP server from the server manager and
then click on Next button.
Figure: Role selection
The wizard will show the introduction to DHCP server. We can get more information about
DHCP server from here.
Figure: introduction to DHCP server
At this point we will begin being prompted for IP network information, scope information and
DNS information. If we only want to install Dhcp server with no configured scopes or
settings, we can just click on the Next through these questions and procees with the
installation.
On the other hand I have optionally configured the DHCP server.
In my case I chose to configure some basic IP settings and configure the first DHCP scope.
3) Select the IP address and click Next.
Figure: Network Connection Bindings
4) Write the name of the parent domain and specify the IP address. Then click on the next
button.
Figure :IPv4 DNS server settings
Here the WINS (Windows Internet Naming Services) is to be specified. As it is not required
for the applications on this network so we have to choose the first option.
5) Choose the first option: WINS is not required for applications on this network.
Figure: WINS server settings
Then, I was promoted to configure a DHCP scope for the new DHCP Server. I have opted to
configure an IP address range of 20.0.0.100-200. To do this,
5) I clicked Add to add a new scope. As you see below, I named the Scope LKC, configured
the starting and ending IP addresses of 20.0.0.100-20.0.0.200, subnet mask of 255.0.0.0
and activated the scope.
Figure: Adding a new scope
The wizard will ask to add or edit DHCP scopes but at the moment we do not need any so we
will simply proceed by selecting Next.
6) Click the Next button.
Figure: Adding or editing DHCP scopes
7) Choose to Disable DHCPv6 stateless mode for this server and click Next.
Figure: Disabling DHCPv6 stateless mode
8) Choose Skip authorization of this DHCP server in AD DS
Figure: skipping DHCP authorization in AD DS
9) Confirm the DHCP Installation Selections (on the screen below) and click on Install.
Figure: Confirmation of installation selections
After only a few seconds, the DHCP Server will be installed and I saw the window, below:
Figure : Installation succeeded
4.4 CONFIGURATION OF DHCP SERVER

If we have to configure the scopes,if we did not do it during the installation process then
follow the following steps.
1) Go to the start menu > Administrative tools > DHCP and click on DHCP.
After choosing DHCP, the screen which pops out is shown as under. To create a new scope
we need to follow the following steps.
2) Select the IPv4 as we used IPv4 address. Right click on IPv4 from the left panel and
select New scope.
Figure: DHCP Server Manager
A New scope wizard will appear on the screen as shown under.

Figure: New scope wizard welcome page
4) Enter the scope name and a description (optional) and click on Next.
Figure: Scope name
5) Enter the range of IP address for the scope.

Here I have used 30.0.0.100 as a starting IP address and 20.0.0.200 as the ending IP
address followed by 8 (prompted) as the length that propagates DHCP client and 255.0.0.0
as the subnet mask.
Figure: IP address range
Exclusion:
We also can exclude some IP addresses which we do not want to distribute among the
computers in the network but specifically assign them to particular computers or machines.
6) Specify the starting and ending IP address. I have used range of 5 which includes the
IP addresses from 30.0.0.100 to 30.0.0.105 .
7) Click on Add and then next.
We can repeat the above 2 steps if we want to add more excluded addresses.
Figure: Adding exclusions
The wizard will show the by default lease duration of a distributed IP address to a machine. It
can also be changed by using the up and down buttons. I have not changed it and let it remain
the same.
8) Click the Next button
Figure: Lease duration
9) Choose the second option ie: NO, I will configure these options later.
Figure: Skipping the configurations of other DHCP options
The wizard will show the completion page.

11) Click finish to finish the New scope wizard.
Figure: Completion of new scope wizard
After we created a new scope, it be shown in the left panel.
Figure:DHCP Server manager
CHAPTER 5
ACTIVE DIRECTORY
5.1 INTRODUCTION
5.2 TYPES OF ACTIVE CONTROLLER
5.3 INSTALLATION OF ACTICE DIRECTORY
5.4 CONFIGURATION OF ACTIVE DIRECTORY
5.5 GROUP POLICY MANAGEMENT CONSOLE
5.1 Active Directory (AD)

We can manage all users and security centralizes with the help of ADS. In simple terms, AD
is a database containing list of user accounts, computer accounts, shared folders, printers,
groups and group policy objects present in the domain network. The service running AD is
called Active Directory Service (ADS). Client PCs use the protocol LDAP (Lightweight
Directory Access Protocol) to access the ADS. Port Number use 389 in LDAP.
Use of DNS in Domain Network

DNS in the Microsoft Domain Network helps in the following ways:
1. DNS provides ADS service to the clients.
2. Clients locate DCs through DNS.
3. DNS provides Name Resolution Service in the network.
4. Active Directory Domain Network is given the same name as the DNS domain
network
5.2 Types of Active Directory

1. Domain.
2. Domain Controller.
1. Domain.
A domain is a group of computer connected logically in a network. The domain enables the
system administrator to simplify the process of managing the computer and user on the
network.
Types of Domain
1. Domain forest.
A forest is created when you configure the win 2k3 server computer as a domain controller. A
forest is a collection of multiple domain link together and relationship between the domains.
You can add domain tree and domain in a forest.
2. Domain Tree.
A domain tree is made up when there is a parent child relationship between domains in a
forest. The child domain name must include the complete parent domain name.
A tree is set of two or more domains sharing common namespace. For example, we can create
a parent domain and then a child domain. (mail.yahoo.com) mail child domain yahoo parent
domain.
Fig 4.2.1: Domain Forest
3. Domain Controller.
 PDC – Primary Domain Controller.

 ADC - Additional Domain Controller.
 CDC- Child Domain Controller.
 RODC-Read Only Domain Controller
 NTR-NEW TREE ROOT
1. PDC – This is first domain controller in the domain all entrees are created in it like
user account, group policy OU etc.
2. ADC – This is true copy of the PDC. This domain controller is use for fault tolerance
and load balance. All Active Directory database is replicated automatically with PDC.
4. CDC – This domain controller is sub domain of the PDC. This is use for load
balancing
5. RODC -A read-only domain controller (RODC) is a server that hosts an Active Directory
database's read-only partitions and responds to security authentication requests.
6. NTR-Create a new domain tree only when you need to create a domain whose DNS
namespace is not related to the other domains in the forest.
 New Tree Root (NTR)

Create a new domain tree only when you need to create a domain whose DNS namespace is
not related to the other domains in the forest. This means that the name of the tree root domain
(and all of the its children) does not have to contain the full name of the parent domain. To
create a new domain tree, you need to promote a Windows Server 2008 computer toa domain
controller. In the Active Directory Installation Wizard, you select the option that makes this
domain controller the first machine in a new domain that is a child of an existing domain. As a
result, you will have a domain tree that contains two domains—a parent and a child. Before
you can create a new child domain, you need the following information:
 The name of the parent domain
 The name of the child domain (the one you are planning to install)
 The file system locations for the Active Directory database, logs, and shared system
volume.
 DNS configuration information

 The NetBIOS name for the new server
 A domain administrator username and password.
 Read Only Domain Controller (RODC)

Read Only Domain Controller are a new features of active directory domain service in
window server 2008. A RODC is a server that hosts an active directory databases read
only partition and responds to security authentication requests. RODC which was designed
to be used in branch offices that cannot support their on domain controllers can be used in
a windows server 2008 environment or higher.
Advantages of Read Only Domain Controller:
a) Password Replication Policy ensures more security in case of compromised scenario.
b) Unidirectional replication should be enabled from Melbourne (RWDC )to Perth (RODC)
which
Provides enhanced security for the data on the Read Only Domain Controllers. In the event
of
RODC compromise, no data can be retrieved
c) Enterprise applications can point to specific RODC and restrict their replication of data to
other RODC , this ensures that critical and secured Applications data will not write to
RODC.
5.3 HOW TO INSTALL ACTIVE DIRECTORY

1. Here we provided an ip address of 20.0.0.2 with subnet mask 255.0.0.0
which is connected to the dns server having ip (20.0.0.1).
Fig 4.2.1: Local Area Connections
2. Shows the computer description as a workgroup which means it is neither a

member nor domain itself.
Fig 4.2.1: System Specifications.
3. Shows the ser322 sending and receiving packets with dns server to ensure
communication.
Figure: Sending and Receiving packets
4. Run a command “dcpromo.exe” to install active directory.
Figure: Run DCPROMO to install AD
5. As the figure shows it checks if the binaries of active directory domain services are
already installed.
Figure: Searching Binaries
6. Welcome wizard will be displayed on the screen. Click next to continue.
Figure: Welcome Wizard
7. This page describes the compatibility of operating system.

8. Click next.
Figure: Compatibility of OS
9. This wizard provides two options:

Either you can create a new forest or you can create a different domain in the same
forest.
10. Click next.
Figure: Choosing Forest
11. Here it asks to provide a full description of domain name that you wish to proceed
with.
Figure: Give Domain Name
12. Provide a NETBIOS name of the domain so that the previous windows users are
able to connect to this domain.
Figure: NETBIOS Name
13. In the active directory installation wizard, it asks for the forest functional level and
provides a drop down list to choose from.
Figure: Choosing Forest Functional level
14. As the forest level, the next step is to select a domain functional level from the
drop down list.
Figure: Choosing Domain Functional level
15. In additional domain controller options, it asks if you want to install dns server
service on this domain. If yes, select the DNS option under the ‘select additional
options for this domain’.
Figure: Installation of DNS Server
If you already have another DNS server, then click next without checking the DNS
option. Your provided DNS will be used.
Figure: DNS Server Option
16. Next step shows the path where database, log files as well as the SYSVOL folders
would be stored. You can change the location by providing another path through
browse.
Figure: storage of database
17. Here it asks for the ‘directory restore mode administrator password’. One thing you
need to remember is that the ‘restore mode administrator account’ is different from
the ‘domain administrator account’.
Figure: Setting Username and Password
18. In the installation wizard, this step gives summary of every option you choose
while creating domain. You can also save the settings for further use by exporting
the summary on another volume.
Figure: Summary of options used
19. As you click next, it checks for the group policy management console.
20. After installation it will ask to restart the server.
Figure: Checking Group Policy Management Console
21. In Server Manager install the roles of Active Directory.
Figure: AD server manager
5.1 Configuration of Active Directory

1. In the start menu, under administrative tools various active directory services
would have been installed. Active Directory Users and Computers is one of them.
Figure: AD server manager
2. Your created domain name ‘it.lkc.local’ would be shown on the left side. Right
click on the domain ‘lkc.local’ and create a new organisational unit under the name
‘IT’.
3. It provides the facility to protect database from accidental deletion.
Figure: Creating New User
4. Now in the OU named ‘IT’ , create a user with first name, user logon name and
click next.
Figure: Filling Details
5. This wizard asks to set a password for a specific user.

6. It also grants the permissions like password never expires or the user can change
password by himself or not etc.
Figure: Set Password and Password Permissions
7. Full details of a particular user are shown, if you want to change any detail you
may go back to those steps. Else click finish and the user would be created.
Figure: Confirming User Details
8. Under the IT OU the list will be provided with all the details of users created in
lkc.local.
Figure: Created List of Users
9. Right click on the user and go to properties. Here you can edit any stting or
permission of this user related to account, profile or environment etc.
Figure: User Properties
10. Right click the user and choose the group from the select groups dialogue box.
Figure: Choosing groups window
11. In the object types, choose the group which you want.
Figure: Choosing Group
5.5 Group policy management

1. Under the lkc.local, right click the IT OU .
2. Right click on create a GPO in this domain.
Figure: Applying Group Policies
3. Go to the user properties and create a home folder with the volume Z and
provide the path where you want to create the folder in domain.
Figure: Creating Volume and Providing Path
4. Create a new GPO under the organisational unit emp, named “obj1”.
Figure: Creating GPO
5. Right click on the obj1 and select edit.
Figure: Editing GPO
6. Under the group policy management you can select from computer as well as user
configuration.
Figure: Selection from computer or user configuration
7. You can choose policies from the list of available policies.
Figure: List of policies
8. You can also provide desktop permissions.
Figure: Permissions
9. Policies are shown below to choose from and the policies are applied.
Figure: Choosing and Applying Policies
CHAPTER 6
WINDOWS DEPLOYMENT SERVICES
6.1 INTRODUCTION
6.2 Installation of WDS Server
6.3 Configuration of WDS Server
6.4 Add install images to Windows
6.5 Adding boot image to windows
6.6 Adding Drivers
6.1 Windows Deployment Services

Windows Deployment Services is a server technology from Microsoft for network-
based installation of Windows operating systems. It is the successor to Remote
Installation Services.[1] WDS is intended to be used for remotely deploying
Windows Vista, Windows 7, Windows 8, Windows Server 2008, and Windows
Server 2012, but also supports other operating systems because unlike its
predecessor RIS, which was a method of automating the installation process, WDS
uses disk imaging, in particular the Windows Imaging Format (WIM). WDS is
included as a Server Role in all 32-bit and 64-bit versions of Windows Server
2008, and is included as an optionally installable component with Windows Server
2003 Service Pack 2.
Automated image capture and apply
WDS functions in conjunction with the Preboot Execution Environment (PXE) to
load a miniature version of Windows known as Windows PE for installation and
maintenance tasks. WDS functions as both a storage repository for the PXE
network boot images as well as a repository for the actual operating system images
to be installed on the target computer.
When multiple boot images are available, PXE booting via WDS will present the
end-user with a boot menu to select the image to load.
Windows PE automation using WAIK
To simplify the tasks of capturing and applying images, two special scripted
Windows PE boot images can be created which automate these tasks. These
scripted Windows PE boot images are created using the Windows Automated
Installation Kit, in combination with Windows 7 installation media containing the
source WIM images, and then added to the WDS server's boot image repository.
The Windows PE boot images may be either 32- or 64-bit, but 32-bit tends to be
more universally compatible across all potential hardware types.
A difficulty of Windows PE booting is that it needs to include network drivers and
disk controller drivers intended to work with the target hardware to be imaged. The
process of adding drivers to the Windows PE boot image can be automated using
the WDS server console:
1. Select the source WIM image, which may be either a new one created from
original Windows 7 installation DVDs (32- or 64-bit), or a previously
configured WIM.
2. Select the drivers to install into the WIM
3. WDS mounts the WIM to a virtual path, adds drivers to the virtual path, and
generates a new WIM
4. The updated WIM image is added to the boot image section of the WDS
repository
This process can be repeated at a later time when a new system type needs to be
captured but the current Windows PE Capture boot image does not include network
drivers for it. The boot image is updated with the additional drivers using the WDS
interface and automatically re-added to the WDS boot image collection to replace
the original.
For specialty one-off systems this WIM driver update process is not necessary if
the hard drive of the target system to be captured is removed from the source
system after sysprepping, and is either installed in a computer with supported
network drivers, or attached to the supported system using an external "USB to
hard drive" adapter.
Automated apply process
Applying a captured image involves running a second Windows PE "Apply" boot
image on the target system to receive the image. This boot image also needs the
appropriate network and disk controller drivers as with the Windows PE Capture
boot image.
1. The system is booted using PXE network booting and the Windows PE
Apply image is loaded.
2. The operator logs on to the domain, and selects the boot image to apply.
3. A disk partitioning screen appears and the location for the target image is
selected. If the target storage is unformatted, a default partition set is
created. For Vista and Windows 7, a small 100 megabyte boot partition is
created for storing bootloader data
4. separate from the rest of the system partition. This boot partition is
normally hidden from the Windows Vista/7 user.
5. The image data is applied to the selected partition, and the system reboots,
either running the Sysprep manual mini-setup process or following the
script created during the initial Sysprepping.
The WDS image creator may optionally select a separate WAIK / Sysprep
installation script to be applied to the image during the first boot. This alternate
script is selected within WDS by viewing the properties of each uploaded system
image.
WDS automation and dual-boot systems
WDS automated capture and apply do not directly support dual-boot operating
systems. Only one operating system at a time can be captured and deployed, and
the automated capture process only deals with single partitions containing a
sysprepped Windows OS installation. It will not capture data-only partitions.
However, WDS automated capture and apply can be used to duplicate and create
dual-boot systems, if each OS is captured and applied separately. Generally,
Windows XP and older operating systems need to be applied to the target system
before Vista or Windows 7, due to the different boot loaders used by the newer
operating systems.
Manual image capture and deploy
It is technically possible to create scripts that manually perform the imaging,
capture, and apply processes, using command line tools provided by Microsoft.
However, the methods for doing this are complex and difficult.
Tools Involved
 dism - Deployment Image Service and Management Tool, used to add
drivers to Windows PE boot images.
 imagex - used to capture and apply images. Creates either a single WIM
structure, or can deduplicate data using a second shared resource WIM.
Does not require a Windows Deployment Server to capture or apply
images, and can work solely with a logged-on network share or mapped
drive letter.
 wdsutil - used to manage the WDS server without the graphical user
interface, and to add captured images to the repository.
Using imagex to manually create a WIM does not require the source operating
system to be sysprepped or for the source partition to contain a Windows operating
system. Any type of Windows-accessible file system can be imaged, including
MSDOS, but the source system either needs to be able to run Windows PE or the
source system's hard drive is moved into a newer system that supports Windows
PE.
Microsoft generally requires Windows 2000, XP, Vista, and Windows 7 to be

sysprepped before imaging, due to certain security-related disk data that Microsoft
requires to be unique across duplicated system images. Sysprep randomizes this
data when the image is applied to a new system.
Imagex does not have any disk formatting and partitioning capabilities. Separate
Windows command line tools such as diskpart are needed to define partitions on
the target system for imagex to use.
6.2 Installation of WDS Server

Steps for installing Windows Deployment Services
You can install Windows Deployment Services by using the Initial Configuration Wizard,
Server Manager, or the command line.
 To install the role by using the Initial Configuration Wizard, in the Server manager
click Add roles on the Initial Configuration Tasks startup screen. Click Next and
then select Windows Deployment Services.
Figure: Selection of WDS role.
The Add roles wizard opens up and introduces WDS. We can get more information about
WDS server from here.
Figure: Overview of WDS role.
Here ensure that both Deployment Server and Transport Server are selected on the
second screen of the installation wizard. This is the most common option because it
provides the full functionality of Windows Deployment Services, which you can use to
configure and remotely install Windows operating systems. Note that Deployment
Server is dependent on the core parts of Transport Server.
2) Tick the both options i.e. Deployment server and Transport Server and then proceed by
clicking on the Next button
Figure: Selecting the role services.
The wizard will confirm the installation selections.

3) Check the choices made and click the Install button.
Figure: Confirm installation services.
The process would take a few seconds to be installed
Figure: Installation Process.
A message of installation success will appear .

6) click the Close button to proceed.
Figure: Installation results.
6.3 Configuration of WDS Server

To configure the server role, use the following procedure. Then see the following section to
add images to the server.
1. Ensure that you are a Domain Administrator.
2. Click Start, click Administrative Tools, and then click Windows Deployment
Services.
3. Right-click the server, and then click Configure Server
Figure: Windows Deployment Services home page.
4. Follow the instructions in the wizard and click the Next button.
Figure: Windows Deployment Services configuration wizard.
5. Browse for the folder where we want to place the remote installation files. By default it is the
Remote install folder in C drive.
6. Click ok .
Figure: Remote installation folder location.
7. Change the path to the remote installation folder and click on the Next button
Figure: Specifying folder path.
8. Tick both the options and click on the Next button.
Figure: Selecting options.
9. Choose the last radio button asking to respond to all client computers.
10. Click on the Next botton.
Figure: PXE server initial settings.
The server task will start progressing. After it is done, the Finish button will be highlighted then click
on the Finish button
If any error occurs as in the figure shown below, follow the recovering the error steps.
Figure: Task progress.
Recovering the error

If the service do not respond to the start or control request in a timely fashion
1. Then start the services.
Figure: Starting services.
It may take a few seconds in resolving the error and a success message will pop up on the
screen after resolving the error as shown in figure.
Figure: Starting successfully WDS
6.4 Add install images to Windows:

 Install images. Install images are the operating system images that you deploy to the
client computer. You can use the Install.wim file from the product DVD to deploy
images for Windows Vista, Windows Server 2008, Windows 7, and Windows Server
2008 R2. For operating systems released prior to Windows Vista, you must create a
custom install image.
To add the Install.wim from the product DVD, use the following procedures.
1. In the Windows Deployment Services MMC snap-in, right-click the Install
Images node, and then click Add Install Image.
Figure: WDS Image Installation
1. Specify a name for the image group, and then click Next.
Figure: Naming Image Group
2. Click on Browse... to select the default install image.
Figure: Browsing image file
3. Select the default install image (Install.wim), which is located in the \Sources folder of
the product DVD, and then click Open.
Figure: Image File Location
4. To add a subset of the images included in the Install.wim file, clear the check boxes
for the images that you do not want to add to the server. You should add only the
images for which you have licenses.
Figure: Selecting licensed Image
The wizard will confirm the chosen windows image.

5. Click on the Next button
The image will be added.
Figure: Confirmation and Installation
6.5 Adding boot image to windows
1. In the left pane of the Windows Deployment Services MMC snap-in, right-click
the Boot Images node, and then click Add Boot Image.
Figure: WDS Boot Image
2. Browse to choose the default boot image (Boot.wim) on the external hard drive,
located in the \Sources folder.
3. Click Open.
Figure: Browsing Boot Image
4. Click Next.
Figure: Boot image location
5. Enter the name and description for the chosen boot images.
6. Click on the next button.
Figure: Specified Boot Image Name and Description.
The wizard will confirm the chosen windows image.

6. Click on the Next button
Figure: Boot image Confirmation
The server task will start progressing. After it is done, the Finish button will be highlighted
then click on the Finish button
The boot image will be added.
Figure: Adding Boot Image
6.6 Adding Drivers

To add the default drivers included on the product hard drive use the following procedures.
1. In the Windows Deployment Services MMC snap-in, right-click the Drivers node,
and then click Add Driver Package.
Figure: WDS Drivers
1. Choose the first option.

2. Click on Browse... to select the default install image.
Figure: WDS Driver Package Location
3. Select the driver package location , which is located in the \Support folder of the
product drive, and then click Open.
Figure: WDS Driver location browsing.
The server task will start progressing. After it is done, the Finish button will be highlighted
then click on the Next and then on Finish button
The driver package will be added.
Figure: WDS Drivers installation progress
CHAPTER 7
ROUTING AND SWITCHING
7.1 PLANNING AND DESIGNING
7.2 IMPLEMENTATION AND OPERATION
7.3 PROCESS DESCRIPTION
7.4 VIRTUAL LAN
7.5 COMMANDS TO CREATE VLAN
7.6 CODING
7.1 PLANNING AND DESIGNING

–Design a simple LAN using CISCO technology
-Design an IP addressing scheme to meet design requirement
- Select an appropriate routing protocol based an user requirement
- Design a simple interanet using CISCO technology
- Develop an access list to meet user specifications
- Choose wan services to meet customer requirement
7.2 IMPLEMENTATION AND OPERATION

- Configure routing protocols given user requirements
- Configure IP addresses, subnet masks and gateway addresses on routers and hosts
- Configure a router for additional administrative functionality
- Configure a switch with VLANS and inter-switch communication
- Implement a LAN
- Customize a switch configuration to meet specified network requirements.
- Manage systems image and device configuration files
- Perform an initial configuration on a router
- Perform an initial configuration on a switch
- Implement access lists
- Implement simple WAN protocols
7.3 PROCESS DESCRIPTION:-

To acquire VLAN: Configuring VLAN’s is actually pretty easy .Figuring out which user you
want in each VLAN is not extremely time consuming but once you have decided the number
of VLAN’s you want to create and establish. To configure VLAN’s on cisco switch, use the
global configuration VLAN command.
Here in this project we have created 3 VLAN’s in the following way:

S1#config t
S1(config)#vlan 10
S1(config)#name CSE
S1(config)#vlan 20
S1(config)#name ECE
S1(config)#vlan 30
S1(config)#name IT
7.4 VLAN (Virtual LAN):-
VLAN provides Virtual Segmentation of Broadcast Domain in the network. The devices,
which are member of same VLAN, are able to communicate with each other. The devices of
different VLAN may communicate with each other with routing. So that different VLAN
devices will use different n/w addresses. VLAN provides following advantages: -
(1) Logical Segmentation of network
(2) Enhance network security
Creating port based VLAN

In port based VLAN, first we have to create a VLAN on manageable switch then we have to
add ports to the VLAN.
7.5 Commands to create VLAN

Switch#config ter
Switch(config)#vlan <no> [name <word>]
Switch(config)#exit optional
Or
Switch#vlan database
Switch(vlan)#vlan <no> [name <word>]
Switch(vlan)#exit
Commands to configure ports for a VLAN

By default, all ports are member of single VLAN that is VLAN1. we can change VLAN
membership according to our requirement.
Switch#conf ter
Switch(config)#interface <type> <no>
Switch(config-if)#switchport access vlan <no>
Switch(config-if)#exit
Commands to configure multiple ports in a VLAN
Switch#conf ter
Switch(config)#interface range <type> <slot/port no (space)–(space) port no>
Switch(config-if)#switchport access vlan <no>
Example: - Suppose we want to add interface fast Ethernet 0/10 to 0/18 in VLAN5
Switch#config ter
Switch(config)#interface range fastethernet 0/10 – 18
Switch(config-if)#switchport access vlan 5
Switchconfig-if#exit
In 1900 & Compatible switches

Switch#config ter
Switch(config)#interface <type> <no>
Switch(config-if)#vlan-membership static <vlan no>
To Disable web access in switch

Switch#config ter
Switch(config)#no ip http server
To display mac address table
Switch#sh mac-address-table
Vlan Mac address type ports

20 00-08-a16-ab-6a-7b dynamic fa0/7
To Display VLAN and port membership
Switch#sh vlan
7.6 Coding
IN ORDER TO AVOID THE CODING FROM BEING COMPLEX WE HAVE DIVIDED

THE CODING INTO NUMBER OF STEPS.
STEP 1:
CODING OF SWITCH 1:
Switch1> en
Switch1#config t
Switch1(config)#vtp mode client
Switch1(config)#vtp domain cisco
Switch1(config)#int fastEthernet 0/1
Switch1(config-if)#switchport mode access
Switch1(config-if)#switchport access vlan 2
Switch1(config-if)#exit
Switch1(config)#int fastethernet 1/1
Switch1(config-if)# switchport mode access
Switch1(config-if)#switchport mode trunk
CODING OF SWITCH 2:
Switch2> en
Switch2#config t
CODING OF SWITCH 3:
Switch3> en
Switch3#config t
CODING OF SWITCH 4:
Switch4> en
Switch4#config t
STEP 2:
CODING OF SWITCH 5:
Switch5> en
Switch5#config t
Switch5(config-if)# switchport mode trunk
CODING OF SWITCH 6:
Switch6> en
Switch6#config t
CODING OF SWITCH 0:
Switch)0> en
Switch0#config t
Switch0(config)#vtp mode server
Switch0(config)#vlan 2
Switch0(config)#name sales
Switch0(config)#name marketing
Switch0(config)#name engineering
Switch0(config)#name production
Switch0(config)#exit
Combining both steps 1&2 we get our scenario having vlanship:
Now the host belonging to same vlans can communicate with each other. In this scenario
1. Pc 0, Pc 4, Pc 8 are grouped into VLAN 2 i.e. sales department.

2. Pc 1, Pc 5, Pc 9 are grouped into VLAN 3 i.e. marketing department.
3. Pc 2, Pc 6, Pc 10 are grouped into VLAN 4 i.e. engineering department.
4. Pc 3, Pc 7, Pc 11 are grouped into VLAN 5 i.e. production department.
So each host in same department can communicate with each other but cant communicate
with host of other departments.
Pc 0 of sales department communicating with Pc 8 also belonging to sales department:
Reply from PC 8 having ip address 10.0.0.3 is obtained thus indicating a successful

communication between both the host.
PC 1 of marketing department communicating with PC 9 also belonging to marketing

department:

PC 2 of engineering department communicating with PC 10 also belonging to engineering

department:

communication between both the host
PC 3 of production department communicating with PC 10 also belonging to production

department:

Now if we want that host belonging to different vlans can communicate with each other
we have to introduce the concept of inter VLANship . For this we need to introduce a
router at uppermost position as ISP [internet service provider]. Then host’s belonging to
different VLANs can communicate with each other through that router.
The coding of switch 0, switch 1 and switch 2 has been described earlier. Here we will
describe coding of the router.
CODING OF ROUTER:
Router> en
Router #config t
Router(config)#int fastethernet 0/0
Router(config-if)#no ip address
Router(config-if)# no shutdown
Router(config-if)#exit
Router(config)#int fastethernet 0/0.1
Router(config-if)#encapsulation dot1q 2
Router(config-if)#ip address 10.0.0.4 255.0.0.0
Router(config-if)#exit
Router(config-if )#encapsulation dot1q 3
Router(config-if )#ip address 20.0.0.4 255.0.0.0
Router(config-if )#exit
Scenario having inter VLANship:
Now in this scenario the hosts belonging to different VLANs can communicate with each
other.
PC 0 belonging to sales department communicating with PC 9 and PC 10 belonging to

marketing department and engineering department respectively:
A positive reply indicating successful communication.
PC 1 belonging to marketing department communicating with PC 8 and PC 10 belonging

to sales department and engineering department respectively:
A positive reply indicating successful communication.
PC 2 belonging to engineering department communicating with PC 9 and PC 11 belonging to

marketing department and production department respectively:
A positive reply indicating successful communication
CHAPTER 8
8.1 CONCLUSION
8.2 FUTURE SCOPE
8.1 Conclusion
According to the structure ,we need to centralize the database and to overcome this need, we
placed a Primary Domain Controller in the Network and to restrict users from some non-
work related services and to give access to resources, Group Policy Objects came into the
picture.
In locations where the clients and Windows Deployment Services servers are separated by a
router, Routing and switching is configured.
The project was successful in overcoming the disadvantages of a manually assigning the IP
addresses by using DHCP Servers. The networks located in two different places could share
their data with the help of trust created between PDC and NTR.
We can manage the whole network from the core device at a site.
8.2 Future Scope

In Future, Windows Deployment Services servers could be separated by a router. A
mechanism for discovering the Windows Deployment Services servers can be determined.
The method for Windows Deployment Services discovery can be recorded so that it can be
implemented at deployment.
The destination ports can be guarded as an unauthorized person can also deploy windows to a
system.
We can implement more security on this project, using VPN (Virtual Private Network). We
can add a new college site by adding a new Primary Domain Controller or NTR.
CHAPTER 9
BIBLIOGRAPHY
1. Book: MCITP Enterprise Administrator Core Requirements

Author: Dan Holme, Danielle Ruest, Nelson Ruest
2. Book: Windows Server 2008 Enterprise Administrator Study Guide
Author: Samuel Johnson
3. Book: CCNA Routing and Switching Complete Study Guide:
Author: Todd Lammle
4. Book: CCNA Routing and Switching
Author: Wendell Odom
Websites links:
www.networksolutions.com
www.wikipedia.org
www.technet.microsoft.com
www.cisco.com

4.all Chapters

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

4.all Chapters

Hochgeladen von

Copyright:

Verfügbare Formate

IMPLEMENTAION OF WINDOWS DEPLYOMENT SERVICES IN INTRANET

1.1 INTRODUCTION TO THE PROJECT:

1) Centralization: Unlike P2P, where there is no central administration, here in this

4) Up gradation and Scalability in Client-server set-up: Changes can be made easily by

5) Accessibility: From various platforms in the network, server can be accessed

8) Servers can play different roles for different clients.

VMware vSphere leverages the power of virtualization to transform datacenters into

2.1.3 Operating system

2.1.5 Packet Tracer

2.2 Hardware Requirement:

Server type Purpose Clients

Sound server Enables computer programs of a computer to Computer programs of the

Layer 2 Layer 3(router)

It know mac address It know both addresses

For e.g.: - For e.g.: -

3.1 DNS (DOMAIN NAME SYSTEM):

DNS IN PRIVATE NETWORKS/LANs: In a private network or LAN. you can use

DNS NAMESPACE IN INTERNET

What is a ZONE in DNS ?

TYPES OF DNS SERVERS

Components of the DNS Server :---

DNS Query Are Of Two Types:

DNS Resource Record:

3.2 INSTALLATION OF DNS SERVER

Figure: Server manager

2. In the results pane, under Roles Summary, click Add roles.

Figure: Choosing DNS Server

3. Select DNS server from the list and click on next.

Figure: Overview of DNS Server

Figure: Confirmation of installation

The process would take a few seconds to be installed

Figure: Installation Process

Figure: Installation Results

4.3 CONFIGURATION OF DNS SERVER

Figure: DNS Server manager

Figure: Adding a New Zone.

6. Click on allow both unsecure and secure updates.

Figure: Confirmation of installation selections

Figure: Confirmation of new zone selections

8. Add all of the resource records

Figure: Resource Records

The records would be like as shown under.

Figure: Created Records

4.4 DNS COMMANDS

1. Open CMD MODE and run nslookup command

Figure: Running nslookup

2. ping the domain lkc.local

Figure: Pinging lkc.local

3. Type ipconfig /displaydns to check the DNS specifications.

Figure: DNS configurations

4.1 Dynamic Host Configuration Protocol (DHCP)

Why Is DHCP Important

4.2 Working of DHCP Server:

If Automatic private IP address is selected, the DHCP client auto-configures its IP

4.3 INSTALLATION OF DHCP SERVER

Figure: Role selection

Figure: introduction to DHCP server

3) Select the IP address and click Next.

Figure: Network Connection Bindings

Figure :IPv4 DNS server settings

Figure: WINS server settings

Figure: Adding a new scope

Figure: Adding or editing DHCP scopes