Class Notes (1,100,000)
CA (630,000)
Ryerson (30,000)
ITM (1,000)
ITM 315 (20)
Lecture 2

ITM 315 Lecture Notes - Lecture 2: Service Pack, Shared Resource, Active Directory


Department
Information Technology Management
Course Code
ITM 315
Professor
Farid Shirazi
Lecture
2

This preview shows page 1. to view the full 5 pages of the document.
Chapter 2
Planning a Windows Server 2012/R2 Installation
Some networks require more planning than others
Smaller networks will most likely only require a few decisions before installation can
begin
Larger networks will require more planning to ensure a productive integration of the new
server
Network environment and the roles a server will play on the network are key
considerations in planning Windows Server 2012/R2 installations
32-bit versus 64-bit processors: Microsoft no longer makes a 32-bit version of its server
OS
Virtualization extensions: CPU needs to support this if you want to run Hyper-V
Disk subsystem: do research on current drive technology and your network’s needs
beforehand
Hot-add/hot-replace features; ability to add memory or CPU without shutting down the
system
Other things to consider:
Name of the server
Must be unique and include some description, like location or primary purpose
Network protocols
Windows installs both TCP/IPv4 and TCP/IPv6 by default in Windows Server 2012/R2
If you need support for older protocols, such as IPX/SPX, you need to find a third party
solution
IP Address
Windows Server 2012/R2 uses automatic IP addressing, but a server should have a static
IP address
Other things to consider (cont’d):
Time zone
Important for user authentication
Workgroup or domain
Workgroup is more suitable for smaller environments, domain provides more advantages
Server roles
find more resources at oneclass.com
find more resources at oneclass.com
You're Reading a Preview

Unlock to view full version

Only page 1 are available for preview. Some parts have been intentionally blurred.

Will determine how the server is used and what network services will be available to
users
Performing a Clean Installation
Clean installation - one in which the OS is installed on a new disk partition and isn’t an
upgrade from a previous version of Windows
The upgrade option is available only if a supported version of Windows is already
installed
A custom installation performs a clean install of Windows
Patches
Fixes to bugs and security vulnerabilities
Can be installed through Windows Update
Windows Update downloads and installs new drivers and service packs
Service pack
Collection of all bug fixes and security updates
May also add features and performance enhancements or change the functionality of
existing features
When adding a new server, you must decide whether the server will be one of the
following:
A domain controller (DC) in the existing domain
Adding a second domain controller can reduce server load and provide fault tolerance
A read only domain controller (RODC) in the existing domain
Can provide benefits similar to a DC’s, but is more suited for branch offices
A member server in the existing domain
Falls under domain management but doesn’t run Active Directory
A stand-alone server
Doesn’t fall under domain management, but is part of a workgroup
Reasons to add servers to a network:
Need for Fault tolerance
Loss of access to server resources = reduction in productivity and increase in costs
Fault tolerance is built into several Windows server roles, such as AD DS, DNS, and file
sharing with Distributed File System (DFS)
Upgrading to Windows Server 2012/R2
find more resources at oneclass.com
find more resources at oneclass.com
You're Reading a Preview

Unlock to view full version