OSDResults doesn’t display applications installed by a UDI task sequence in Configuration Manager

Applies to: System Center Configuration Manager (current branch - version 1902)System Center Configuration Manager (current branch - version 1810)System Center Configuration Manager (current branch - version 1806)

Symptoms


You create a Microsoft Deployment Toolkit (MDT) integrated User-Driven Installation (UDI) task sequence in System Center Configuration Manager current branch version 1806 or a later version. In the task sequence, users can select the applications to install at deployment time. After the task sequence runs, OSDResults doesn’t display the packages or applications that were installed by the UDI Wizard.

When this issue occurs, the following error messages are logged in SMSTS.log:

Cause


This issue occurs under one of the following conditions:

  • In the task sequence, the dynamic Install Application step runs before the dynamic Install Package step.

    The dynamic Install Package step must run before the dynamic Install Application step.
  • In the task sequence, a static Install Package or static Install Application step runs before the dynamic Install Package and dynamic Install Application steps.

    All static Install Package and static Install Application steps must run after the dynamic Install Package and dynamic Install Application steps.

When the tasks in the task sequence aren't run in the proper order, the  OSD_BaseVariables.vbs MDT script can't populate the necessary registry values. The script runs during the Parse Base Variables action and is responsible for populating registry values that are used by OSDResults. The script parses the task sequence XML  in a predefined order looking for the base variables in the dynamic Install Package and dynamic Install Application steps. When either of the conditions occur, OSD_BaseVariables.vbs can’t read the base variables correctly. 

Note

  • In the MDT UDI task sequence, the dynamic Install Package step is displayed as Install Software.
  • A dynamic Install Package or dynamic Install Application step installs packages or applications by using a dynamic variable list. Otherwise, we call it a static Install Package or static Install Application step.

 

Resolution


To fix the issue, in the task sequence:

  1. Make sure that the dynamic Install Package (displayed as Install Software) step is placed before the dynamic Install Application step.
  2. Make sure that all static Install Package and static Install Application steps are placed after the dynamic Install Package (displayed as Install Software) and dynamic Install Application steps.

Note:

  • By default, the dynamic Install Application step is under the Install Applications group. When you change the order of the steps, don't remove the dynamic Install Application step from the group, and make sure that the original order of steps in the group is preserved.
  • Also, make sure that the Install Applications group is placed after the dynamic Install Package (displayed as Install Software) step, but before any static Install Package or static Install Application steps.