Bug: Applications are not Selected Properly When Set through CustomSettings.ini or through the Database

A bug has been discovered in Microsoft Deployment where the Application List is not populating correctly if the Applications are pre-defined in the customsettings.ini or in the admin database. 

To work around this bug a small change is needed in the wizard.hta.  Line 731 in the script currently reads like this:

ElseIf oEnvironment.Item(strName & "1") <> "" then

However to fix it, modify it to read like the following:

ElseIf oEnvironment.Item(strName & "001") <> ""  then

Thanks to all of you who have brought this to our attention!

Comments (4)
  1. Anonymous says:

    I tried the modifying the Wizard.hta according to the post, but the app specified in CustomSettings.ini still isn’t selected in the applications list

  2. Anonymous says:

    I’ve been doing more BDD/Microsoft Deployment work lately with various DDPS engagements and there are two fairly well known bugs in the current Microsoft Deployment toolkit that are easily fixed, but becomes tedious to fix on every install. Rather th

  3. Anonymous says:

    i jumped the gun slightly.  this does work in a a Refresh scenario, but it does not work in a NewComputer scenario.

  4. Anonymous says:

    This does not work in the NEWCOMPUTER scenario if you specify a BuildID in CustomSettings.ini and set SkipBuild=YES.  If you select a TaskSequence from the list, it does check the apps, but not if you skip the Task Sequence selection screen in the wizard.

    I have my CS set to select the task sequence based on the model of the machine.

Comments are closed.

Skip to main content