Server installation

Introduction
 A server is a computer that is meant to be a dedicated
service provider
 a client is a computer that requests services.
 A network that is made up of dedicated servers and clients
is known as a client/server network.
 A server-based network is the best network for sharing
resources and data, while providing centralized network
security for those resources and data
 When you are determining hardware and software needs,
Look at the role the computer needs to fill and the load the
Computer will be placed under (RAM,CPU,HDD) and
growth
Slide
#2
 Introduction …
Windows Server is Microsoft’s Unix server OS
server OS Has gone through a
Has gone through a number of number of editions
editions – Windows Server 2003
– Windows Server 2003 – Windows Server 2003 R2
– Windows Server 2003 R2 – Windows Server 2008
– Windows Server 2008 – Windows Server 2008 R2
– Windows Server 2008 R2 – Windows Server 2012
– Windows Server 2012 – Windows Server 2012 R2
– Windows Server 2012 R2 – Windows Server 2016
(current)
– Windows Server 2016 (current)
Installation steps
Planning;
 Gathering system hardware information;
 Deciding the installation type
Backing up your old system (optional, but strongly
recommended);
Booting a OS kernel from CD, HDD or network;
Running related software through scripts;
Installing the kernel on hard disk;
Choosing and installing software packages;
Making final configuration adjustments; and
Rebooting into a running system.
Identify Requirements for installation
Server software edition selection
Product line: Servers OS are available in various editions
Server edition is dependent on the business requirement
Hardware requirement
Reliability / fault tolerant
Future expansion/ Slots for scale up
Performance/ Capacity
 Processor
 Memory
 Disk space
 Other / Network interface

Version of OS for 32/64 bits

Win server 2008

 Installation process & Type
Installation process for Windows Server is very easy and more user
friendly than in earlier editions
 Boot from installation CD and follow GUI wizard
using answer files created with Windows System Image Manager (SIM)
and
automating deployment using the Windows Automated Installation Kit
(WAIK).
Following choices are involved
– Full Installation (GUI) vs Server Core Installation (reduced
footprint and mainly command line)
– Upgrade (if other OS exists in the machine) vs Custom (e.g. when
installing from scratch)
– In case of Custom installation, allows re-defining partitions and
selecting the partition where to install Windows Server
When complete, server will be automatically rebooted
Full Installation
Core installation

Only the module containing the required role is installed

GUI is not installed
Disk space utilization is minimal
use the command-line or remote-management tools
does not support upgrading from previous versions
installs only the subset of the binary files that are
required by the supported server roles
Used environment that require
High security and minimal surface attack
Perform dedicated task
Benefits of a Server Core Installation
Key
Server Core installations provide the following
benefits:
it can improve security
it reduce management
• Reduced maintenance
• Reduced attack surface
• Less disk space required
Server roles supported in core installation
Server Core installations provide an environment for
running the following server roles:
• Active Directory Domain Services (AD DS)
• Active Directory Lightweight Directory Services (AD LDS)
• Dynamic Host Configuration Protocol (DHCP) Server
• Domain Name System (DNS) Server
• File Services
• Print Server
• Streaming Media Services
Features that a Server Core Installation
Supports
The Server Core installation of Windows Server 2008
supports the following optional features:
• Backup
• Bitlocker Drive Encryption
• Failover Clustering
• Multipath input/output (I/O)
• Network Load Balancing
• Removable Storage
• Simple Network Management Protocol (SNMP)
• Subsystem for UNIX-based applications
• Telnet client
• Windows Internet Name Service (WINS)
Installation scenarios
Clean installation
Upgrade
Back up your servers before you upgrade
 all data and configuration information that is necessary
 be sure to include the boot and system partitions, and the system
state data
Unattended installation
using answer files, Windows SIM, and the Windows
AIK.
Preparing for the Installation of Windows
Server
Managing server role & Feature
After the installation is complete
and the administrator logs on
to the server, and use among the 4 methods
1. he Initial Configuration Tasks window opens and allows the administrator
to setup
the server name, networking configuration, automatic updates and the Windows,
Firewall settings.
After using this tool, the administrator can choose to use
custom
2. Microsoft Management Consoles (MMCs) to manage the
server,
3. use Server Manager to install and remove roles and features,
and
4. use Windows PowerShell for configuration tasks, if desired.
What Are Server Roles?

eg
Active directory domain service
web server
Server adminstration tool is used to add and remove role.
 What Are Server Features?

Failover Clustering is a feature

Tools
Managing a Server Installation
Key
Locally and remotely using command prompt and
scripting technique
Remotely using terminal server
Alternatively using Microsoft Management Console
(MMC) snap-ins from another computer running
Windows remote shell
And locally using the GUI in full installation option
Installation type
Stand alone machine
Virtual Machine (VM)
Virtual Machine
is technology and technique that is abstracting the computer’s
physical hardware and creating multiple virtualized hardware
environments, called VMs
Each VM has its own (virtual) hardware configuration and can run a
separate copy of an operating system (OS).
with sufficient physical hardware and the correct licensing,
Multiple OS can be installed and run installed can support multiple VMs,
which administrators can manage as if they were standalone computers.
Virtualization software dynamically allocates the “host” CPU,
memory, and I/O resources, among several “guest” operating
systems while resolving conflicts
From the user’s point of view, a virtual machine behaves like a full-
fledged physical server
A hypervisor (or, virtual machine monitor) is a
software layer that mediates between virtual machines
(VMs) and the underlying hardware.
Responsible for sharing system resources among guest
VMs
 Guest OS’s are independent, so they don’t need to be the
same (e.g. CentOS can run alongside Windows)
Vmware ESX, XenServer, bhyve,Oracle virtualBox are
examples of hypervisors
Virtualization architectures
Type II virtualization
requires a standard OS installed on a compute
install the virtualization product on top of the host
for each VM
 Memory allocated
 Virtual disk allocated
 Perpheral will be created
 Guest OS will be installed

it is not generally recommended for high-traffic servers in production

environments
eg Microsoft Windows Virtual PC and Microsoft Virtual Server
,bhyve, Oracle VirtualBox, and VMware Workstation
 Type I virtualization
 A type 1 hypervisor runs directly on the hardware without a supporting OS
 Also called “bare-metal” or native hypervisor
 hypervisor is an abstraction layer that interacts directly with the computer’s physical
hardware
 No host OS
 Hypervisor is responsibility for allocating a computer’s processor clock cycles
 The hypervisor creates individual environments called partitions,
 Creates one parent and more than one child
 parent partition helps to
 Access Hardware resurce
 Used to run the virtualization stack
 Responsible for the subsystem that directly affect performance of the physicla
HW
 each of which has its own OS installed and accesses the computer’s hardware via
the hypervisor
 eg Hyper V Widow server 2012 R2 standard data center
VMware ESXi and XenServer
Exercise
List and explain about the different types of
virtualization?
Explain the difference between containerization and
virtualization?
2.2 Booting & startup
Booting
The process by which a computer is turned on and the
operating system starts functioning
The standard term for “starting up a computer”,
shortened form of the term “bootstrapping”
Operating system’s normal facilities are not available during
booting
Tasks during the boot process:
– Finding, loading and running bootstrapping code
– Finding, loading and running the OS kernel
– Running startup scripts and system daemons
– Maintaining process hygiene and managing system state
transitions
Startup procedures have changed a lot recently
– UEFI replacing BIOS
– systemd replacing the traditional UNIX init
– systems migrating to the cloud, virtualization and containerization
o no need for admins to touch hardware
o instead, we have image management, APIs, and control
panels
During booting, the kernel is loaded into memory and
begins to execute
A variety of initialization tasks are performed, and the
system is then made available to users
Boot process Overview
The basic boot process are
1. The system BIOS checks the system and launches the first stage boot
loader on the MBR of the primary hard disk.
2. The first stage boot loader loads itself into memory and launches the
second stage boot loader from the /boot/ partition.
3. The second stage boot loader loads the kernel into memory, which in
turn loads
4. any necessary modules and mounts the root partition read-only.
5. The kernel transfers control of the boot process to the /sbin/init program.
6. The /sbin/init program loads all services and user-space tools, and
mounts all partitions listed in /etc/fstab.
7. The user is presented with a login screen for the freshly booted Linux
system
Boot process overview
 Understanding the Startup Process

The normal startup sequence for

Windows 7 is:
Power-on self test (POST) phase.
Initial startup phase.
Windows Boot Manager phase.
Windows Boot Loader phase.
Kernel loading phase.
Logon phase
vary if the computer is resuming
 from hibernation or
 a non-Windows 7 option I
s selected during the Windows Boot
Manager phase
Start up instruction
Power-on Self Test Phase
The first startup instruction
processor execute instruction in the BIOS or EFI/UEFI
Firmware containing processor dependant code
Responsible:
 Hardware check such memory
 Verifies presence of devices required to start the OS such sa HDD
 Retrieve system configuration form Non-volatile memory
 eg boot order Hardware setting, pnp device
Ad-ons adapter with firmware
 carried out internal diagnostic test
 Video adapter, HDD controller starts diagnostic test

Startup failure due to Hardware failure

BIOS/EFI display error code indicating the problem/ beep
Initial startup phase
Load Windows Boot Manager
The computer load based on the boot order
CD/DVDFloppyHDD
startup fails during the initial startup phase may be due to:
a problem with the BIOS configuration,
the disk subsystem,
the file system.
Boot form Hard disk
Reads boot code instruction from MBR
MBR is first sector of data on the startup disk
MBR contain boot code & partition table /primary and extended
 Active partition /bootable loade the code to perform
 Read contain of file system
 Locate and load bootmgr( 16 bit instruction) & load 32-64 Boot manager
Initial Startup Phase for EFI Computers

Unlike BIOS , EFI computers have a built-in boot

manager
Enable the hardware to choose from multiple OS
Windows Boot Manager Phase

Read & load the supported file system

Enable to choose among multiple OS
Enable to start window memory diagnostics
Starts window boot loader then the OS
Windows Boot Manager default behavior can be interrupted to
view Advanced Boot Options.
Windows Boot Loader to open Windows
Windows Boot Manager starts Ntldr proceed HW detection if
earlier version of OS is selected.
control is passed to the boot sector for the other operating system
if other OS is selected.
Windows Boot Manager starts the diagnostic tool
Windows Boot Loader Phase

Loads the operating system kernel, Ntoskrnl.exe

Loads the Hardware Abstraction Layer (HAL), Hal.dll
Loads the system registry hive (System32\Config\System) into
memory.
Scans the HKEY_LOCAL_MACHINE\SYSTEM\Services key
for device drivers and loads all drivers that are configured for
the boot class into memory.
It does not, however, initiate the drivers.
Drivers are not initiated until the kernel loading phase.
Enables paging.
Passes control to the operating system kernel, which starts the
next phase
Kernel Loading Phase

Windows Boot Loader is responsible for loading

 the Windows kernel (Ntoskrnl.exe) and
the HAL into memory
initialize a group of software features that are called
the Windows executive.
Windows executive processes the configuration
information stored in the registry
 HKLM\SYSTEM\CurrentControlSet and starts services
and driver
Kernel Loading Phase
Control Sets
startup
kernel has been loaded, it has initialised its data structures and
found all the hardware devices.
a process can be created is by an existing process performing a fork
operation.
init is the process that is the ultimate ancestor of all user processes
on a UNIX system.
It always has a Process ID (PID) of 1. init is started by the operating
system kernel so it is the only process that doesn’t have a process as
a parent.
 init is responsible for starting all other services provided by the
UNIX system.
The services it starts are specified by init’s configuration file,
/etc/inittab.
Run level
init is also responsible for placing the computer into
one of a number of run levels.
init run level system provides a standard process for
controlling which programs init launches or halts when
initializing a run level
The init process is the grandfather of all processes
init are located in the /etc/rc.d/ directory
given run level determine which services are halted
and started by init.
0 — Halt : shut down eveything/system
 1 — Single-user text mode : halts any network services
2 — Not used (user-definable)
3 — Full multi-user text mode : Use network services
4 — Not used (user-definable)
5 — Full multi-user graphical mode (with an X-based login
screen)
6 — Reboot

The default runlevel for the system is listed in /etc/inittab

init n ( telinit n) as a root can be used to change the run level
Shutdown command is used to poweroff the system.
The command is available in /sbin
Shutdown –h : after shutdown it halts the machine
Shutdown –r : -r option reboots