Planning Server Deployments

1. Planning Server Deployments Lesson 1

2. Skills Matrix

3. Server Deployment • When planning a server deployment for a large enterprise network, the operating system edition you choose for your servers must be based on multiple factors, including the following: • The hardware in the computers. • The features and capabilities you require for your servers. • The price of the operating system software.

4. Windows Server 2008 Editions • Windows Server 2008 Web • Windows Server 2008 Standard • Windows Server 2008 Enterprise • Windows Server 2008 Datacenter

5. Windows Server 2008 Web • Designed specifically for computers functioning as Internet or intranet Web servers. • Includes all of the Internet Information Services 7 capabilities, but it cannot function as an Active Directory domain controller, and it lacks some of the other features found in the other editions as well. • The licensing terms for this product forbid you to run client/server applications that are not Web-based.

6. Windows Server 2008 Standard • The Standard edition includes nearly the full set of Windows Server 2008 features, lacking only some high-end components, such as server clustering and Active Directory Federation Services. • Standard edition is also limited to computers with up to 4 GB of RAM (in the x86 version) and up to four processors.

7. Windows Server 2008 Enterprise • The Enterprise edition includes the full set of Windows Server 2008 features, and supports computers with up to eight processors and up to 64 GB of RAM (in the x86 edition). • Enterprise also supports up to four virtual images with Hyper-V (in the 64-bit version) and an unlimited number of network connections.

8. Windows Server 2008 Datacenter • Designed for large and powerful servers with up to 64 processors and fault tolerance features such as hot add processor support. • This edition is available only from original equipment manufacturers (OEMs), bundled with a server.

9. Processor Support • Each of the editions support x86 and x64 processors. • There is also a Window Server 2008 for Itanium-Based Systems and Windows HPC Server 2008.

10. Server Core • Windows Server 2008 includes an installation option that gives a stripped-down version of the operating system. • There is no Start menu, no desktop Explorer shell, no Microsoft Management Console, and virtually no graphical applications. • All you see when you start the computer is a single window with a command prompt.

11. Server Core • To work with a Server Core computer, you must rely primarily on: • The extensive collection of command prompt tools Microsoft includes with Windows Server 2008. • Use MMC consoles on another system to connect to the server.

12. Microsoft Assessment and Planning Solution Accelerator (MAP) • Deploying Windows Server 2008 on a large network can often mean evaluating a large number of existing servers, to determine whether they have the appropriate hardware for the operating system. • Microsoft Assessment and Planning Solution Accelerator (MAP) is a new tool that adds to the capabilities of its predecessor, Windows Vista Hardware Assessment Solution Accelerator, so that you can evaluate the hardware on servers as well as workstations.

13. Microsoft Assessment and Planning Solution Accelerator (MAP) • MAP is essentially a database application based on Microsoft SQL Server 2005 Express, a scaled-down, free version of SQL Server 2005. • MAP can run on the 32-bit version of the following operating systems: • Windows Vista • Windows XP Professional with Service Pack 2 • Windows Server 2003 R2

14. Microsoft Assessment and Planning Solution Accelerator (MAP)

15. The Microsoft Assessment and Planning Solution Accelerator Setup Wizard

16. The Microsoft Assessment and Planning Solution Accelerator Console

17. The Create or Select a Database To Use Dialog box

18. The Select Reports and Proposals Page

19. The Choose Computer Discovery Methods Page

20. The Specify Active Directory Options Page

21. The Use the Windows Networking Protocols Page

22. The Import Computer Names From a File Page

23. The Scan an IP Address Range Page

24. The Inventory Account Dialog Box

25. The Assessment Wizard Status Window

26. The MAP Console

27. The WS2008 Proposal File

28. The WS2008 Hardware Assessment File

29. The WS2008 Role Assessment File

30. Windows Deployment Server • Microsoft provides a variety of tools that enable network administrators to deploy the Windows operating systems automatically, using file-based images. • Windows Deployment Services (WDS) enables you to perform unattended installations of Windows Server 2008 and other operating systems on remote computers, using network-based boot and installation media.

31. Windows Deployment Server • The client computer must have a network adapter that supports a preboot execution environment (PXE). • In a PXE, the computer, instead of booting from a local drive, connects to a server on the network and downloads the boot files it needs to run. • In the case of a WDS installation, the client downloads a boot image file that loads Windows PE (Preinstallation Environment) 2.1, after which it installs the operating system by using another image file.

32. Installing Windows Deployment Services • To use WDS, you must install the Windows Deployment Services role, configure the service, and add the images you want to deploy. • WDS is a standard role that you can install from the Initial Configuration Tasks window or the Server Manager console. • The Windows Deployment Services role includes the following two role services: • Deployment Server • Transport Server

33. Windows Deployment Services Prerequisites • Windows Deployment Services role, but the role has several other prerequisites, as follows: • Active Directory — The Windows Deployment Services computer must be a member of, or a domain controller for, an Active Directory domain. • Dynamic Host Configuration Protocol (DHCP) — The network must have an operational DHCP server that is accessible by the WDS clients. • Domain Name Service (DNS) — A DNS server must be on the network for the WDS server to function. • NTFS — The WDS server must have an NTFS drive to store the image files.

34. The Windows Deployment Services Console

35. The Remote Installation Folder Location Page

36. The DHCP Option 60 Page

37. The PXE Server Initial Settings Page

38. The Configuration Complete Page

39. Image Files • Windows Deployment Services requires two types of image files to perform remote client installations: • Boot image • Install image

40. Boot Image • A boot image contains the files needed to boot the computer and initiate an operating system installation. • The Windows Server 2008 installation DVD includes a boot image file called boot.wim, located in the \Sources folder, which loads Windows PE 2.1 on the client computer. • You can use this boot image file for virtually any operating system deployment without modification.

41. Install Image • Contains the operating system that WDS will install on the client computer. • Windows Server 2008 includes a file named install.wim in the \Sources folder on the installation DVD. • This file contains install images for different operating system editions. • You can apply these images to a new computer to perform a standard Windows Server 2008 setup, just as if you had used the DVD to perform a manual installation.

42. The Image File Page

43. The Image Metadata Page

44. The Image Group Page

45. The List of Available Images Page

46. Custom DHCP Option • When you are using another computer as your DHCP server, you should clear the Do Not Listen on Port 67 and Configure DHCP Option 60 to ‘PXEClient’ checkboxes on the DHCP Option 60 page of the Windows Deployment Services Configuration Wizard. • When you are using an external DHCP server, you must also configure it manually to include the custom option that provides WDS clients with the name of the WDS server.

47. The DHCP Console

48. The Predefined Options and Values Dialog Box

49. The Option Type Dialog Box

50. The Server Options Dialog Box