Tech Lover 9

     The Windows Deployment Services role in Windows Server 2008 is the updated and redesigned version of Remote Installation Services (RIS). Windows Deployment Services enables you to deploy Windows operating systems Windows Server 2008. You can use it to set up new computers by using a network-based installation. This means that you do not have to be physically present at each computer and you do not have to install each operating system directly from a CD or DVD. The components of Windows Deployment Services are organized into the following three categories:
⦁    Server components     These components include a Pre-Boot Execution Environment (PXE) server and Trivial File Transfer Protocol (TFTP) server for network booting a client to load and install an operating system. Also included is a shared folder and image repository that contains boot images, install images, and files that you need specifically for network booting.
⦁    Client components     These components include a graphical user interface that runs within the Windows Pre-Installation Environment (Windows PE). When a user selects an operating system image, the client components communicate with the server components to install the image.
⦁    Management components     These components are a set of tools that you use to manage the server, operating system images, and client computer accounts.

     Windows Deployment Services for Windows Server　2008 includes several modifications to RIS features. There are also modifications from Windows Deployment Services that you can install onto computers running Windows Server　2003.

     Windows Deployment Services provides the following installation and deployment advantages-

* Reduces the complexity of deployments and the costs associated with inefficient manual installation processes.

* Allows network-based installation of Windows operating systems, including Windows Vista and Windows Server　2008.

* Deploys Windows images to computers without operating systems.

* Supports mixed environments that include Windows Vista, Windows Server　2008, Microsoft Windows　XP, and Microsoft Windows Server　2003.

* Provides an end-to-end solution for the deployment of Windows operating systems to client computers and servers.

* Uses standard Windows Server　2008 setup technologies.

　

　

　

Installing Windows Deployment Services

Deployment Server

Transport Server

* AD DS. A Windows Deployment Services server must be either a member of an AD DS domain or a domain controller for an AD DS domain. The AD DS domain and forest versions are irrelevant; all domain and forest configurations support Windows Deployment Services. * DHCP. You must have a working DHCP server with an active scope on the network because Windows Deployment Services uses PXE, which relies on DHCP for IP addressing. * DNS. You must have a working DNS server on the network before you can run Windows Deployment Services. * NTFS volume. The server running Windows Deployment Services requires an NTFS file system volume for the image store. * Credentials. To install the role, you must be a member of the Local Administrators group on the server. To initialize the server, you must be a member of the Domain Users group. For more information about this, see the Required .

* Credentials. To install the role service, you must be a member of the Local Administrators group on the server

  You can install Windows Deployment Services by using the Initial Configuration Wizard, Server Manager.
⦁    To install the role by using the Initial Configuration Wizard, click Add roles on the Initial Configuration Tasks startup screen.     
⦁    To install the role by using Server Manager, click Add roles, which is located in the Roles Summary pane.
⦁    Click Next and then select Windows Deployment Services.
⦁    Now install the window deployment services.

    During the installation, you have the following two role services to choose
⦁    Transport Server     To install this option, clear the Deployment Server check box on the second installation wizard screen. You can use Transport Server to create multicast namespaces that transmit data (including operating system images) from a standalone server.
⦁    Deployment Server     To install this option, ensure that both Deployment Server and Transport Server are selected on the second installation wizard screen. This option provides the full functionality of Windows Deployment Services. Which you can use to configure and remotely install Windows operating systems.

   After you install the server role, you must configure Windows Deployment Services by using the Windows Deployment Services MMC snap-in or by using WDSUTIL at the command prompt.
To configure the server role, use the following procedure.
⦁    Ensure that you are a Domain Administrator.
⦁    Click Start, click Administrative Tools, click Windows Deployment Services.
⦁    In the left pane of the Windows Deployment Services MMC snap-in, expand the list of servers.
⦁    Right-click the server, and then click Configure Server.
⦁    Follow the instructions in the wizard.
⦁    When the configuration is completed clear the Add images to Windows Deployment Services now check box and then click Finish.

   At least one boot image and one install image before you will be able to boot to the Windows Deployment Services server and install an image.
⦁         Boot images     Boot images are images that you boot a client computer into to perform an operating system installation. you can use the Boot.wim file from the Windows Server 2008 installation DVD (in the \Sources folder). The Boot.wim file contains Windows PE and the Windows Deployment Services client.
⦁    Install images     Install images are the operating system images that you deploy to the client computer. You can also use the Install.wim file from the installation DVD.
    To add the default images, use the following procedures. After you have a boot image and an install image on the server, you can perform a PXE boot on a client computer to install an operating system.
    To add the default boot image
⦁    In the left pane of the Windows Deployment Services MMC snap-in, right-click the Boot Images node, and then click Add Boot Image.
⦁    Browse to choose the default boot image (Boot.wim) on the Windows Server 2008 DVD, located in the \Sources folder.
⦁    Click Open and then click Next.
⦁    Follow the instructions in the wizard to add the image.

   The following procedures explain how to add more boot images to the boot menu.

To add an additional boot image by using the Windows interface:
⦁    Open the Windows Deployment Services MMC snap-in.
⦁    Right-click the Boot Images node, and then click Add Boot Image.
⦁    Click Browse to locate the boot image that you want to add. The boot image must be located on the server, and it can be the same or a different architecture.
⦁     Follow the instructions in the wizard to add the boot image.
⦁     When you have completed this procedure and you perform a PXE boot on a client computer, a boot menu will appear that shows both images (if both apply to that computer).


To add the default install image
⦁    In the Windows Deployment Services MMC snap-in, right-click the Install Images node,and then click Add Install Image.
⦁    Specify a name for the image group, and then click Next.
⦁    Browse to select the default install image (Install.wim) Windows Server 2008 DVD, located in the \Sources folder, and then click Open.
⦁    To add a subset of the images included in the Install.wim file, clear the check boxes for the images that you do not want to add to the server. You should add only the images for which you have licenses.
⦁    Follow the instructions in the wizard to add the images.
⦁    Now that you have a boot image and an install image on the server, you can perform a PXE boot on a client computer to install an operating system.

   Multicast transmissions enable you to deploy an image to a large number of client computers without overburdening the network.
Steps for creating a multicast transmission
    (a)    Using the Windows interface:
    To enable multicasting for an image, you must create a multicast transmission     for it.
⦁    Right-click the Multicast Transmission node, and then click Create Multicast Transmission.
⦁    Right-click an image, and then click Create Multicast Transmission.
    (b)    Multicast types.    There are two types of multicast transmissions:
⦁    Auto-Cast.
⦁    Scheduled-Cast.

    After a transmission has been created, you can perform any of the following actions:
⦁    Start the transmission  right-click the transmission and then click Start.
⦁    Delete the transmission. If you right-click the transmission and click Delete. Deactivate the transmission. If you right-click and then click Deactivate.
⦁    View the transmission's properties. To view the properties, right-click the transmission and then click Properties.
⦁    Refresh the transmissions and data. To do this, right-click a transmission and then click Refresh.
⦁    Configuring clients in a transmission
⦁    After you have created the transmission, client computers can join it by selecting the image in the Windows Deployment Services user interface.
⦁    View clients and see progress. To view any connected clients, expand the Multicast Transmissions node, and click the image. The connected clients are shown in the right pane. 
⦁    Stop a client installation. Right-click a client and then click Disconnect.
⦁    Disconnect a client from a multicast transmission. Right-click the client, and then click Bypass multicast.

 The TFTP download phase is when the boot image is downloaded to the client computer. Performance in this phase is tied directly to the following factors (in order of importance):
⦁    Latency between the client computer and the server
⦁    Size of the boot image.
⦁    TFTP block size.
⦁    TFTP window size.
⦁    Other network conditions.

 The simplest way to diagnose long download times  is to look at the average response time between the client and the server. To do this, in Windows PE, open the Command Prompt window, run ping <server’s IP address>, and then note the average latency.
The output will look similar to the following, where the average latency is less than 1 millisecond (which is good):
C:\Windows\system32>ping 10.197.160.93
Pinging 10.197.160.93 with 32 bytes of data:
Reply from 10.197.160.93: bytes=32 time=2ms TTL=60
Reply from 10.197.160.93: bytes=32 time<1ms TTL=60
Reply from 10.197.160.93: bytes=32 time<1ms TTL=60
Reply from 10.197.160.93: bytes=32 time<1ms TTL=60
Ping statistics for 10.197.160.93:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 2ms, Average = 0ms

High round-trip times indicate latency on the network, which is an indicator that TFTP download performance will be poor. To improve this performance, consider doing one or more of the following:
⦁    Use a Windows Deployment Services server that is closer to each client.
⦁    Remove stress and load from the network segment.
⦁    If the client connects to the server after multiple network hops, use the output from the tracert command to identify the latent segment, and consider rerouting TFTP traffic to avoid the hop.

 Windows Deployment Services uses the following protocols for installing images -
⦁    Dynamic Host Configuration Protocol (DHCP)
⦁    Pre-Boot Execution Environment (PXE)
⦁    Trivial File Transfer Protocol (TFTP)
⦁    Remote procedure call (RPC)
⦁    Server Message Block (SMB)
⦁    Multicasting