Admin Hp Thin Clients

7/27/2019 Admin Hp Thin Clients

1/56

Revision 1.1

Released: March 2004

Written for Deployment Server 6.0

T R A I N I N G A N D C E R T I F I C A T I O N

Managing HP Thin Clients

Students Guide

C O U R S E N U M B E R : 5 1 5 S U P P L E M E N T


2/56

Copyright 2004, Altiris, Inc. All rights reserved.

Altiris, Inc.

588 West 400 South

Lindon, Utah 84042

Phone: 801-226-8500

Fax: 801-805-1111

Altiris, Inc. assumes no responsibility for errors or omissions in this document, nor does Altiris

make any commitment to update the information contained herein.

Altiris Trademarks

Altiris Certified Engineer, Altiris Certified Professional (ACP), Deployment Solution,

PC Transplant (PCT), RapiDeploy, RapidInstall, and all other Altiris brands are trademarks or

registered trademarks of Altiris, Inc. in the U.S. and other countries.

All other brands and names are the property of their respective owners. These brands and names are

used only for explanation and to the owners benefit, without intent to infringe.


3/56

C ON TEN TS

2004 Altiris, Inc. iii

Chapter 1 Managing HP Thin Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1

Module 1 Managing HP CE.netThin Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3

HP Thin Clients Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-4

Managing Windows CE.net Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-5

Changing the Deployment Agent for CE.net Settings . . . . . . . . . . . . . . . . . . . . . . 1-7

Installing the Deployment Agent for CE.net . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-10

Removing the Deployment Agent for CE.net . . . . . . . . . . . . . . . . . . . . . . . . . . .1-12

Creating and Deploying Images for CE.net Thin Clients . . . . . . . . . . . . . . . . . . . . .1-13

Installing Embedded BootWorks on CE.net . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14

Creating a BootWorks Install Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-16

Installing BootWorks on CE.net Thin Clients . . . . . . . . . . . . . . . . . . . . . . . . . . .1-18

Removing Embedded BootWorks from CE.net . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-23

Non-Supported Deployment Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-25

Module 2 Managing HP Thin Clients Running Windowsxp Embedded . . . . . . . . . . . . . . . . . . . .1-27

Windows XP Embedded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-28

Deployment Agent for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-29

Understanding the Enhanced Write Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-30

Installing the Deployment Agent for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-33

Creating and Deploying Images to XPe Thin Clients. . . . . . . . . . . . . . . . . . . . . . . .1-37

Deploying XPe Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-39

Embedded BootWorks and XPe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-41

Embedded BootWorks Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-43

Creating BootWorks Installation Deployment Jobs . . . . . . . . . . . . . . . . . . . . . . 1-44

Removing Embedded BootWorks on XPe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-47

Installing New Thin Client images from HP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-50


4/56

iv 2004 Altiris, Inc.


5/56


2004 Altiris, Inc. 1-1

Chapter 1 Managing HP Thin Clients

Overview

In addition to managing computers running the standard Windows operatingsystems such as Windows 2000, XP, and Windows Server 2003, DeploymentSolution also gives you the ability to manage the HP Compaq thin clients.


6/56

1-2 2004 Altiris, Inc.

Altiris


7/56



MODULE 1 Managing HP CE.netThin Clients

Objectives

In this module, you will learn the unique information needed to manage HP thin

clients that are running the Microsoft Windows CE.net operating system including

the following topics:

A quick overview of the thin client

How to configure and re-install the Deployment Agent for CE.net

How to install or remove Embedded BootWorks


8/56


Altiris

HP Thin Clients Overview

Figure 1-1

A thin client is a small, solid-state device that connects to current or legacy

networks. These devices contain no local drives (in the typical sense) or moving

parts. Instead, all data is stored to flash RAM. This provides increased

manageability, security, control, and reliability.

Thin clients are often used in such areas as call centers, medical environments,

financial services, and other environments where access to centralized

applications and a desktop-like environment is required.

The HP thin clients, supported by Altiris, include all of the t5000 series of clients

which include the t5300, t5500, and the t5700 units.

Depending on the exact model you are working with, the thin client comespre-installed with either the Windows CE.net operating system or theWindowsxp Embedded operating system.

In addition, these thin clients also come with the applicable Deployment Agentpre-installed allowing you to begin managing them directly out of the box.

HP Thin Clients


9/56



Managing Windows CE.net Clients

Figure 1-2

When managing a thin client running the CE.net 4.2 operating system, thedeployment agent known as the Deployment Agent for CE.netwill already bepre-installed.

This agent is very similar in function to the Deployment Agent for Windows usedwith the standard Windows operating systems, but is slightly different toaccommodate the unique environment of the CE.net operating system.

The Deployment Agent performs the following limited tasks on the WindowsCE.NET platform:

Modify Computer Configuration (the computer name and TCP/IP Settingonly)

Distribute software (.CAB and .EXE files)

Execute and run scripts (DOS and WIN batch files) *no VBS support

Copy files and directories

Create disk images

Distribute disk images

Remote Control clients (24 bit color depth only. No chat or send file features)

Power Control (restart/shutdown/wake up jobs)

Set computer properties

Create conditions to run jobs and filter computers

Modify client properties via Windows and Linux agent settings

Additional features included with other Deployment Agents are not supportedin the Deployment Agent for CE.NET.

Deployment Agentfor CE.net

Deployment Agentfor CE.net


10/56


Altiris

Agent Settings

By default, the Deployment Agent for CE.net is configured to use the multicastmethod of locating the Deployment Server. This works well when theDeployment server and client are on the same network segment or when any

connecting routers and switches connecting these two devices are configured toforward multicast packets.

If your environment does not support either of these configurations, then youwill need to reconfigure the Deployment Agent for CE.net settings.


11/56



Changing the Deployment Agent for CE.net Settings

Figure 1-3

The Deployment Agent for CE.net properties can be remotely changed from aDeployment Console when the thin client has a current connection to theDeployment Server.

If this connection is not possible, then the changes must be made from the thinclient itself.

Deployment Agent for CE.net Properties

The Deployment Agent for CE.net properties or options (although similar to theDeployment Agent for Windows properties) are limited to the settings show belowand can be changed from ether the Deployment Console or from the thin clientusing the following locations.

Table 1-1

Agent Setting Type Thin Client Location

Deployment Console

Location

Log Files Logtab Log File tab

Time Synchronization General tab Othertab

User Prompt Security Security tab User Prompts and

Remote Control tabs

Transport Transporttab Transporttab


12/56


Altiris

Making Changes from a Deployment Console

To remotely change the agent settings from a Deployment Console, complete thefollowing steps:

1. From the Deployment Console, right-click on the desired computer(s) or group

of computers and select the Change Agent Settings > Windows/Linux Agentoption.

2. Select the applicable tabs and make the changes needed.

For example, to change how the client connects to the Deployment Server,click on the Transport tab and change any needed values.

3. After making all of the needed changes, click OK.

All of the computers selected will now have these changes made.

To automatically change all new clients, connecting to your Deployment Server,you can use the following steps:

1. From the Deployment Console select Tools > Options > Agent Settings.

2. Select theForce new agents to take these default settings box and clickChange Default Settings.

3. Make the applicable changes and click OK.

4. Click OK again to exit the Program Options screen.

From this point on, any new computers or thin clients connecting to theDeployment Server will use these settings.

These settings will not be applied to any computers or clients currently exiting

in the Deployment Database.


13/56



Making Changes from a CE.net Thin Client

To change the agent settings from a thin client, complete the following steps:

1. Log on to the thin client.

2. Click on the agent icon displayed on the taskbar.

3. Click Properties.

You can now select the applicable tabs and edit the needed agent properties.


14/56


Altiris

Installing the Deployment Agent for CE.net

Figure 1-4

The Deployment Agent for CE.net is pre-installed on all HP thin clients running theCE.net operating system. If you remove the agent and need to reinstall it, this canbe accomplished from the thin client only. The Deployment Console cannot pushthe Deployment Agent for CE.net to the clients running Windows CE.net.

To install the Deployment Agent for CE.net from the client computer, use thefollowing general steps:

For detailed information on how the AClient.inp file works see the DeploymentSolution product guide.

1. From the server running the Deployment System Access Point, move to theAgents\CEAgent subfolder (by default this is c:\Program Files\Altiris\eXpress\ Deployment Server\Agents\CEAgent).

2. Rename the EXE and DLL files used to install the agent.

For example, if the current names of the install files areADCService_6.0.74.dlland CEClient_6.0.74.exe, you must rename them toADCService.dll andCEClient.exe.

3. Log on to the thin client using a user with Administrator rights.

4. Click Start > Run and attach to your Deployment System Access Point.

\\FS1\Agents\CEAgent\CEClient.exe\\FS1\Agents\CEAgent\aclient.inp-install


15/56



For example, if your Deployment System Access Point is installed to a severnamed FS1 and is using the default share name of eXpress, you would enter:

5. Using the Start > Run method, install the agent using a command similar to thefollowing:

\\FS1\Agents\CEAgent\CEClient.exe \\FS1\Agents\CEAgent\aclient.inp -install

For the above command to work, the AClient.inp file must be located in theCEAgent folder and the AClient.inp file must be configured with the proper

installation path ofInstallDir=\Hard Disk\Program FilesFor detailed information on how to configure the AClient.inp file see theDeployment Solution product guide.


16/56


Altiris

Removing the Deployment Agent for CE.net

Figure 1-5

If the Deployment Agent for CE.net needs to be removed for any reason, it can beuninstalled using the Deployment Console or from the CE.net thin client usingthe following general steps.

Using the Deployment Console to Remove the Agent

This method will only work if the agent is currently installed and connected to theDeployment Server.

1. From the Deployment Console, right-click on the computer icon of the thinclient you want to remove the agent from and select Advanced > UninstallWindows Agent.

2. Click Yes to confirm you want to remove the agent.

The scheduling screen will be displayed.

3. Configure the applicable schedule and click OK.

Removing the Agent at the Thin Client

The Deployment Agent for CE.net can be removed while working at a thin client

using the following general steps:

1. From the thin client running the CE.net operating system and DeploymentAgent for CE.net, click Start > Run.

2. In the Open box, type the following, substituting the server name of FS1 withthe name of your server (change the path if needed as well):

\\FS1\Agents\CEAgent\CEClient.exe -remove

3. Click OK.


17/56



Creating and Deploying Images for CE.net Thin Clients

Figure 1-6

With the Deployment Agent for CE.net installed and connected the toDeployment Server, creating and deploying images of this device is no differentthan creating and deploying images for standard Windows operating systemssuch as Windows 2000 or XP.

Details on how to create these types of Jobs can be found in the DeploymentSystem Basics chapter, in module 4. A brief review of these steps are listedbelow:

From the Deployment Console, create a new Job.

Add the Create (or Distribute) Disk Image Task Configure the above Task with the proper image name and location.

Assign and schedule the Job on the applicable CE.net thin clients.


18/56


Altiris

Installing Embedded BootWorks on CE.net

Figure 1-7

Deployment Solution has the ability to create BootWorks Install packages forCE.net devices allowing you to install BootWorks files and commands on a thinclient.

Among other things, BootWorks (in general terms) includes a DOS boot imageand the files and commands needed to attach to a server where images can bestored or retrieved as needed. It also includes the ability to check with theDeployment Server to see what if any Jobs or Tasks need to be run.

Installing BootWorks on the thin client is only needed when the client does notsupport PXE (Intels Pre-boot Execution).

Because of the space limitation of thin clients and for ease of use, Altiris highlyrecommends that you use PXE instead of Embedded BootWorks when possible.

Installing BootWorks on CE.net requires more program memory allocation thanthe amount provided by the default setting of the operating system. Therefore,the memory setting must be changed prior to installing embedded BootWorks.

HP provides theMemory Allocation Change Utility (available fromhttp://www.hp.com/products/thinclientsoftware) that can be used to change thememory allocation to allow enough room to install BootWorks. This utility

(smad.exe) can be executed on all machines remotely through a DeploymentServer Job.


19/56



As an alterative to using a Deployment Job to change the memory, the memoryallocation can be manually changed by selecting the Start > Settings >Control Panel > System > Memory tab and then moving the slider to adjust theStorage Memory. You must have approximately 11456 KB (or more) to installembedded BootWorks on a thin client running CE.net.

Another option for freeing up additional disk space is to uninstall the pre-installedHP applications. With this method you can free up to as much as 10 MB of diskspace. If the slider is not placed around the middle of the Memory tab, then anError 112 may occur.


20/56


Altiris

Creating a BootWorks Install Package

Figure 1-8

To be able to install BootWorks through a Deployment Job, you must first create aBootWorks install package.

To create a CE.net BootWorks Install package, complete the following steps:

1. From a Deployment Console, click Tools > Boot Disk Creator.

2. When the opening selection screen appears, choose Create a NewConfiguration and click OK. If this screen is not displayed, click NewConfiguration.

3. Enter a unique name for the configuration (e.g., BWCE) and a description if

desired and then click Next.

4. Select BootWorks Install Package, check the button forInstall toWindowsCE.netand click Next.

5. SelectMicrosoft Windows and click Next.

6. From theNetwork Adapters screen, select the VIA Rhine II Fast EthernetAdapterdriver from the list and click Next.

7. Select Obtain an IP Address from a DHCPserver and click Next.

8. Select Use TCP/IP to connect to Altiris Express Server, enter the applicable IPaddress and port number, and click Next.

9. Enter the domain or workgroup and account privileges to connect to the serverand click Next.


21/56



10. SelectManually Create Drive Maps, verify the UNC path to the eXpress shareon the Altiris server is correct, and click Next.

11. Verify that all of the information on theFinish screen is correct and clickFinish.

12. On the pop-up window, choose Create a Windows Installation Package Fileand click OK.

13. Make sure the package name and path is what you want.

14. Place a check mark in the Run in quiet modebox and click Next.

15. When the package is complete, click Close and exit the Boot Disk Creatorprogram.


22/56


Altiris

Installing BootWorks on CE.net Thin Clients

Figure 1-9

With a BootWorks install package created, you can now use the power of theDeployment System to install embedded BootWorks to all of the CE.net thinclients requiring it.

Before begin, you must first download the Configure Memory Allocation ChangeUtility from the HP Web site.(See www.hp.com/products/thinclientsoftware).

After you have downloaded the memory utility (smad.exe), unpack and save itinto a folder on the Deployment System Access Point computer and note the

location (for example: c:\Program Files\Altiris\eXpress\Deployment Server\CE_CABS).

Part I Creating Tasks Changing the Memory Settings

The Deployment Job used to install BootWorks will consist of severalDeployment Tasks. The first few Tasks will be configured to ensure that there isenough Storage Memory to install BootWorks.

1. From the Deployment Console, right-click in the Jobs window and selectNew Job.

2. Give the Job a descriptive name that can be easily remembered, such as:Install BootWorks on CE.net.

3. In the upper right corner of theJob Detail pane, click Add > Copy File to.

4. Select Copy File and enter the path to the Configure Memory AllocationChange Utility that was downloaded from the HP Web site.

For example:c:\Program Files\ Altiris\ eXpress\Deployment Server\CE_CABS\smad.exe

Tasks to change storage memoryTasks to change storage memory

Tasks to install BootWorksTasks to install BootWorks




23/56



5. Enter the following into the destination path:\temp\smad.exe

6. Click Finish.

7. In the upper right corner of theJob Detail pane, click Add > Run Script.

8. Select Run this script and enter the following in the script window:cd \tempsmad.exe 22528 (the amount of memory may differ on different hardware)

This will change the program memory allocation to 22528 KB.

9. From the In which OS would you like to run this script area, selectWindows. and click Finish.

Part II Creating Tasks to Install BootWorks

You are now ready to create the Deployment Tasks needed to install BootWorks.



24/56


Altiris

2. Select Copy File and enter the path to the CE.net BootWorks InstallationPackage created earlier (for example; c:\Program Files\Altiris\eXpress\Deployment Server\BWpkgs\BWCE.exe).

3. In the Destination path field, enter the name of the file into the temporary folderof the client:

For example:\temp\BWCE.exe

4. Click Finish.

5. In the upper right corner of the Job Detail pane, click Add > Run Script.

6. Select Run this scriptand enter the following in the script box:cd \tempBWCE.exe(use the name of your package here)

7. From the In which OS would you like to run this script area, select Windowsand click Finish.


25/56



You now have a Deployment Job that will adjust the memory and installBootWorks.

Part III Running the BootWorks Install JobUse the following steps to assign and schedule the Deployment Job that willinstall BootWorks.

1. Drag-and-drop your newly created Deployment Job to the selected devices orgroup of devices.

A Schedule Computer Job screen appears.

2. Select an applicable scheduling option and click OK.

3. After the Deployment Job is run on the target system, the machine will reboot.

When the machine returns to Windows, the process is complete.You can also tell when the Job is complete by lookingfor a green check mark associated with the Job.






26/56


Altiris

Part IV (Optional) Changing the Memory

If desired, you may want to add an additional Deployment Task that will changethe Storage Memoryback to the original size. This can be accomplished using thesame basic steps used to change the memory as listed above, but changing thesize back to the default of 1024 KB.

1. Add another Task to copy the Configure Memory Allocation Change Utility tothe clients.

2. Add another Task to run the Configure Memory Allocation Change Utility.


27/56



Removing Embedded BootWorks from CE.net

Figure 1-10

Building a Remove BootWorks Package

To remove embedded BootWorks from a CE.net thin client, complete thefollowing steps:


2. Give the Job a descriptive name that can be easily remembered, such as:Remove BootWorks from CE.net.


4. Select Copy File and enter the path to the BootWorks uninstall utility (forCE.net) named BWINSTCE.

5. Enter the following into the destination path:\temp\bwinstce.exe

6. Click Finish.


28/56


Altiris

7. In the upper right corner of theJob Detail pane, click Add > Run Script.

8. Select Run this script and enter the following in the script window:cd \tempbwinstce -u -q (-u = uninstall, -q= use quiet mode)

9. Select to run this script using the Windows operating system. (See the figure

above.)10. Click Finish.

11. Assign your BootWorks uninstall Job to the desired computers and schedulethem to run at an applicable time.


29/56



Non-Supported Deployment Functions

When managing thin clients running the CE.net operating system, the followingDeployment Solution features cannot be used:

PC Transplant

Chat

RapidInstall

Some of the Change Agent Settings functionality(see the supported feature listed earlier in this document)

Visual Basic Scripts


30/56


Altiris


31/56



MODULE 2 Managing HP Thin Clients RunningWindows

xpEmbedded

Objectives

In this module, you will learn the unique information needed to manage HP thin

clients that are running the Microsoft Windowsxp Embedded operating system

including the following topics:

How to configure and reinstall the Deployment Agent for Windows

How to install or remove Embedded BootWorks

Specific issues relating to thin clients running the Windowsxp

Embeddedoperating systems including such things as:

Understanding and using Windowsxp

Enhanced Write Filter


32/56


Altiris

Windows XP Embedded

Figure 1-11

Windows XP Embedded is Microsofts embedded operating system that deliversthe power of the Windows operating system in componentized form, enablingembedded developers to rapidly build reliable and advanced embedded devices.

Based on the same binaries as Windows XP Professional, Windows XPEmbedded enables embedded developers to choose from over 10,000 individualfeature components to achieve optimum functionality in a reduced footprint.

To take advantage of this powerful embedded operating system, HP hasprovided the ability to install and use Windows XP Embedded (commonlyreferred to as XPe) on several of its thin client devices such as the T5700.

Managing these devices using Deployment Solution is easy and quick, however,because of a few unique features of XPe, it is important to understand whatadditional steps need to be taken to manage these devices.

Windows XP Embedded:

Allows Developers to rapidly buildadvance embedded devices suchas the HP Compaq Thin Client

XPe is based on the same binariesas Windows XP Professional

XPe has over 10,000 featurescomponents, yet fits in a smallfootprint

The HP t57000 ships with XPeinstalled

Requires a few unique steps tomanage with Deployment Systems


33/56



Deployment Agent for Windows

Figure 1-12

As is the case when managing the other Windows platforms such as Windows2000 and XP (and more), it is important to install the applicable DeploymentAgent.

When working with XPe, the same agent used for the standard Windowsoperating systems is used. This agent is called the Deployment Agent forWindows. HP ships its thin clients with this agent pre-installed.

By default, the Deployment Agent for Windows is configured to use the multicastmethod of locating the Deployment Server. This works well when theDeployment server and client are on the same network segment or when anyconnecting routers and switches connecting these two devices are configured toforward multicast packets.

If your environment does not support either of these configurations, then youwill need to reconfigure the Deployment Agent for Windows settings.

This is accomplished using the same techniques used for computers running thestandard Windows operating system.

For example, from a Deployment Console, you can right-click on a computer orgroup of computers and select Change Agent Settings > Windows/Linux Agent.

The agent settings are then displayed and can be changed as needed. ClickingOK from this screen will send the desired changes to the computers selected.

The agent settings can also be changed by double-clicking on the Agent icondisplayed in the taskbar.

For detailed information on the meaning of each agent property, see theDeployment System Agent chapter or the Deployment Solution Product Guide.

Deployment Agentfor Windows

Preinstalled on allXPe HP Thin Clients


34/56


Altiris

Understanding the Enhanced Write Filter

Figure 1-13

The major factor that makes managing XPe different from a standard Windowscomputer is the unique Enhanced Write Filter used to protect the contents of thefiles and operating system installed on a thin client.

The Enhanced Write Filter allows the operating system to boot from a disk volumeresiding on any read-only media such as flash media, CD-ROM, or awrite-protected hard drive while maintaining the appearance of read/writeaccess to the operating system.

Enhanced Write Filter protects the contents of a volume on the target media byredirecting all writes to another storage location, called an overlay. Used in thiscontext, an overlay is similar to a transparency overlay on an overhead projector.Any change made to the overlay affects the picture as seen in the aggregate, but ifthe overlay is removed, the underlying picture remains unchanged.

Enhanced Write Filter can protect one or more bootable and non-bootable diskvolumes, including such things as a thin clients flash ROM.

For each protected volume, you can choose whether you want to retain theoverlay information in a disk overlay, on a predesignated disk partition called theEnhanced Write Filter volume, or in RAM overlay, which uses system memory.With a RAM overlay, all overlay information is lost when you shut down orreboot the target system. With disk overlay, the information is retained after

rebooting.

By default the thin clients are configured to save most if its changes to the RAMoverlay and therefore they are lost when the client is rebooted.

Therefore, simple Tasks such as installing the Deployment Agent for Windows orreconfiguring a thin client after it has been deployed (such as changing thecomputers name and IP address) cannot be done while the Enhanced Write Filteris enabled.


35/56



To successful install the Deployment Agent for Windows or to successfullyreconfigure a thin client after it has been imaged, you simply need to make sureyour Deployment Jobs include a Task to disable the Enhanced Write Filterbeforethe attempting to do the regular Tasks and then to have another Task at the endof the Deployment Job that will enable the Enhanced Write Filter.

This module has been written for Deployment Solution 6.0.With Deployment Solution 6.1 or higher the need to disable the Enhanced WriteFilter will not be needed for imaging or installing the Deployment Agent.

Using the EWFMGR Utility

Enabling or disabling the Enhanced Write Filter is done using a XPe utility namedewfmgr.exe and is stored in the C:\Windows\System32 folder.

Although there are many switches that can be used with this utility, you typically

will only use the following three or four:

The following are a few examples of how to use the ewfmgr.exe program:

Table 1-2

Switch Description

-all Performs a specified command (such as disable or

enable) on all protected volumes. The default

command is to display protected volume

information.

-disable Disables the overlay on the specified protected

volume.

-enable Enables the write filter so that data written to the

protected media is cached in the overlays. The

current overlay level becomes 1 as soon as EWF is

started, and a new overlay is created at level 1.

-commitanddisable Commits all current level data in the overlay to the

protected volume and disables the overlay.

Table 1-3

Example Description

ewfmgr -all This will display the current Enhanced Write Filter

settings.

ewfmgr c: -disable This will disable the Enhanced Write Filter on the C:

volume.


36/56


Altiris

Although the enhanced Write Filter manager can be run from a thin client, it ismore efficient to include it as part of your Deployment Job.

To give you an idea of how this is accomplished, you will be shown how to createa Deployment Job that will allow you to install the Deployment Agent forWindows and how to create a Deployment Job that will allow you to re-image athin client running XPe.

ewfmgr c: -enable This will enable the Enhanced Write Filter on the C:

volume.

Table 1-3

Example Description


37/56



Installing the Deployment Agent for Windows

Figure 1-14

Installing the Deployment Agent for Windows to an XPe system requires two steps:

Installing the agent

Committing the changes

Installing the Deployment Agent for Windows is rarely needed because the agent ispre-installed by HP.

Installing the Deployment Agent for WindowsThe Deployment Agent for Windows can be installed to all of your XPe thin clientsremotely from the Deployment Console. This is accomplished using the RemoteAgent Installerfeature.

To install the agent using the Remote Agent Installer, use the following steps:

1. From the Deployment Server consoles menu bar, select Tools > Remote AgentInstaller.

2. Select the Use this username and password for all clients option


38/56


Altiris

3. Enter the username and password of the account that exists on the remotecomputers.

4. Click Next.

5. If you need to change any of the agent settings, click Change Settings from theGathering Default Installation Information screen now displayed. Makethose changes and click OK.

6. After you have returned to the Gathering Default Installation Information

screen, click Next.The Selecting Clients window will now be displayed.

7. Click Add.

This will open the Browse computers window.

8. Using this screen, locate and select your client computer and click OK.

9. Click Finish to start the installation of the agent on the computers you haveadded.

When the has been successfully installed, you will see the agent icon on thethin client computers Windows taskbar and the ball on the icon will be blueif the computer can locate the Deployment Server.


39/56



10. Click Exit Install.

DO NOT rebootthe thin client at this point.The Deployment Agent for Windows is now installed, but if you reboot theagent installation will be removed.

Committing the Changes

The final step is to commit the installation of the Deployment Agent forWindows to the thin clients. This step can also be accomplished remotely fromthe Deployment Console using a Deployment Job.

To commit the change of adding the Deployment Agent for Windows to the thinclients, complete the following steps:

1. From the Deployment Console, right-click in the Jobs window and select NewJob.

2. Give the new job a descriptive name that can be easily remembered, such asCommitting Changes for XPe.

3. Click Add > Run Script.

4. Select Run this script and enter the following Write Filter command:ewfmgr c: -commitanddisable

This command will tell the thin client that you want to save the changesmade to the computer and will also disable the Write Filter so those changescan be made the next time the computer is booted.

5. From the In which OS would you like to run this script area, select Windows.6. Click Finish.

7. The next Task needed is one to tell the computer to reboot.Click Add > Power Control.

8. Select Restart and click Finish.


40/56


Altiris

9. Using the same basic steps as you just used, create a new Run Script Task thatwill enable the Write Filter using the following command:ewfmgr c: -enable

10. You now need to add a final Task to reboot the computer again. Click Add >Power Control,select Restart, and click Finish.

Your commit changes Deployment Job is now finished and will look similarto the following:

11. Using the drag-n-drop method, assign this Job to the same computers youinstalled the Deployment Agent for Windows on and schedule it to run at anapplicable time.

When the Deployment Job is run, the Write Filter will be disabled and theagent files and settings will be saved. The Write Filter will then be enabled.


41/56



Creating and Deploying Images to XPe Thin Clients

Figure 1-15

The basics of creating or deploying an image for thin clients running XPe is thesame as creating or deploying an image of a standard Windows operating systemsuch as Windows 2000 or XP. The one exception, however, is that the EnhancedWrite Filter must be turned off before a Deployment Job can configure a thinclient after it has received an Altiris image.

When Deployment Solutions is installed, several sample Deployment Jobs areincluded. Among these sample Jobs are several XPe Jobs that can be copied and

then edited saving you the time of creating these Jobs from scratch.

The sample Jobs can be found in the Deployment Consoles Job pane under theSamples > XP Embedded folder. (See Figure 1-15.)

For example to create a new Deployment Job that will create an image of an XPethin client, complete the following steps:

These steps assume that you have configured and are using PXE to help in thecreation of the images. If needed see the Deployment Solutions modules on how toconfigure PXE. If you are not using PXE, then it is assumed that EmbeddedBootWorks has been installed on the thin clients. Installing Embedded BootWorks

on a XPe thin client will be discussed later in this module.

1. From the Deployment Console locate and select (highlight) theSamples > XP Embedded > Create Disk Image Task.

2. Right-click on this image Task and select Copy.

3. Right-click on the folder where you want to copy the Job to and click Paste.


42/56


Altiris

4. Select this Job. The Tasks it contains will be displayed in the details area of theconsole (upper right-hand corner).

5. This Job can be used as it is (without modification) as long as you are satisfied

with the location and name of the image that will be created.

By default, the image will be named using the computers NETBIOS name(because of the COMPNAME token used) as it is stored in the DeploymentDatabase and the image will be saved in a subfolder of the Deployment SystemAccess Point namedImages.

If you need to change the name or path, double click on the Create Disk ImageTask and enter the new information.

6. You can now use the drag-n-drop technique to assign and schedule the Job tothe desired thin client.

In this Job you will notice that there are two Run Script Tasks used, one todisable the Enhanced Write Filter and one to enable it. You will not need to changethese, but they can be viewed or changed by double clicking on the Task.

By default, these Tasks are configured as follows:

Disable the Enhanced Write FilterDisable the Enhanced Write Filter

Enable the Enhanced Write FilterEnable the Enhanced Write Filter


43/56



Deploying XPe Images

Figure 1-16

With an XPe image created, you can now deploy this image to other thin clients.

The Enhanced Write Filter included with the thin client image is built into a verysmall RAW formatted flash partition on the client. Due to current limitations of theEnhanced Write Filter, this partition cannot be restored unless the flash is the samesize as the flash from which the image was created. For example, an image that wascreated from a 192 MB flash should only be restored to systems with a 192 MBflash.

With Deployment Solutions 6.1 or higher, you will be able to image to clients with

different size flash partitions.

Additionally, any new updated images released by HP will need to be restoredusing the Hewlett Packard Imaging Utility (IBR).

To deploy an Altiris image of an XPe device, use the sample Jobs as describedbelow:

1. From the Deployment Console locate and select (highlight) theSamples > XP Embedded > Distribute Disk Image Task.

2. Right-click on this image Task and select Copy.

3. Right-click on the folder where you want to copy the Job to and click Paste.


44/56


Altiris

4. Select this Job. The Tasks it contains will be displayed in the details area of theconsole (upper right-hand corner).

5. This Job can be used as it is (without modification) as long as the Deploy Image

Tasks path and file name matches the name and path where the XPe imageresides.If you used the default settings from the Create Disk Image Job then these arethe same.

If you need to change the path or name, double-click on the Deploy ImageTask and make the needed changes.

6. You can now use the drag-n-drop technique to assign and schedule the Job tothe desired thin client.

As you look closely at this Job to deploy the image, that there is no Task todisable the Enhanced Write Filter. This is not needed because the image wascreated after the Enhanced Write Filter was disabled.


45/56



Embedded BootWorks and XPe

Figure 1-17

Deployment Solution has the ability to create BootWorks Install packages for allof the standard Windows operating systems, including Windows XPe. Thisallows you to install the BootWorks files and commands on a thin client.

Among other things, BootWorks, in general terms, includes a DOS boot imageand the files and commands needed to attach to a server where images can bestored or retrieved as needed. It also includes the ability to check with theDeployment Server to see what if any Jobs or Tasks need to be run.

Installing BootWorks on the thin client is only needed when the client does notsupport PXE (Intels Pre-boot Execution).

Because of the space limitation of thin clients and for ease of use, Altiris highlyrecommends that you use PXE instead of Embedded BootWorks when possible.

Creating a BootWorks Install Package for XPe

To create a standard BootWorks Install package that can be used on WindowsXPe, perform the following steps:

1. From a Deployment Console, click Tools > Boot Disk Creator.

2. When the opening selection screen appears, choose Create a NewConfiguration and click OK.

3. Enter a unique name for the configuration (e.g., BWXPe) and a description ifdesired and then click Next.

4. Select BootWorks Install Package and click Next.

5. SelectMicrosoft Windows and click Next.

BootWorks can be embedded or installed to aXPe thin client

BootWorks includes a DOS image, files andcommands needed to create and deployimages and perform other tasks

BootWorks is only needed when PXE is notbeing used


46/56


Altiris

6. Select the VIA Rhine II Fast Ethernet Adapterdriver from the list and clickNext.

7. Select Obtain an IP Address from a DHCPserver and click Next.

8. Select Use TCP/IP to connect to Altiris Express Server, enter the applicable IPaddress and port number, and click Next.

9. Enter the domain or workgroup and account privileges to connect to the serverand click Next.

10. SelectManually Create Drive Maps, verify the UNC path to the eXpress shareon the Altiris server is correct, and click Next.

11. Verify that all of the information on theFinish screen is correct and clickFinish.

12. On the pop-up window, choose Create a Windows Installation Package Fileand click OK.

13. Make sure the package name and path is what you want and click Next.

14. When the package is complete, click Close and exit the Boot Disk Creatorprogram.


47/56



Embedded BootWorks Prerequisites

Figure 1-18

With the Embedded BootWorks install package for Windows created, you cannow remotely install Embedded BootWorks using a Deployment Job.

To install Embedded BootWorks, you must have anywhere from 5 to 10 MG offree contiguous disk space. To check for the amount of free disk space right-clickon the desired thin client from within the Deployment Console and selectProperties. Click Drives (from the left pane). The amount of free space will belisted on the line labeled Capacity.


48/56


Altiris

Creating BootWorks Installation Deployment Jobs

Figure 1-19

To create the Job that will install your Embedded BootWorks package, completethe following steps:

1. From the Deployment Console, create a new Job by right-clicking in the Jobpane and selecting New Job.

2. Give the new Job an applicable name that is easy to remember, such asInstallEmbedded BW for XPe.

3. Click Add > Run Scripts.

4. Configure the Run Script Task as follows:

5. Click Finish.

6. Click Add > Power Control, select Restart, and click Finish.

7. Click Add > Distribute Software.


49/56



8. Use the browse feature to locate and select the BootWorks install package youcreated earlier.

9. Click Finish.

10. Click Add > Run Script and configure the script to as follows:


12. The install Embedded BootWorks Job is now ready to be assigned to theapplicable thin clients running XPe.


50/56


Altiris

13. From the Deployment Console, use the drag-n-drop method to assign this newJob to the desired computers.


51/56



Removing Embedded BootWorks on XPe

Figure 1-20

If for some reason you need to remove embedded BootWorks from a thin clientthat is running XPe, you will need to first create an uninstall package and then aDeployment Job to run this package.

Building a Remove BootWorks Package

To build a package that will remove embedded BootWorks from a XPe thin client,complete the following steps:

1. From the Deployment Console, run the Boot Disk Creatorby selectingTools > Boot Disk Creator from the consoles menu bar.

2. If prompted to create a new configuring, click Cancel.

3. From the Boot Disk Creator menu bar, select the Tools > Create a BootWorksWindows Uninstall Package option.

4. Enter the desired name and location.

5. Click Run in quiet mode and click Next.

6. Click Close.

7. Close the Boot Disk Creator program.

Running the BootWorks Uninstall Package

To use the BootWorks uninstall package you just created, create and use thefollowing Deployment Job:



52/56


Altiris

2. Give the Job a descriptive name that can be easily remembered, such asUnInstall BootWorks.

3. Click Add > Run Scripts.

4. Configure the Run Script Task as follows:

5. Click Finish.


7. Click Add > Distribute Software.

8. Use the browse folder icon to locate and select the BootWorks uninstallpackage you created earlier and click Finish.


53/56



9. Click Add > Run Script and configure the script to as follows:

10. Click Add > Power Control, select Restart, and click Finish.Your Job is now complete.

11. You can now use the drag-n-drop method to assign and schedule this Job to theneeded thin clients.


54/56


Altiris

Installing New Thin Client images from HP

Figure 1-21

From time to time HP may release a newer images of the XPe operating system toupgrade your thin clients to a newer version. These images are not Altiris imagesand therefore cannot be deployed using Altiris RapiDeploy imaging software.

However, a Deployment Solution Job can be created that can deploy the HPimage. This Job will utilize Hewlett Packards imaging utility (commonlyreferred to as the IBR utility) to install the image.

To customize and deploy a new thin client image from HP, the following generalsteps need to be completed:

Download the appropriate image from HP. These are usually stored in theform of a SoftPaq (see http://www.hp.com/products/thinclientsoftware)

Unpack the new thin client image and tools for deployment as delivered fromHP.

Create a Deployment Job to deploy the HP image.

Deploy the IBR job to units to be updated. This updates the thin clients withthe new version of the image from HP.

Deploying Images Released by HP

To unpack the image and tools for deployment, complete the following steps:

1. Double-click on the softpaq you downloaded containing the new HP imageand deployment tools.


55/56



2. When prompted, click Deployment.

3. When prompted, select the destination directory for the imaging tools andimage. This should be stored on your Client Access Point server. For example,C:\Program f\Files\Altiris\eXpress\Deployment Server\tcimages

The components are now unpacked to the specified directory. When thisprocess is complete, there will be three new files in the specified folder:

IBR.EXE HPs image restoration utility

FLASH.IMG The OS image

RECOVERY.PDF Documentation

Ensure that IBR.EXE and FLASH.IMG are stored in the same directory on theserver.

4. From the Deployment Console, click File > New > Job.

5. Enter a unique name for the Job that you will use to deploy the original thinclient image. For example, Install HP Image.

6. Click Add > Run Script.

7. Configure the Run Script as follows:F:\tcimages\ibr.exe flash.img HD0 -y(set the OS type to DOS)

The -y switch allows the image to be deployed without requiring user input.

Change the path and name tomeet your environment

Change the path and name tomeet your environmentChange the path and name tomeet your environment

Change the path and name tomeet your environment


56/56

Altiris

8. Click Finish.

Your Job is now complete.

9. You can now use the drag-n-drop method to assign and schedule this new Jobto the desired thin clients.

Documents

Admin Hp Thin Clients