IBM Tivoli Provisioning Manager for OS Deployment, Version 7.1.1.14

Adding matching target models to a WinPE deployment engine

If you have several WinPE deployment engines for the same architecture, you must specify with which targets a given WinPE deployment engine must be used.

About this task

If you have only one WinPE deployment engine per computer architecture, there is no reason to modify the model patterns. Use the default * pattern, to match any target known to the OS deployment server.

Procedure

To add model patterns associated with a deployment engine:

  1. Go to Server > Advanced features > Deployment engines.
  2. To view the details of the deployment engine, perform one of the following options:
    • Double-click a deployment engine.
    • Select a deployment engine, and then select View engine details in the contextual menu.
  3. In the Matching models section, click Add a new model pattern.
  4. Enter the pattern and click OK to save your new pattern. The ? character is used as a wildcard replacing one character.
    Note: If WinPE 3.x deployment engines are already available on the OS deployment server, WinPE 4.x deployment engines are not bound to any model pattern automatically.

Results

When deploying a target, if there are several WinPE deployment engines available, a search is performed in the list of model patterns for all WinPE deployment engines available. The WinPE deployment engine selected has the most restrictive pattern matching the target model being deployed.

If there is no matching pattern, deployment cannot proceed.

Note: In a multiple server architecture, a WinPE deployment engine that is not fully replicated from a parent server is not yet available on the child server.

Example

Consider that you have two WinPE deployment engines, WinPEa and WinPEb. WinPEa has the following patterns: IBM Server *, and lenovo *, while WinPEb has lenovo m/55 *, lenovo T*, and *.

A target with model lenovo T61 is deployed with WinPEb because its model matches the lenovo T* pattern, because it is more restrictive than lenovo *.

A target with model lenovo ThinkCenter A58 is deployed with WinPEa because its model matches the lenovo * pattern, because it is more restrictive than the generic * pattern.

A target with model HP Server is deployed with WinPEb because its model matches only the * pattern.

What to do next

You can check which WinPE deployment engine is used with a given target by looking at the Windows specific info section in Server > OS deployment > Target Monitor > Target details. If you are dissatisfied with the selected WinPE deployment engine, you must adapt the target models for your WinPE deployment engines.



Feedback