none
MDT 2013 to update 2 - rules not applying RRS feed

  • Question

  • OK.  Historically speaking, we did an update from MDT2013/ADK8.1/MDS Lite Touch to MDT2013U2/ADK10/MDS  LiteTouch But the instructions we used are not available.  Everything ran fine until i added a task sequence for win10 and the associated custom settings and did a Update DS and choose 'replace boot images'.  As soon as those images were added, things went downhill.  In an attempt to isolate the cause, I tried to remove WDS at which time my server fell down and couldn't get back up.

    So, after failing to restore the server from backup, we rebuilt it and restored the data.  I then installed 2013/8.1/MDS and performed the upgrade following these instructions http://deploymentresearch.com/Research/Post/504/A-Geeks-Guide-for-upgrading-MDT-2013-to-MDT-2013-Update-1

    Although i didn't use the powershell, i just started with a reboot and then put reboots in between everything, remove adk8.1, reboot, install adk10, reboot, install MDT2013U2, ...

    Then i created a new TS and using the original as a guide, matched it up to the old.  I can provide an image, but i'm not comfortable exporting the xml

    I am back to a point where i have the exact same problem as before.  Basically, the [DEFAULT] custom settings are being applied, however the ones specified for the task sequence are not.  I haven't even gotten into the task sequence itself, i'm still doing the steps following selecting the task sequence.  I'm enclosing the relevant customsettings in a code block below but if files would help, i have a cleaned up copy of the full ini file, an image of my task sequence and an image of the screen of my deployment in action.

    I'm basically wondering if, for instance, some of the name value pairs have been deprecated or if there's a problem with duplication now that i'm in update 2 or..well...I have no idea, all i know is that the default rules appear to be working, but the specific task sequence ones aren't being applied.

    [Settings] Priority=TaskSequenceID, Default Properties=SavedJoinDomain [Default] WSUSServer=http://wsusServer:8530 UserID=serviceAccount UserDomain=domainName.com UserPassword=Password DomainAdminDomain=domainName.com DomainAdmin=serviceAccount DomainAdminPassword=Password SLShareDynamicLogging=\\deployServer\deploymentShare\ClientLogs\%COMPUTERNAME% SLShare=\\deployServer\deploymentShare\ClientLogs _SMSTSOrgName=My Org Name BitsPerPel=32 VRefresh=60 XResolution=1 YResolution=1 SkipTimeZone=YES TimeZone=035 TimeZoneName=Eastern Standard Time SkipLocaleSelection=YES KeyboardLocale=en-us UserLocale=en-us UILanguage=en-us SkipProductKey=YES SkipBitLocker=YES SkipComputerBackup=YES EventService=http://deployServer:9800 ... [22] UserID=serviceAccount UserDomain=domainName.com UserPassword=Password GPOPackPath=baseline SkipDomainMembership=YES SkipCapture=NO SkipAdminPassword=YES AdminPassword=Password JoinDomain=domainName.com DomainAdminDomain=domainName.com DomainAdmin=serviceAccount DomainAdminPassword=Password SkipFinalSummary=YES FinishAction=RESTART

    ...



    Tuesday, April 12, 2016 8:46 PM

Answers

  • The task sequences did not have that setting, however adding and updating the DS made no change. The rules for 22 aren't being applied when TS 22 is selected.  

    I found a very old article here that has my exact problem duplicated.  If i put the TS name on the priority line, it runs, but without it, it doesn't run.:

    https://social.technet.microsoft.com/Forums/en-US/320aafee-07d2-4b96-9138-a902fec7edf5/mdt-2012-custom-rules-by-tasksequenceid-not-working-now?forum=mdt

    I tested it by placing 22 on the priority line between TAskSeqID and Default.  Suddenly more rules were being applied.

    So i opened DeployWiz_SelectTS and i found that "ZTIGather.wsf" isn't in it anymore.

    This actually solved the problem.  

    Is it still appropriate? I would think that a bug this old would be fixed by now, even if it was fixed another way.


    • Marked as answer by mdt109 Thursday, April 14, 2016 7:19 PM
    • Edited by mdt109 Thursday, April 14, 2016 7:21 PM
    Thursday, April 14, 2016 6:58 PM

All replies

  • I believe you need to change the gather process and have it point to customsettings.ini in order to process settings per task sequence. Normally customsettings is processed BEFORE you select a task sequence.

    If this post is helpful please vote it as Helpful or click Mark for answer.

    Tuesday, April 12, 2016 9:50 PM
  • The task sequences did not have that setting, however adding and updating the DS made no change. The rules for 22 aren't being applied when TS 22 is selected.  

    I found a very old article here that has my exact problem duplicated.  If i put the TS name on the priority line, it runs, but without it, it doesn't run.:

    https://social.technet.microsoft.com/Forums/en-US/320aafee-07d2-4b96-9138-a902fec7edf5/mdt-2012-custom-rules-by-tasksequenceid-not-working-now?forum=mdt

    I tested it by placing 22 on the priority line between TAskSeqID and Default.  Suddenly more rules were being applied.

    So i opened DeployWiz_SelectTS and i found that "ZTIGather.wsf" isn't in it anymore.

    This actually solved the problem.  

    Is it still appropriate? I would think that a bug this old would be fixed by now, even if it was fixed another way.


    • Marked as answer by mdt109 Thursday, April 14, 2016 7:19 PM
    • Edited by mdt109 Thursday, April 14, 2016 7:21 PM
    Thursday, April 14, 2016 6:58 PM
  • By tasksequenceID rules not applying isn't seen as a bug. There might be feedback on connect you could thumbs up.

    Many questions such as where do I find logs and what logs are interesting are found in: MDT TechNet Forum - FAQ & Getting Started Guide Please take the time to read it.

    Thursday, April 14, 2016 7:51 PM
    Moderator
  • Hi, mdt109,

    Yes, looks like this feature is not available out of the box. In order to get working the Priority to TaskSequenceID in CustomSettings.ini, you have to do a little patching in the DeployWiz_SelectTS.vbs script, adding several lines in order to re-run ZTIGather.wsf so the settings are re-loaded after selecting the Task Sequence.

    For MDT 2013 Update 2, in "Function ValidateTSList", after the line that says "Dim oTaskOsUpgrade" add the following:

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

    For MDT build 8443 you will have to add an extra line; in "Function ValidateTSList", after the line that says "Dim oTS" add the following:

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

    In both versions, scroll down to the bottom and just before "End Function" add the following:

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

    Kudos on this workaround goes to Jeff Irvine in http://techmological.com/mdt-2013-part-1/ and Ward Vissers in http://www.wardvissers.nl/2016/12/29/mdt-build-8443-automatically-move-computers-to-the-right-ou/

    Hope this will be helpful for you too :-)

    Best regards,
    -- Javier Llorente



    • Edited by Javier Llorente Wednesday, March 29, 2017 10:25 AM Grammarly Add-in messing the text
    • Proposed as answer by Ty GlanderModerator Wednesday, March 29, 2017 7:55 PM
    Wednesday, March 29, 2017 10:24 AM
  • Hi, mdt109,

    Yes, looks like this feature is not available out of the box. In order to get working the Priority to TaskSequenceID in CustomSettings.ini, you have to do a little patching in the DeployWiz_SelectTS.vbs script, adding several lines in order to re-run ZTIGather.wsf so the settings are re-loaded after selecting the Task Sequence.

    For MDT 2013 Update 2, in "Function ValidateTSList", after the line that says "Dim oTaskOsUpgrade" add the following:

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

    For MDT build 8443 you will have to add an extra line; in "Function ValidateTSList", after the line that says "Dim oTS" add the following:

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

    In both versions, scroll down to the bottom and just before "End Function" add the following:

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

    Kudos on this workaround goes to Jeff Irvine in http://techmological.com/mdt-2013-part-1/ and Ward Vissers in http://www.wardvissers.nl/2016/12/29/mdt-build-8443-automatically-move-computers-to-the-right-ou/

    Hope this will be helpful for you too :-)

    Best regards,
    -- Javier Llorente



    This is still the only workaround that works for me, even with the latest ADK10 and MDT v.8456

    DeployWiz_SelectTS.vbs gets less and less code inside for each new release. 


    • Edited by freeAppz Tuesday, February 5, 2019 1:14 PM added text
    Tuesday, February 5, 2019 12:50 PM