Net OS. Chapter 2 PDF

Chapter 2 PAGE 3 How can we plan for a Windows Server 2012/R2 Installation? - Smaller networks will require a few decisions before installation. - Larger networks require more planning to ensure a productive integration of the new server. PAGE 4 - 7 What should be considered when Installing t...

Chapter 2 PAGE 3 How can we plan for a Windows Server 2012/R2 Installation? - Smaller networks will require a few decisions before installation. - Larger networks require more planning to ensure a productive integration of the new server. PAGE 4 - 7 What should be considered when Installing the First Server in a New Network? Hardware considerations: - CPU architecture: AMD or Intel? - Workstation or Server processors: servers support up to 64 physical CPUs. - Total number of physical processors - 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 (FAT, NTFS etc.) - 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. - IP Address: Windows Server 2012/R2 uses automatic IP addressing, but a server should have a static IP address. - Time zone: Important for user authentication. - Workgroup or domain: Workgroup is more suitable for smaller environments, domain provides more advantages. - Server roles: Will determine how the server is used and what network services will be available to users PAGE 8 & 11 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. Usually use a DVD: Make sure the BIOS is set to boot from the CD/DVD drive first if you have an OS already installed. Windows begins the installation: Your computer typically restarts twice. After the installation is finished: You will be prompted to set the Administrator password. Password must contain a minimum of three characters that include three of the following types: ○ Uppercase & lowercase letters, numerals, and special symbols, such as @,/,# When prompted, log on to open Server Manager. PAGE 9 PAGE 10 The initial installation window for Windows Server 2012 R2: Choosing the edition and installation type: PAGE 12 Post Installation Tasks (After installation): Activate Windows Server 2012 R2 ○ Activation should take place automatically, but if it doesn’t, it must be done within 10 days after installation. Set the correct date, time, and time zone Assign a static IP address Assign a computer name Configure automatic updates Download and install available updates PAGE 13 - 14 Installing Updates: 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 Accessing Windows Update settings: PAGE 15 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 domain controller is a server that responds to authentication requests and verifies users on computer networks. - 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. PAGE 16 - 17 What are the reasons for us to expand our networks or add servers to a network? - Company growth: Ideal to plan for growth before the server is overloaded. - Excessive load on existing servers: Performance will gradually degrade on servers. - Need to isolate an application: Adding new applications to an unused machine reduces the workload of servers providing critical services. - 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) - Addition of branch office: Placing a server in a branch office can reduce WAN traffic created by authentication and authorization on a domain controller, DNS lookups, DHCP address assignment, access to shared files, etc. PAGE 18 In what situations is a server core suitable? - Acting as a secondary DC to provide redundancy for Active Directory. - As a branch office server when remote administration is likely. - As an RODC server role for a branch office server. - As a virtual machine to reduce the amount of resources used. - As a specialized single role server providing services such as DNS, DHCP, Web, or File Services. - As a departmental server. PAGE 19 When should we not use server core? - When it’s the first server in a network. - When you need to install server roles and features that Server Core doesn’t support. - When the server administrator isn’t well versed in using command-line programs or remote administration tools. - When you cannot live without a Windows GUI running on your server. PAGE 20 - 21 Summary - The process of installing Windows Server 2012/R2: is fairly straightforward with most of the work taking place in the planning phase. - Installing from a DVD is common for a: single-server installation. - Post Installation configuration tasks include: giving the server a name, configuring network protocols, setting time zone information, selecting a network model, and installing and configuring Windows Updates. - Server roles can then be installed - When adding new servers to an existing network, you must decide: whether the new server will be a new domain controller in the existing domain, a read-only domain controller, a member server, or a stand-alone server. - You can do an in-place upgrade to Windows Server 2012/R2 only if the existing OS is Windows Server 2008 or Windows Server 2008 R2. - Windows Server Core: is the default and recommended installation option. - Feature on Demand: is a new feature in Windows 2012/R2 that enables you to remove Windows feature installation files from the local disk.