Technical Reference

The following sections describe the technical characteristics of the Management Pack, including:

  • Computer attributes

  • Computer groups

  • Notification groups

  • Scripts

  • Rules

  • Events

On This Page

Computer Attributes Computer Attributes
Computer Groups Computer Groups
Notification Groups Notification Groups
Scripts Scripts
Rules Rules
Events Events

Computer Attributes

Table 9 lists the computer attributes included in this Management Pack. All the values for these attributes are automatically populated through ZTI events sent to ZTI event collection servers.

Table 9. Management Pack Computer Attributes

Computer attributes

Description

ZTI Advertisement ID

The SMS advertisement ID that started the operating system deployment process.

ZTI Asset Tag

The System Management BIOS (SMBIOS) asset tag of the computer (available only if Windows Management Instrumentation, or WMI, is included in Windows PE). Some vendors might not populate this value. (Requires SMBIOS 2.0 or higher.)

ZTI Log Path

The UNC path to the ZTI log files the scripts create.

ZTI Mac Address 1

The media access control (MAC) address of the first network interface card (NIC) in the computer.

ZTI Mac Address 2

The MAC address of the second NIC in the computer (if present).

ZTI Mac Address 3

The MAC address of the third NIC in the computer (if present).

ZTI Mac Address 4

The MAC address of the fourth NIC in the computer (if present).

ZTI Mac Address 5

The MAC address of the fifth NIC in the computer (if present).

ZTI Package ID

The SMS package ID for this operating system deployment (OSD00000, if started from an SMS 2003 Operating System Image Installation CD).

ZTI Phase

This is the name of the current phase, as last reported by the scripts. Valid values are:

  • NEWCOMPUTER

  • OLDCOMPUTER

  • VALIDATION

  • STATECAPTURE

  • PREINSTALL

  • POSTINSTALL

  • STATERESTORE

ZTI User Data Directory

The directory on the ZTI User Data Share (below) where user state information that the Microsoft Windows User State Migration Tool (USMT) creates should be stored. (This will be used only if there is not enough space on the local computer or if this is an “OldComputer.”)

ZTI User Data Share

The UNC path where user state information that the USMT created should be stored. (This will only be used if there is not enough space on the local computer or if this is an “OldComputer”.)

ZTI UUID

The SMBIOS Universal Unique Identifier (UUID) value from the computer (populated by the manufacturer; requires SMBIOS 2.1 or higher).

Computer Groups

Table 10 lists the computer groups included in this Management Pack.

Table 10. Management Pack Computer Groups

Computer group

Description

Microsoft SA for BDD Event Collection Servers

This computer group includes all the servers that are repositories for the events the scripts create. These servers are specified by setting the EventShare parameter in the CustomSettings.ini file. Manually add any server specified in the EventShare parameter to this computer group.

Microsoft SA for BDD Client Computers

This group is dynamically updated by the management pack to include all computers being deploying using the SMS OSD Feature Pack and ZTI.

SMS 2003 Central Site Servers

This computer group contains all computers running SMS 2003 that have no parent site and that are managed by MOM 2005. This computer group is typically populated automatically by the MOM discovery process.

Notification Groups

Table 11 lists the notification groups included in this Management Pack.

Table 11. Management Pack Notification Groups

Notification group

Description

BDD Administrators

This group will receive all notifications for new alerts generated for all ZTI and SMS OSD Feature pack warning and error events.

Scripts

Table 12 lists the scripts included in this Management Pack.

Table 12. Management Pack Scripts

Script

Description

BDD Get OSD Status Messages

This script connects to the SMS 2003 WMI provider to retrieve all new status messages related to ZTI and the SMS OSD Feature Pack. Each status message is converted into a MOM event.

BDD Get ZTI Events

This script monitors the event collection shares looking for event files that the ZTI script creates. Each event file is then converted into a MOM event.

BDD Regenerate Hang Events

A managed code response generates hang events but is unable to generate them for the actual hung computer, so this script regenerates the event for the proper computer.

BDD Event Filter

The BDD Get OSD Status Messages and BDD Get ZTI Events scripts generate events in which the computer name is one of the parameters. This script takes that parameter and generates a new MOM event where the event comes from that computer.

Rules

Table 13 lists the rules included in this Management Pack.

Table 13. Management Pack Rules

Rule

Description

Cleanup old computers

This rule is responsible for removing all monitored computers after a specified number of days. This is necessary to minimize the overall impact on the MOM 2005 Operator console.

Collect BDD Events

This rule causes MOM 2005 to retain the parameters that are associated with each event generated as part of this Management Pack. These parameters are used for reporting purposes.

Detect Hung Computers

This rule detects in-progress operating system deployments in which the target computer has not reported any events in more than the specified number of minutes (by default, 30 minutes), as a technician may have to visit these computers to make sure that no problems exist.

Process Regenerated Hang Events

This processes the events generated by the Regenerate Hang Events rule.

Raise Alerts for Hung Computers

This rule will generate an alert for each event generated by the Process Regenerated Hang Events rule (all of which are warnings).

Regenerate Hang Events

The Detect Hung Computers rule generates events in which the hung computer is just a parameter (a limitation in MOM 2005). The script attached to this rule regenerates the events by using the deployed computer’s name.

Collect OSD Status Messages

This rule causes MOM 2005 to retain the parameters that are associated with each event generated as part of this Management Pack. These parameters are used for reporting purposes.

Generate OSD Events

This rule queries the SMS 2003 central primary site server (as configured in the associated computer group) by using WMI to find all new ZTI and SMS OSD Feature Pack–related SMS status messages, generating a MOM event for each one found.

Process OSD Events

This rule process the events generated by the Generate OSD Events rule, recording discovery information, performance counters, and other information.

Raise Alerts for OSD Error Events

This rule generates alerts for any event with an “error” status generated by the Process OSD Events rule.

Raise Alerts for OSD Warning Events

This rule generates alerts for any event with a “warning” status generated by the Process OSD Events rule.

Collect ZTI Event Parameters

This rule causes MOM 2005 to retain the parameters that are associated with each event generated as part of this Management Pack. These parameters are used for reporting purposes.

Generate ZTI Events and Discovery Data

This rule reads the event files written to the ZTI event collection shares, generating a MOM event for each event file found.

Process ZTI Events

This rule processes the events generated by the Generate ZTI Events and Discovery Data rule, recording discovery information, performance counters, and other information.

Raise Alerts for ZTI Error Events

This rule generates alerts for any event with an “error” status generated by the Process ZTI Events rule.

Raise Alerts for ZTI Warning Events

This rule generates alerts for any event with a “warning” status generated by the Process ZTI Events rule.

Events

Table 14 lists the SMS client component events that the Management Pack references (event IDs 10002–10099). The Management Pack processes only SMS OSD Feature Pack–related status messages; status messages from other software packages or advertisements will be ignored.

Table 14. SMS Client Component Events Referenced by the Management Pack

Event

Event

Description

ID:
Component:
Type:
Text:

10002
SMS Client
Informational
A new advertisement %1 was received

The SMS client received the new SMS OSD Feature Pack advertisement and will run it based on the advertisement’s schedule.

ID:
Component:
Type:
Text:

10005
SMS Client
Informational
Program started for advertisement %1

The SMS client successfully started running the SMS OSD Feature Pack program associated with the advertisement.

ID:
Component:
Type:
Text:

10006
SMS Client
Error
Program failed, return code = %11

The program being executed as part of the SMS OSD Feature Pack advertisement failed to run. At this point, the SMS OSD Feature Pack process has not started. See the SMS OSD Feature Pack logs for more information about the cause of this error.

ID:
Component:
Type:
Text:

10007
SMS Client
Error
Program failed with status MIF

The program being executed as part of the SMS OSD Feature Pack advertisement failed to run. At this point, the SMS OSD Feature Pack process has not started. See the SMS OSD Feature Pack logs for more information about the cause of this error.

ID:
Component:
Type:
Text:

10008
SMS Client
Informational
Program successful

The program associated with the SMS OSD Feature Pack advertisement finished successfully. This does not mean that the SMS OSD Feature Pack process has finished successfully. Instead, it means that the SMS OSD Feature Pack has successfully installed and started the OSDAgent service that will drive the remainder of the process.

ID:
Component:
Type:
Text:

10009
SMS Client
Informational
Program successful

The program associated with the SMS OSD Feature Pack advertisement finished successfully. This does not mean that the SMS OSD Feature Pack process has finished successfully. Instead, it means that the SMS OSD Feature Pack has successfully installed and started the OSDAgent service that will drive the remainder of the process.

ID:
Component:
Type:
Text:

10018
SMS Client
Warning
Advertisement rejected due to platform restrictions

The SMS OSD Feature Pack advertisement was received by a computer, but that computer rejected it because it was not running the right operating system platform. This event will typically only occur on Microsoft Windows 98 computers, as SMS OSD Feature Pack advertisements support Microsoft Windows 2000 Professional and later.

ID:
Component:
Type:
Text:

10019
SMS Client
Warning
Advertisement rejected because it is expired

The SMS OSD Feature Pack advertisement was received by the computer, but it will not run because the expiration date configured on that advertisement has already passed.

ID:
Component:
Type:
Text:

10020
SMS Client
Informational
Program will not be run due to a slow network connection

The SMS OSD Feature Pack advertisement is configured not to run the program over a slow network connection, but a slow network connection was detected.

ID:
Component:
Type:
Text:

10023
SMS Client
Informational
Content download has started

The SMS OSD Feature Pack advertisement has been configured to use “Download and execute” and has started downloading the package content. The package cannot begin executing until the download is complete.

ID:
Component:
Type:
Text:

10024
SMS Client
Informational
Content download has completed

The contents of the SMS OSD Feature Pack package have been completely downloaded so that program can run as soon as the advertisement start time arrives.

ID:
Component:
Type:
Text:

10030
SMS Client
Error
Content hash mismatch

The contents of the SMS OSD Feature Pack package were downloaded, but the content hash (checksum) of the local content did not match the server content. This means that the local content is corrupt and unusable.

ID:
Component:
Type:
Text:

10031
SMS Client
Informational
Content download cancelled

The SMS client cancelled the SMS OSD Feature Pack package download.

ID:
Component:
Type:
Text:

10034
SMS Client
Informational
Program cancelled by user request

The SMS client cancelled the SMS OSD Feature Pack package download at the user’s request.

ID:
Component:
Type:
Text:

10035
SMS Client
Informational
Waiting for package content

The SMS OSD Feature Pack package cannot run, because the SMS client has not yet located or obtained the package content. If the package is configured for “Download and execute,” it will take some time for this download to complete. If the package is configured to run from a distribution point, this status message is still generated to indicate that it is looking for a distribution point, but one should be found quickly, enabling the package execution to continue.

ID:
Component:
Type:
Text:

10037
SMS Client
Informational
Waiting for another program to complete

The SMS OSD Feature Pack package cannot run, because the SMS client is busy running something else. As soon as that advertisement is complete, the SMS OSD Feature Pack package should run.

ID:
Component:
Type:
Text:

10040
SMS Client
Warning
Program will not be re-run due to program settings

The SMS client will not re-run the SMS OSD Feature Pack advertisement, because the same package/program combination has already successfully run on the computer.

ID:
Component:
Type:
Text:

10041
SMS Client
Warning
Program will not be re-run due to program settings

The SMS client will not re-run the SMS OSD Feature Pack advertisement, because the same package/program combination has already successfully run on the computer.

ID:
Component:
Type:
Text:

10042
SMS Client
Warning
Program will not be re-run due to program settings

The SMS client will not re-run the SMS OSD Feature Pack advertisement, because the same package/program combination has already successfully run on the computer.

ID:
Component:
Type:
Text:

10043
SMS Client
Warning
Program will not be re-run due to program settings

The SMS client will not re-run the SMS OSD Feature Pack advertisement, because the same package/program combination has already successfully run on the computer.

ID:
Component:
Type:
Text:

10045
SMS Client
Warning
Not enough space in cache

The SMS OSD Feature Pack advertisement has been configured for “Download and Execute,” but there is not enough space in the SMS client’s local disk cache to hold the package contents. The cache must be increased before the package can download and run.

ID:
Component:
Type:
Text:

10050
SMS Client
Error
Not enough space in cache

The SMS OSD Feature Pack advertisement has been configured for “Download and Execute,” but there is not enough space in the SMS client’s local disk cache to hold the package contents. The cache must be increased before the package can download and run.

ID:
Component:
Type:
Text:

10051
SMS Client
Error
Content cannot be located, SMS client is giving up

The SMS client attempted to locate a distribution point containing the SMS OSD Feature Pack package files but was unable to do so after several tries, so it gave up.

ID:
Component:
Type:
Text:

10053
SMS Client
Error
Content download failed

The SMS client experienced a problem while downloading the SMS OSD Feature Pack package files from an SMS distribution point. No more attempts will be made.

ID:
Component:
Type:
Text:

10054
SMS Client
Error
Not enough space in cache

The SMS OSD Feature Pack advertisement has been configured for “Download and Execute,” but there is not enough space in the SMS client’s local disk cache to hold the package contents. The cache must be increased before the package can download and run.

ID:
Component:
Type:
Text:

10057
SMS Client
Error
Not enough space in cache

The SMS OSD Feature Pack advertisement has been configured for “Download and Execute,” but there is not enough space in the SMS client’s local disk cache to hold the package contents. The cache must be increased before the package can download and run.

ID:
Component:
Type:
Text:

10058
SMS Client
Error
Not enough space in cache

The SMS OSD Feature Pack advertisement has been configured for “Download and Execute,” but there is not enough space in the SMS client’s local disk cache to hold the package contents. The cache must be increased before the package can download and run.

ID:
Component:
Type:
Text:

10060
SMS Client
Warning
Content download failed, will retry

The SMS client experienced a problem while downloading the SMS OSD Feature Pack package files from an SMS distribution point. More attempts will be made to complete the download.

ID:
Component:
Type:
Text:

10061
SMS Client
Warning
Content download failed, will retry

The SMS client experienced a problem while downloading the SMS OSD Feature Pack package files from an SMS distribution point. More attempts will be made to complete the download.

ID:
Component:
Type:
Text:

10062
SMS Client
Warning
Content download failed, will retry

The SMS client experienced a problem while downloading the SMS OSD Feature Pack package files from an SMS distribution point. More attempts will be made to complete the download.

Table 15 lists the OSD Agent component events that are referenced by the Management Pack (event IDs 11100—11199).

Table 15. OSD Agent Component Events Referenced by the Management Pack

Event

Event

Description

ID:
Component:
Type:
Text:

11100
OSD Agent
Informational
OSD action '%1' started

The OSD agent generates this event for each action started during the OS deployment process.

ID:
Component:
Type:
Text:

11101
OSD Agent
Error
OSD action '%1' failed with rc = %1

The OSD agent detected that an action failed with a non-zero return code. This is a terminal error prior to the Install phase; after the install phase, execution will continue. (The management pack will raise an alert for each action failure, regardless of the phase.)

ID:
Component:
Type:
Text:

11102
OSD Agent
Informational
OSD deployment successfully completed

The OSD agent successfully completed the OSD image deployment process. The new OS is fully installed and ready to use.

ID:
Component:
Type:
Text:

11103
OSD Agent
Error
OSD did not receive a response from the management point

The OSD agent attempted to contact an SMS management point to locate the closest SMS distribution point containing the specified package, but the management point did not respond. This causes the OS deployment process to fail.

ID:
Component:
Type:
Text:

11104
OSD Agent
Error
OSD found no distribution points available at the site

The OSD agent successfully contacted an SMS management point, but that management point reported that there were no suitable SMS distribution points available given the computer’s current network location. This causes the OS deployment process to fail. (This may mean that the site is configured to use Active Directory site boundaries and the update associated with Microsoft Knowledge Base article 888311, “Deploying an operating system by using the Operating System Deployment Feature Pack fails when Active Directory sites are used as site boundaries in SMS 2003,” has not been installed.)

ID:
Component:
Type:
Text:

11105
OSD Agent
Error
OSD was unable to connect to a distribution point

The OSD agent successfully obtained the name of an SMS distribution point from the SMS management point but was unable to connect to that distribution point. This causes the operating system deployment process to fail. (This may mean that the server is down, that there are firewalls or IP Security [IPSec] configurations interfering, and so on.)

ID:
Component:
Type:
Text:

11106
OSD Agent
Informational
OSD Validation phase started

The OSD agent successfully started the validation phase, the first phase in the operating system deployment process.

ID:
Component:
Type:
Text:

11107
OSD Agent
Informational
OSD State Capture phase started

The OSD agent successfully started the state capture phase (running in the original, or “old,” operating system), the second phase in the operating system deployment process. This phase typically runs the USMT to capture user settings and files.

ID:
Component:
Type:
Text:

11108
OSD Agent
Informational
OSD Preinstall phase started

The OSD agent successfully started the preinstall phase. For an operating system refresh, Windows PE is placed on the hard disk, and the computer is restarted to continue the process. For a new computer, the pre-installation phase is initiated from the Windows PE image installation CD.

ID:
Component:
Type:
Text:

11109
OSD Agent
Informational
OSD Install phase started

The OSD agent successfully started the installation phase (running in Windows PE). This phase cleans the old operating system from drive C (if there is an existing operating system) and extracts the contents of the new operating system Windows Image Format (WIM) image, placing it on the drive.

ID:
Component:
Type:
Text:

11110
OSD Agent
Informational
OSD Postinstall phase started

The OSD agent successfully started the post-installation phase (running in Windows PE). During this phase, the new operating system can be adjusted or modified before it runs for the first time (for example, editing the Sysprep.inf configuration file or adding drivers).

ID:
Component:
Type:
Text:

11111
OSD Agent
Informational
OSD State Restore phase started

The OSD agent successfully started the state restore phase (running in the “new” operating system). During this phase, the user state information captured previously is restore and any needed applications are installed.

Table 16 lists the ZTI Script component events that the Management Pack references (event IDs 41000–41099).

Table 16. ZTI Script Component Events Referenced by the Management Pack

Event    

Event

Description

ID:
Component:
Type:
Text:

41000
ZTI Script
Informational
ZTI script started processing for %1 phase.

The script was started as part of the specified phase (%1).

ID:
Component:
Type:
Text:

41001
ZTI Script
Informational
ZTI %1 processing completed successfully

The script processing for the specified phase (%1) was successfully completed.

ID:
Component:
Type:
Text:

41002
ZTI Script
Error
ZTI ERROR - Unhanded error returned from ZTI Process function: %2 (%3)

An error occurred while running the scripts. This situation is not normal; further investigation is required to identify the cause of the error.

ID:
Component:
Type:
Text:

41003
ZTI Script
Informational
ZTI Heartbeat: command has been running for %1 minutes (process ID %2)

The scripts run some commands that may take a long time to complete (for example, the USMT state capture). The ZTI script generates this event to indicate that it is still alive and monitoring the specified process.

ID:
Component:
Type:
Text:

41004
ZTI Script
Informational
ZTI Beginning user state estimate/capture

The scripts are going to start the USMT state capture process; waiting for it to finish.

ID:
Component:
Type:
Text:

41005
ZTI Script
Informational
ZTI Scanstate was successful

The USMT state capture process was successful.

ID:
Component:
Type:
Text:

41006
ZTI Script
Warning/Error
ZTI ERROR - Unable to run Scanstate, Error = %1 (%2)

The scripts encountered an error while running the USMT Scanstate command. See the usmtcapt.log file for more information.

ID:
Component:
Type:
Text:

41007
ZTI Script
Informational
ZTI Beginning user state restore

The scripts are going to start the USMT state restore process.

ID:
Component:
Type:
Text:

41008
ZTI Script
Informational
ZTI User state restored successfully

The USMT state restore process finished successfully.

ID:
Component:
Type:
Text:

41009
ZTI Script
Warning
ZTI ERROR - No user state migration store was found, impossible to restore user state

The scripts were unable to locate a user state store directory, so no user state will be restored for this computer. This is normal for new computers (where there is no “old” computer to replace) but not for existing computers.

ID:
Component:
Type:

Text:

41010
ZTI Script
Informational, Warning, or Error
ZTI USMT <USMTType> reported <ErrorCount> errors and <WarningCount> warnings

The scripts automatically scan the USMT progress logs for errors and warnings. USMTType can be ESTIMATE, SCANSTATE, or LOADSTATE.

If the error count is greater than 0, this event is an Error type. If the warning count is greater than 0 with no errors, the event is Warning type. Otherwise, the event is an Informational type.

ID:
Component:
Type:
Text:

41011
ZTI Script
Informational
ZTI Successfully installed %1:%2

The scripts successfully installed the specified SMS package and program combination.

ID:
Component:
Type:
Text:

41012
ZTI Script
Error
ZTI ERROR - Unable to execute command

The scripts were unable to install the specified SMS package and program combination because of an error executing the command.

ID:
Component:
Type:
Text:

41013
ZTI Script
Error
ZTI error opening SQL connection: %1

The scripts were unable to connect to the specified SQL Server database.

Download

Get the Microsoft Solution Accelerator for Business Desktop Deployment 2007

Update Notifications

Sign up to learn about updates and new releases

Feedback

Send us your comments or suggestions