Professional Documents
Culture Documents
Nos Assignment
Nos Assignment
Nos Assignment
OF
NETWORK OPERATING
SYSTEM.
Benefits
Portability
No reconfiguration necessary – standard parameters are sent by the service to each PC
automatically
Ease of use – PCs and Macs do not have to be rebooted for the DHCP addressing to be in
effect
Simple to support – configuration for network administrators is standardized and flexible
to the needs of those using the service
Support for any operating system that supports DHCP, with client support focused on PC
and Mac
Capability, where required, to allocate reserved DHCP addresses for special needs
devices
ANS-- Distributed OS: They use multiple central processors to serve multiple real-time
applications and multiple users. Data processing jobs are distributed among the processors
accordingly.
The processors communicate with one another through various communication lines (such as
high-speed buses or telephone lines). These are referred as loosely coupled systems or distributed
systems. Processors in a distributed system may vary in size and function.
Eg- Plan 9 and Inferno
Cluster OS: A computer cluster is a single logical unit consisting of multiple computers that are
linked through a LAN. The networked computers essentially act as a single, much more powerful
machine. A computer cluster provides much faster processing speed, larger storage capacity,
better data integrity, superior reliability and wider availability of resources.
Computer clusters are, however, much more costly to implement and maintain. This result in
much higher running overhead compared to a single computer.
QUE-3. Explain client server architecture and difference b/w workgroup and
domain.
ANS-- Client/server architecture is a computing model in which the server hosts, delivers and
manages most of the resources and services to be consumed by the client. This type of
architecture has one or more client computers connected to a central server over a network or
internet connection. This system shares computing resources.
Client/server architecture is also known as a networking computing model or client/server
network because all the requests and services are delivered over a network.
Domain:
One or more computers are servers. Network administrators use servers to control the
security and permissions for all computers on the domain. This makes it easy to make
changes because the changes are automatically made to all computers.
If you have a user account on the domain, you can log on to any computer on the domain
without needing an account on that computer.
There can be hundreds or thousands of computers.
The computers can be on different local networks.
ASSIGNMENT NO-02
o Bus Topology: Bus topology is a network type in which every computer and network
device is connected to single cable. When it has exactly two endpoints, then it is called
Linear Bus topology
o Ring Topology: It is called ring topology because it forms a ring as each computer is
connected to another computer, with the last one connected to the first. Exactly two
neighbours for each device.
Features of Ring Topology
1. A number of repeaters are used for Ring topology with large number of nodes, because if
someone wants to send some data to the last node in the ring topology with 100 nodes,
then the data will have to pass through 99 nodes to reach the 100th node. Hence to
prevent data loss repeaters are used in the network.
2. The transmission is unidirectional, but it can be made bidirectional by having 2
connections between each Network Node, it is called Dual Ring Topology.
3. Data is transferred in a sequential manner that is bit by bit. Data transmitted, has to pass
through each node of the network, till the destination node.
o Star Topology: In this type of topology all the computers are connected to a single hub
through a cable. This hub is the central node and all others nodes are connected to the
central node.
ANS-- Active Directory Domain Services (AD DS) is a server role in Active Directory that
allows admins to manage and store information about resources from a network, as well as
application data, in a distributed database. AD DS can also help admins manage a network's
elements (computers and end users) and reorder them into a custom hierarchy.
Schema master.
RID master.
PDC emulator.
Infrastructure master.
ANS-- A forest is a security boundary. Objects in separate forests are not able to interact with
each other, unless the administrators of each separate forest create a trust between them. For
example, an Enterprise Administrator account for domain1.com, which is normally the most
privileged account of a forest, will have, no permissions at all in a second forest
named domain2.com, even if those forests exist within the same LAN, unless there is a trust in
place.
If you have multiple disjoint business units or have the need for separate security boundaries,
you need multiple forests.
A domain is a management boundary. Domains are part of a forest. The first domain in a forest is
known as the forest root domain. In many small and medium organizations (and even some large
ones), you will only find a single domain in a single forest. The forest root domain defines the
default namespace for the forest. For example, if the first domain in a new forest is
named domain1.com, then that is the forest root domain. If you have a business need for a child
domain, for example - a branch office in Chicago, you might name the child domain chi.
The FQDN of the child domain would be chi.domain1.com. You can see that the child domain's
name was prepended forest root domain's name. This is typically how it works. You can have
disjoint namespaces in the same forest, but that's a whole separate can of worms for a different
time.
In most cases, you'll want to try and do everything possible to have a single AD domain. It
simplifies management, and modern versions of AD make it very easy to delegate control based
on OU, which lessens the need for child domains.
ANS-- Active Directory objects represent the physical entities that make up a network. An object
is an instance of storage of a class. A class is defined in the Active Directory schema as a
specific set of mandatory and optional attributes — that is, an attribute can be present in an
object in Active Directory only when that attribute is permitted by the object's class. Classes also
contain rules that determine which classes of objects can be superior to (parents of) a particular
object of the class. Each attribute is also defined in the directory schema. The attribute
definitions determine the syntax for the values the attribute can have.
When you create an object in Active Directory, you provide values for the attributes of the object
in its particular class, and you do so according to the rules of the directory schema. For example,
when you create a user object, you provide alphanumeric values for the user's first and last
names, the logon identifier, and perhaps other values, such as telephone number and address.
You cannot create the user object successfully without providing acceptable values for the user
name and logon name because these attributes are mandatory, according to the directory schema.
Applications that create or modify objects in Active Directory use the directory schema to
determine what attributes the object must and might have, and what those attributes can look like
in terms of data structures and syntax constraints. For this reason, the directory schema is
maintained forest-wide so that all objects created in the directory conform to the same rules.
Objects are either container objects or leaf objects. A container object stores other objects, and,
as such, it occupies a specific level in a subtree hierarchy. An object class is a container if at least
one other class specifies it as a possible superior; thus, any object class defined in the schema can
become a container. A leaf object does not store other objects, and, as such, it occupies the
endpoint of a subtree.
Active Directory provides the flexibility in designing a business structure for an organization’s
current and future needs. Understanding Active Directory is key when designing your
organization’s Directory structure. In Active Directory all resources are organized in a logical
structure which enables any resource to be located by name rather than physical location.
In Active Directory there are different type of resources and objects that define the logical
structure:
Organizational Units
All these Active Directory components work together in defining your logical structure. By the
way, a Forest defines the logical boundary for one or more Trees, and a Tree defines the logical
boundary for one or more domains.
The physical structure of Active Directory consists of a database that is replicated to all domain
controllers in a Forest. The Data Store is what handles all access to the database and consists of
services and physical files that make the directory available. The storage architecture of Active
Directory has four different parts.
Another main aspect of Active Directory is Sites. Sites are used for communication between
domain controllers located in the same site, and we can use sites to optimize bandwidth between
domain controllers that are in different physical locations. All IP subnets that share the same
local area network are part of the same site.
ANS-- Active Directory uses DNS as its domain controller location mechanism and leverages the
namespace design of DNS in the design of Active Directory domain names. As a result, DNS is positioned
within the discoverability and logical structure components of Active Directory technology components.
Typically, a Windows Server 2003 DNS namespace is deployed to mirror an Active Directory
forest and domain infrastructure. In such a deployment, a partition of the DNS namespace is set
aside for Active Directory, where a DNS domain name such as corp.contoso.com is used support
the Active Directory forest root domain, and then subdomains of this name are created to suit
additional Active Directory domains as needed.
Active Directory is dependent on DNS as a domain controller location mechanism and uses DNS
domain naming conventions in the architecture of Active Directory domains. There are three
components in the dependency of Active Directory on DNS:
Component Description
Domain The Windows Server 2003 domain controller locator, implemented in the
controller Net Logon service, enables a client to locate a domain controller. The
locator (Locator) component contains the DNS–compatible and the Windows NT 4.0–
compatible locators that provide interoperability in a mixed Windows
Server 2003– and Windows NT 4.0–based environment.
Active Directory Every Windows Server 2003 Active Directory domain has a DNS domain
domain names in name (for example, contoso.com), and every Windows Server 2003–based
DNS computer has a DNS name (for example, win2kserver.contoso.com).
Architecturally, domains and computers are represented both as objects in
Active Directory and as nodes in DNS.
Because DNS domains and Active Directory domains share identical domain
names, it is easy to confuse their roles. The two namespaces, although
typically sharing an identical domain structure, store different data and,
therefore, manage different objects:
DNS stores zones and resource records, and Active Directory stores
domains and domain objects. Both systems use a database to resolve
names.
Active Directory When DNS data is stored in Active Directory, each DNS zone is an Active
DNS objects Directory container object (class dnsZone). The dnsZone object contains a
DNS node object (class dnsNode) for every unique name within that zone.
These unique names include the variations assigned to a specific host
computer when it functions, for example, as a primary domain controller or
as a global catalog server. The dnsNode object has a dnsRecord multivalue
attribute that contains a value for every resource record that is associated
with an object’s name.