CustomSettings.ini based on task Sequences MDT 8456

Question

Dear all,

I'm trying to add different priorities in my customsettings.ini based on the task sequences I have, but MDT only process the first in line and skipping the last one.
Both LAB and 20H2 get the same results nomatter how I change the values or changing the settings in the task sequences for the OS deployments.

In my customsettings.ini I have the following, and it's the SkipLocalAccount I want to differ for the two OS deployment, but it doesn't work.

[Settings]
Priority=TaskSequenceID,LAB,20H2
Properties=MakeAlias, ModelAlias, OSDPrefix, TaskSequenceID

[20H2]
SkipLocalAccount=No
SomeMoreStuff

[LAB]
SkipLocalAccount=YES
SomeMoreStuff

I have tried the following:

• Tried with two Gather Local Only, one with default setting in task sequences and then added CustomSettings.ini and had it process the rules.
• Tried with two Gather Local Only, one with default setting and a custom LabSetting.ini file and had it process the rule.
• Tried with one Gather Local Only, but with only Labsetting.ini and had it process the rule.
• Also tried to add the .ini like this: %SCRIPTROOT%\LabSettings.ini or just have in the same folder as CustomSettings.ini.
• With having two new ini files like LabSettings.ini and OSdeployment.ini in the respective task sequences, I tried removed everything in CustomSettings.ini.
• I tried to add Set Task Sequence Variable: SkipLocalAccount with Value Yes and same thing for the other OSdeployment but with No instead.
• Tried to remove the priority in the CustomSettings.ini and kept [20H2] [LAB]

All of the above back and forth didn't work.

I have read about that DeployWiz_SelectTS.vbs needs to be modified to be able to use TaskSequenceID in the customsettings.ini and found this post:
https://social.technet.microsoft.com/Forums/de-DE/e3878cd0-37f6-45b4-bbe4-a49fecddcbde/mdt-2013-different-settings-per-task-sequence

I have the same DeployWiz_Select.TS.vbs from the blogpost in my MDT 6.3.8443.1000 but I'm running MDT version 6.3.8456.1000 - This didn't do the trick.

Anyone who knows how to set this up for it work properly

Thaaaank you!

Answer 1

With only having like this, MDT choose LAB before 20H2 and in task sequence I only have one Gather Local Only with default setting "Gather only local data (do not process rules)"

[Settings]
Priority=TaskSequenceID

[20H2]
OSInstall=Yes
SkipCapture=YES
SkipAdminPassword=YES
SkipProductKey=YES
SkipComputerBackup=YES
SkipBitLocker=YES
SkipLocaleSelection=YES
SkipTimeZone=YES
SkipDomainMembership=YES
SkipSummary=YES
SkipFinalSummary=YES
SkipComputerName=YES
SkipUserData=YES
DoNotCreateExtraPartition=YES
HideShell=Yes
SkipRoles=YES
SkipLocalAccount=No

[LAB]
OSInstall=Yes
SkipCapture=NO
SkipAdminPassword=NO
SkipProductKey=YES
SkipComputerBackup=YES
SkipBitLocker=YES
SkipLocaleSelection=YES
SkipTimeZone=NO
SkipDomainMembership=YES
SkipSummary=YES
SkipFinalSummary=YES
SkipComputerName=YES
SkipUserData=YES
DoNotCreateExtraPartition=YES
HideShell=Yes
SkipRoles=YES
SkipLocalAccount=YES

Answer 2

So I found out that it seems to work but with with a bug or update problem?

If I choose the task sequence that contains the OS deployment with [LAB] it does not ask for create local account (which is correct).
However if I go back and choose the task sequence that contains [20H2] it does not ask for create local account (update problem? which is wrong)

If I start over but I start with [20H2] it asks for create local account.
If I go back and choose [LAB] it asks for create local account (which is wrong).

The default DeployWiz_SelectTS.vbs seems not to work very well, create local account appears no matter how I start.
But the older versions of DeployWiz_SelectTS.vbs from the first post seems to work better as long as when you're sure of which TS to choose.

Answer 3

Hi, @lupinlicious

Thank you for posting in Microsoft Q&A forum.

The customsettings.ini is processed BEFORE we choose our tasksequence.
We may need two Gather steps, the first Gather step simply uses CustomSettings.ini (meaning you do not change default configuration), the second Gather step processes your Task Sequence specific CustomSettings.ini.

You may check Anton Romanyuk's reply in below thread to see if it helps:
https://social.technet.microsoft.com/Forums/en-US/d5ee588f-4e8d-4412-8f3e-77d39518c757/mdt-2013-6384431-tasksequence-by-tasksequenceid-is-not-working?forum=mdt

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 4

Hello @AllenLiu-MSFT and thank you for your reply!

I saw that post earlier you're referring to, and the MDT versions differ between 2013.6.3.8443.1, meanwhile I'm using 6.3.8456.1000
Difficult to say if files have been modified, deleted or broken between these two releases.

However he confirmed it was working first after the following values was deleted MachineObjectOU=, OSDComputerName= and SkipComputerName=.
I have not tried to do the same, but in the very end another user seems to have the same issue, two years later..

Best regards

Answer 5

On MDT 2013 for the Priority=TaskSequenceID to be taken into account, you must modify the DeployWiz_SelectTS.vbs file

1. Backup the DeployWiz_SelectTS.vbs file located in DeploymentShare\Scripts
2. Open the file with Notepad / Notepad++ ….
3. Apply the changes below:

Search for :

Function ValidateTSList

Dim oTS

Add after :

Dim sCmd
Dim oItem
Set oShell = createObject("Wscript.shell")

Go to the end.
Add before [End Function] add:

sCmd = "wscript.exe """ & oUtility.ScriptDir & "\ZTIGather.wsf"""
oItem = oShell.Run(sCmd, , true)

4. Save file
5. Edit the CustomSetting.ini file

source: https://rdr-it.com/en/mdt-customize-sequence-based-deployment-with-tasksequenceid/