Windows Deployment Services

Windows Deployment Services enables you to deploy Windows operating systems. You can use it to set up new computers by using a network-based installation. This means that you do not have to install each operating system directly from a CD or DVD.


WDS features includes:

• Ability to deploy Windows Win7 and Windows Server 2008. 
• Windows PE is the boot operating system.
• Image-based installation, using Windows image (.wim) files.
• An extensible and higher-performing PXE server component.
• A new boot menu format for selecting boot operating systems.
• A new graphical user interface on the client computer that you use to select images.
• The Windows Deployment Services Microsoft Management Console (MMC) snap-in and the WDSUTIL command-line tool, which enable you to configure and manage Windows Deployment Services.

The Requirement of WDS

1. Active Directory
2. DHCP
3. DNS
4. Credentials
5. Windows Server 2003 SP1 or Later

Windows Automated Installation Kit

The Windows Automated Installation Kit (Windows AIK) is a set of tools and documentation that support the configuration and deployment of Windows® operating systems. By using Windows AIK, you can automate Windows installations, capture Windows images with ImageX, configure and modify images using Deployment Imaging Servicing and Management (DISM), create Windows PE images, and migrate user profiles and data with the User State Migration Tool (USMT). Windows AIK also includes the Volume Activation Management Tool (VAMT), which enables IT professionals to automate and centrally manage the volume activation process using a Multiple Activation Key (MAK).

70-646 考試題目 2

Q 1.

Your network contains a single Active Directory site. You have a server named Server1 that runs Windows Server 2008. Server1 is a DHCP server for the network.

You need to plan the automated deployment of operating systems. Your plan must meet the following requirements:

Support Windows Vista deployments

Support Windows Server 2008 deployments

Support computers that start from a Pre-boot Execution Environment (PXE) network adapter

Minimize the number of servers installed

What should you include in your plan?

A. Deploy Windows Automated Installation Kit (WAIK) on Server1.

B. Deploy Windows Automated Installation Kit (WAIK) on a new server.

C. Deploy the Windows Deployment Services (WDS) server role on Server1.

D. Deploy the Windows Deployment Services (WDS) server role on a new server.

Volume Activation Models

Volume Activation Models

Volume Activation allows volume license customers to automate the activation process so that it is transparent to users. Volume Activation applies to computers that are covered under a Volume Licensing program. It is used strictly as a tool for activation, and it is not tied to license invoicing or billing.

Volume Activation provides two models for completing volume activations: Key Management Service (KMS) and Multiple Activation Key (MAK). KMS allows organizations to activate systems within their network, and MAK activates systems on a one-time basis by using the hosted activation services provided by Microsoft. Customers can use either or both key types to activate systems in their environments.

Failover Cluster And Network Load Balancing

Failover Cluster

A failover cluster is a group of independent servers that are running Windows Server 2008 and working together to increase the availability of services and applications. When a failure occurs on one computer in a cluster, resources are redirected and the workload is redistributed to another computer in the cluster. You can use failover clusters to ensure that users have nearly constant access to important server-based resources.

Hardware and software considerations for failover clusters

Network Load Balancing

Network Load Balancing provides scalability and high availability to enterprise-wide TCP/IP services, such as Web, Terminal Services, proxy, Virtual Private Networking (VPN), and streaming media services. Network Load Balancing brings special value to enterprises deploying TCP/IP services, such as e-commerce applications, that link clients with transaction applications and back-end databases.

Choosing cluster technology in different usage:

Failover clusters are designed for applications that have long-running in-memory state, or that have large, frequently updated data states. These are called stateful applications, and they include database applications and messaging applications. Typical uses for failover clusters include file servers, print servers, database servers, and messaging servers. 

Network Load Balancing is intended for applications that do not have long-running in-memory state. These are called stateless applications. A stateless application treats each client request as an independent operation, and therefore it can load-balance each request independently. Stateless applications often have read-only data or data that changes infrequently. Front-end Web servers, virtual private networks (VPNs), File Transfer Protocol (FTP) servers, and firewall and proxy servers typically use Network Load Balancing. Network Load Balancing clusters can also support other TCP- or UDP-based services and applications