How to manage and image Thin clients

Article:HOWTO1563  |  Created: 2005-09-09  |  Updated: 2012-04-04  |  Article URL http://www.symantec.com/docs/HOWTO1563
Article Type
How To

Product(s)



Question
How do I manage or image a thin client?

Answer
 

A prerequisite to imaging thin clients is that PXE server needs to be installed and configured. For information on how to image Thin clients with USB drives, click here.

However, if you are using the Linux Boot, you need to add to the rc.local /mnt/ds/linux/rdeployt also add to call the image.

./rdeployt –md –f[imagename.img]

This is the command line to Deploy the image to the client.

./rdeployt –mu –f[imagename.img]

This is the command line to Create  the image from the client.

From the client computer, at the #  prompt

 cd /mnt/ds/rdeploy/linux

Then type:

./rdeployt -md -f/mnt/images/image.img

Verify the services are not already installed. View Windows Services and check for:

  • Altiris PXE Config Helper.
  • Altiris PXE Manager (only on the Deployment Server computer).
  • Altiris MTFTP Server.
  • Altiris PXE Server.

If they are there then execute PXE Configuration Utility: Deployment Server Console > Tools > PXE Configuration. The Boot menu will show Next Device (Deployment Solution 6.8 build) or Local Boot (Deployment Solution 6.5 build) as the First Boot Option. If there are no jobs assigned to the client to boot into an automation (Imaging), then the client needs to have the first boot option as production. Following the production boot menu should be the automation boot menu. 

Note: Within the PXE configuration, and select the DS tab. Default Boot option needs to be an automation boot instead of a local boot/Next Device. If there is a automation job assigned to the client (Imaging) then the client needs to know which automation boot to use. If this is set to Local boot or Next Device then the client will repeatedly reboot into production and never picks up the image job.
 
If PXE server is not installed, but Deployment Solution is, then locate the axinstall.exe. This is located in the C:\DSSetup\axinstall.exe. (Skip to install the PXE server.) It may be in a different location depending on the extraction of the components during the Deployment Server install.

The Components can be re-downloaded from ftp.altiris.com/Product/DeploymentServer > Altiris_DeploymentSolutionWin_6_5.exe or Altiris_DeploymentSolutionWin_6_8.exe. After the download is complete, only extract the file but do not execute.
 
Installing the PXE Server

  1. Run the axinstall.exe from the C:\DSSetup.
  2. Choose the Component Install option (third option) and accept the Software License Agreement.
  3. Enter the path to the eXpress share or it may have already detected the share.
  4. Choose Altiris PXE Server from the list of additional components.
  5. Choose to install on the same computer or remotely. (Credentials may need Domain\Username if remotely.) Select the computer you would like to install it on.
  6. When Installation is finished you have an option to install Adobe’s Acrobat Reader*.
  7. If installing on a remote box PXE Manager will on reside on the Deployment Solution computer. PXE Manager is installed during the Deployment Server Installation. Open the PXE Configuration Utility. By default, the Shared Configuration options is is shown.
  8. To configure Remote PXE boot Images specific to a PXE Server (Local Configuration), you need to choose that PXE Server from the File Menu. Refer to Article Links at the end for full instructions.

Note: The client's BIOS needs to be set as Network Boot as First Boot Order inorder to be managed by PXE Server.

Managing HP Thin Clients Running CE.net

When managing a thin client running the CE.net 4.2 operating system, the deployment agent known as the Deployment Agent for CE.net will already be pre-installed. This agent is very similar in function to the Deployment Agent for Windows used with the standard Windows operating systems, but is slightly different to accommodate the unique environment of the CE.net operating system.

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

  1. Modify Computer Configuration (the computer name and TCP/IPSetting only)
  2. Distribute software (.cab and .exe files).
  3. Execute and run scripts (DOS and WIN batch files) *no VBS support.
  4. Copy files and directories.
  5. Create disk images.
  6. Distribute disk images.
  7. Remote Control clients (24-bit color depth only. No chat or send file features).
  8. Power Control (restart/shutdown/wake up jobs).
  9. Set computer properties.
  10. Create conditions to run jobs and filter computers.
  11. Modify client properties via Windows and Linux agent settings.

Additional features included with other Deployment Agents are not supported in the Deployment Agent for CE.NET. The Deployment Agent for CE.net is configured to use the multicast method of locating the Deployment Server. This works well when the Deployment server and client are on the same network segment or when any connecting routers and switches connecting these two devices are configured to forward multicast packets. If your environment does not support either of these configurations, then you will need to reconfigure the Deployment Agent for CE.net settings.

Changing the Deployment Agent for CE.net Settings

The Deployment Agent for CE.net properties can be remotely changed from a Deployment Console when the thin client has a current connection to the Deployment Server. If this connection is not possible, then the changes must be made from the thin client itself.

Deployment Agent for CE.net Properties

The Deployment Agent for CE.net properties or options (although similar to the Deployment Agent for Windows properties) are limited to the settings shown below and can be changed from ether the Deployment Console or from the thin client using the following locations.

Making changes from a Deployment Console

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

  1. From the Deployment Console, right-click on the desired computers or group of computers and select the Change Agent Settings > Windows/ Linux Agent option or Production Agent (Deployment Solution 6.5–6.8).
  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.
    • Agent Setting Type Thin Client Location Deployment Console Location Log Files Log tab
    • Log File tab
    • Time Synchronization General tab Other tab
    • User Prompt Security tab User Prompts and Remote
    • Control tabs
    • Transport Transport tab Transport tab
  2. Select the Force new agents to take these default settings box and click Change 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 the Deployment Server will use these settings. These settings will not be applied to any computers or clients currently exiting in the Deployment Database.

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.

Installing the Deployment Agent for CE.net

The Deployment Agent for CE.net is pre-installed on all HP Thin Clients running the CE.net operating system. If you remove the agent and need to reinstall it, this can be accomplished from the Thin Client only. The Deployment Console cannot push the 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 the following general steps. For detailed information on how the AClient.inp file works see the Deployment Solution product guide.

  1. From the server running the Deployment System Access Point, move to the Agents\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 are ADCService_6.8.282.dll and CEClient_6.8.282.exe, you must rename them to ADCService.dll and CEClient.exe.
  3. Log on to the thin client using a user with Administrator rights: \\FS1\Agents\CEAgent\CEClient.exe\\FS1\Agents\CEAgent\aclient.inp-install.
  4. Click Start > Run and attach to your Deployment System Access Point. For example, if your Deployment System Access Point is installed to a server named 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 the following:

\\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 the CEAgent folder and the AClient.inp file must be configured with the proper installation path of InstallDir=\Hard Disk\Program Files.

Removing the Deployment Agent for CE.net

If the Deployment Agent for CE.net needs to be removed for any reason, it can be uninstalled using the Deployment Console or from the CE.net thin client using the 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 the Deployment Server.

  1. From the Deployment Console, right-click on the computer icon of the Thin Client you want to remove the agent from and select Advanced > Uninstall Windows Agent (Deployment Solution 6.5–6.8 Uninstall 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 Deployment Agent for CE.net, click Start > Run.
  2. In the “Open” box, type the following, substituting the server name of FS1 with the name of your server (change the path if needed as well):

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

     
  3. Click OK.

Creating and Deploying Images for CE.net Thin Clients

With the Deployment Agent for CE.net installed and connected the to Deployment Server, creating and deploying images of this device is no different than creating and deploying images for standard Windows operating systems such as Windows 2000 or XP.

The steps are listed below:

  1. From the Deployment Console, create a new Job.
  2. Add the Create (or Distribute) Disk Image Task.
  3. Configure the above Task with the proper image name and location.
  4. Assign and schedule the Job on the applicable CE.net thin clients.

Changing the Memory

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

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

Removing Embedded BootWorks from CE.net

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

  1. From the Deployment Console, right-click in the Jobs window and select New Job.
  2. Give the Job a descriptive name that can be easily remembered, such as "Remove BootWorks from CE.net".
  3. In the upper-right corner of the Jobs Detail pane, click Add > Copy File to.
  4. Select Copy File and enter the path to the BootWorks uninstall utility(for CE.net) named BWINSTCE.
  5. Enter the following into the destination path:\temp\bwinstce.exe
  6. Click Finish.
  7. In the upper-right corner of the Job Detail pane, click Add > Run Script.
  8. Select Run this script and enter this 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.
  10. Click Finish.
  11. Assign your BootWorks uninstall Job to the desired computers and schedule them to run at an applicable time.

Non-Supported Deployment Functions

When managing thin clients running the CE.net operating system, the following Deployment 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

Managing HP Thin Clients Running Windows XP Embedded

Running the Microsoft Windows XP Embedded operating system  including the following topics:

  • How to configure and reinstall the Deployment Agent for Windows
  • Specific issues relating to thin clients running the Windowsxp Embedded operating systems including such things as: Understanding and using Windowsxp Enhanced Write Filter.

Windows XP Embedded

Windows XP Embedded is Microsoft’s embedded operating system that delivers the power of the Windows operating system in componentized form, enabling embedded developers to rapidly build reliable and advanced embedded devices. Based on the same binaries as Windows XP Professional, Windows XP Embedded enables embedded developers to choose from over 10,000 individual feature components to achieve optimum functionality in a reduced footprint. To take advantage of this powerful embedded operating system, HP has provided the ability to install and use Windows XP Embedded (commonly referred 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 what additional steps need to be taken to manage these devices. Windows XP Embedded:

  • Allows Developers to rapidly build advance embedded devices such as the HP Compaq Thin Client
  • XPe is based on the same binaries as Windows XP Professional
  • XPe has over 10,000 features components, yet fits in a small footprint
  • The HP t57000 ships with XPe installed
  • Requires a few unique steps to manage with Deployment Systems

To enable autologon:

  1. Log on locally to the XPe appliance as Administrator.
  2. Click Start > Run, then type autolog in the data field next to Open and click OK.
  3. Configure the Login name, Domain and password. Click the Enable button. An Autologon window will appear informing you that it was successfully configured. Click OK.

To disable autologon:

  1. Only the Administrator can disable autologon. For XPe 1.1 log off and log back on as the Administrator. For XPe 1.2 depress the shift key while selecting the log off option from the start menu. Once logged off you will be presented with the standard login screen. Log in as Administrator.
  2. Click Start > Run, then type autolog in the data field next to Open and click OK. Click the Disable button.

Deployment Agent for Windows (AClient)

If the clients do not show up in the Deployment Solution console it is very likely the AClient build is not the same build as the Deployment Solution server or the HP thin client, access the Registry and enable "ShowTrayIcon" under HKEY_LOCAL_MACHINE/Software/Altiris/Client Service by changing the value from 0 to 1. Use the Remote agent installer to install a new AClient within the Deployment Solution console. Deployment Solution console > Tools > Remote agent installer. Use the Admin credentials, click Next, and change the agent settings. Verify that the AClient has direct connection and has IP address of the Deployment Solution server.

Installing the ADLagent for Linux

As is the case when managing the other Windows platforms such as Windows* 2000 and XP (and more), it is important to install the applicable Deployment Agent. When working with XPe, the same agent used for the standard Windows operating systems is used. This agent is called the Deployment Agent for Windows. HP ships its thin clients with this agent pre-installed. By default, the Deployment Agent for Windows is configured to use the multicast method of locating the Deployment Server. This works well when the Deployment server and client are on the same network segment or when any connecting routers and switches connecting these two devices are configured to forward multicast packets. If your environment does not support either of these configurations, then you will need to reconfigure the Deployment Agent for Windows settings. This is accomplished using the same techniques used for computers running the standard Windows operating system.

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

Deployment Agent for Windows Preinstalled on all XPe HP Thin Clients

The agent settings are then displayed and can be changed as needed. Clicking OK 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 icon displayed in the taskbar. For detailed information on the meaning of each agent property, see the Deployment System Agent chapter or the Deployment Solution Product Guide.

Understanding the Enhanced Write Filter

The major factor that makes managing XPe different from a standard Windows computer is the unique Enhanced Write Filter used to protect the contents of the files and operating system installed on a thin client. The Enhanced Write Filter allows the operating system to boot from a disk volume residing on any read-only media such as flash media, CD-ROM, or a write-protected hard drive while maintaining the appearance of read/ write access to the operating system. Enhanced Write Filter protects the contents of a volume on the target media by redirecting all writes to another storage location, called an overlay. Used in this context, 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 if the overlay is removed, the underlying picture remains unchanged. Enhanced Write Filter can protect one or more bootable and non-bootable disk volumes, including such things as a thin clients flash ROM. For each protected volume, you can choose whether you want to retain the overlay information in a disk overlay, on a predesignated disk partition called the Enhanced Write Filter volume, or in RAM overlay, which uses system memory. With a RAM overlay, all overlay information is lost when you shut down or reboot 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 RAM overlay and therefore they are lost when the client is rebooted. Therefore, simple Tasks such as installing the Deployment Agent for Windows or reconfiguring a thin client after it has been deployed (such as changing the computer’s name and IP address) cannot be done while the Enhanced Write Filter is enabled.

To successful install the Deployment Agent for Windows or to successfully reconfigure a thin client after it has been imaged, you simply need to make sure your Deployment Jobs include a Task to disable the Enhanced Write Filter before the attempting to do the regular Tasks and then to have another Task at the end of 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.

Write Filter 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 named ewfmgr.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: 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. -commit and -disable Commits all current level data in the overlay to the protected volume and disables the overlay.

The following are a few examples of how to use the ewfmgr.exe program: Although the enhanced Write Filter manager can be run from a thin client, it is more 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 create a Deployment Job that will allow you to install the Deployment Agent for Windows and how to create a Deployment Job that will allow you to re-image a thin client running XPe.

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.

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

Installing the Deployment Agent for Windows

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

  1. Installing the agent. Committing the changes Installing the Deployment Agent for Windows is rarely needed because the agent is pre-installed by HP.
  2. Installing the Deployment Agent for Windows The Deployment Agent for Windows can be installed to all of your XPe thin clients remotely from the Deployment Console. This is accomplished using the Remote Agent Installer feature.

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

  1. From the Deployment Server console’s menu bar, select Tools > Remote Agent Installer.
  2. Select the Use this username and password for all clients option.
  3. Enter the username and password of the account that exists on the remote computers.
  4. Click Next.
  5. If you need to change any of the agent settings, click Change Settings from the Gathering Default Installation Information screen now displayed. Make those 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 have added. When it has been installed successfully, you will see the agent icon on the thin client computer’s Windows taskbar and the ball on the icon will be blue if the computer can locate the Deployment Server.
  10. Click Exit Install. Do not reboot the thin client at this point. The Deployment Agent for Windows is now installed, but if you reboot the agent installation will be removed.

Committing the Changes

The final step is to commit the installation of the Deployment Agent for Windows to the thin clients. This step can also be accomplished remotely from the Deployment Console using a Deployment Job. To commit the change of adding the Deployment Agent for Windows to the thin clients, complete the following steps:

  1. From the Deployment Console, right-click in the Jobs window and select New Job.
  2. Give the new job a descriptive name that can be easily remembered, such as “Committing Changes for XPe”.
  3. Click Add > Run Script.
  4. Select Run this script and enter the Write Filter command:  ewfmgr c: -commit -disable  . This command will tell the thin client that you want to save the changes made to the computer and will also disable the Write Filter so those changes can 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.
  9. Using the same basic steps as you just used, create a new Run Script Task that will 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.
  11. Using the drag-and-drop method, assign this Job to the same computers you installed the Deployment Agent for Windows on and schedule it to run at an applicable time. When the Deployment Job is run, the Write Filter will be disabled and the agent files and settings will be saved. The Write Filter will then be enabled.

Creating and Deploying Images to XPe Thin Clients

The basics of creating or deploying an image for thin clients running XPe is the same as creating or deploying an image of a standard Windows operating system such as Windows 2000 or XP. The one exception, however, is that the Enhanced Write Filter must be turned off before a Deployment Job can configure a thin client after it has received an Altiris image. When Deployment Solutions is installed, several sample Deployment Jobs are included. 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 Console’s Job pane under the Samples > XP Embedded folder or HP Thin Clients

For example, to create a new Deployment Job that will create an image of an XPe thin client, complete the following steps. These steps assume that you have configured and are using PXE to help in the creation of the images. If needed see the First section of this article. If you are not using PXE, then it is assumed that Embedded BootWorks has been installed on the thin clients.

  1. From the Deployment Console locate and select (highlight) the Samples > HP Thin Clients > 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.
  4. Select this Job. The Tasks it contains will be displayed in the details of the console (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 Deployment Database and the image will be saved in a subfolder of the Deployment System Access Point named Images. If you need to change the name or path, double click on the Create Disk Image Task and enter the new information.
  6. You can now use the drag-and-drop technique to assign and schedule the Job to the desired thin client. In this Job, you will notice that there are two Run Script Tasks used, one to disable the Enhanced Write Filter and one to enable it. You will not need to change these, 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 Filter Disable the Enhanced Write Filter.

Deploying XPe Images

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 very small RAW formatted flash partition on the client. Due to current limitations of the Enhanced Write Filter, this partition cannot be restored unless the flash is the same size as the flash from which the image was created. For example, an image that was created from a 192 MB flash should only be restored to systems with a 192 MB flash. With Deployment Solution 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 restored using the Hewlett Packard Imaging Utility (IBR).

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

  1. From the Deployment Console locate and select (highlight) the Samples > 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.
  4. Select this Job. The Tasks it contains will be displayed in the details area of the console (upper right-hand corner).
  5. This Job can be used as it is (without modification) as long as the Deploy Image Task’s path and file name matches the name and path where the XPe image resides. If you used the default settings from the Create Disk Image Job then these are the same. If you need to change the path or name, double-click on the Deploy Image Task and make the needed changes.
  6. You can now use the drag-and-drop technique to assign and schedule the Job to the desired thin client.

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

Installing New Thin Client images from HP

From time to time HP may release a newer images of the XPe operating system to upgrade your thin clients to a newer version. These images are not Altiris images and therefore cannot be deployed using Altiris’ RapiDeploy imaging software. However, a Deployment Solution Job can be created that can deploy the HP image. This Job will utilize Hewlett Packard’s imaging utility (commonly referred to as the IBR utility) to install the image. To customize and deploy a new thin client image from HP, the following general steps need to be completed:

  1. Download the appropriate image from HP. These are usually stored in the form of a SoftPaq (see http://www.hp.com/products/thinclientsoftware)
  2. Unpack the new thin client image and tools for deployment as delivered from HP.
  3. Create a Deployment Job to deploy the HP image.
  4. Deploy the IBR job to units to be updated. This updates the thin clients with the new version of the image from HP.

Deploying Images released by HP Deployment Solution 6.1 builds and below. Deployment Solution 6.5 and 6.8 Jobs are included.

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

  1. Double-click on the Softpaq you downloaded containing the new HP image and deployment tools.
  2. When prompted, click Deployment.
  3. When prompted, select the destination directory for the imaging tools and image. 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 this process is complete, there will be three new files in the specified folder:
    • IBR.exe: HP’s image restoration utility
    • FLASH.img: The OS image
    • RECOVERY.pdf: Documentatio
      Ensure that IBR.exe and FLASH.img are stored in the same directory on the server.
  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 thin client 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.
  8. Click Finish. Your Job is now complete.
  9. You can now use the drag-and-drop method to assign and schedule this new Job to the desired thin clients. Change the path and name to meet your environment.

Related Articles:

  • Article 27887, "How can I force all files during the PXE boot process to come from the local Package Server?"
  • Article 19177, "How to install or upgrade the Deployment Agent for Linux ADLAgent"
  • Article 24298, "What is PXE Redirection and how is it used in Deployment Solution 6.5?"
  • Article 21223, "Deployment Solution PXE Overview"
  • Article 18188, "Deployment Solution 6.5 Reference Guide"
  • Article 28986, "Deployment Solution 6.8 Reference Guide"
  • Article 17347, "Creating and setting option 060 on a DHCP server If PXE server is installed on same box"
  • Article 25594, "Clients only boot into Production and only see Local Boot as the menu option Managing HP Thin Clients Running CE.net"
  • Article 1328, "General AClient Troubleshooting Guide"
  • Article 20020, "'Unable to boot to automation' error when imaging thin clients"


Attachments

Source from Archive.txt (2 kBytes)

Legacy ID



1779


Article URL http://www.symantec.com/docs/HOWTO1563


Terms of use for this information are found in Legal Notices