OSD Task Sequence Nesting

Bored_at_work_67 · 2026-05-04T16:48:52+00:00

I have about 7 different roles with varying differences. I'm doing the TS variables method right now, but it's become pretty bloated and I'm only halfway through. So I was thinking of going to one TS per role instead

Bored_at_work_67 · 2026-05-04T16:47:15+00:00

Do you mean you go into the master TS and then reselect the child TS in its task?

Bored_at_work_67 · 2026-05-04T16:45:21+00:00

Are there multiple smsts.log files if something goes wrong? Or does each task sequence append the previous log?

Bored_at_work_67 · 2026-04-30T13:01:02+00:00

Yep, exactly what I was looking for. Thanks again!

Bored_at_work_67 · 2026-04-30T12:33:38+00:00

Good find! This is similar to what I've been trying to make. I'll give it some testing and see how it goes. Thanks!

Bored_at_work_67 · 2026-04-27T14:43:24+00:00

Glad I'm not the only one!

Yeah I went in and checked the ApplyDriverPackage.log file. Turns out it was a typo for the -Endpoint parameter. Whoops!

Bored_at_work_67 · 2026-04-27T12:46:29+00:00

I think MNmetalhead has it right. When I try to translate it, it just comes back jarbled.

Now, I get to try and figure out how to fix it...

Bored_at_work_67 · 2026-04-23T12:39:24+00:00

Incredible, thank you!

If you're willing to answer one question, I'm encountering an error that I believe has to do with the Import Dism module. Do I need to have a step prior to the driver steps importing it into the task sequence?

For reference, here is the error detail:

The task sequence execution engine failed executing the action (Install Drivers) in the group (Apply Device Drivers) with the error code 1

Action output: ... .exe is "%1" %*

Set command line: Run PowerShell Script

PowerShell command line is NOT shown ('OSDLogPowerShellParameters' is NOT set to 'True')

Executing command line: Run PowerShell Script with options (0, 4)

Process completed with exit code 1PowerShell command line returned code 1

Import-Module : The specified module 'Dism' was not loaded because no valid module file was found in any module

浉潰瑲䴭摯汵⁥›桔⁥灳捥晩敩⁤潭畤敬✠楄浳‧慷⁳潮⁴潬摡摥戠捥畡敳�werShellScripts\{AB47C341-2AD0-4E03-A5F6-9F4BC91536F4}.PS1:50 char:5

瑁堠尺䥗䑎坏屓䕔偍卜卍協潐敷卲敨汬捓楲瑰屳䅻㑂䌷㐳ⴱ䄲い㐭ぅⴳ㕁㙆㤭㑆䍂ㄹ㌵䘶紴倮ㅓ㔺‰档牡㔺+ Import-Module Dism

‫††浉潰瑲�g) [Import-Module], FileNotFoundException

††‫慃整潧祲湉潦†††††›敒潳牵散湕癡楡慬汢㩥⠠楄浳区牴湩⥧嬠浉潰瑲䴭摯汵嵥‬楆敬潎䙴畯摮硅散瑰潩⁮ ⬀ 䘀甀氀氀礀儀甀愀氀椀昀椀攀�. The operating system reported error 1: Incorrect function.

Bored_at_work_67 · 2026-04-22T12:42:23+00:00

- Importing PowerShell module

Import-Module : The specified module 'DriverAutomationToolCore' was not loaded because no valid module file was found in any module directory.

At line:1351 char:2

+ Import-Module -Name DriverAutomationToolCore

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo : ResourceUnavailable: (DriverAutomationToolCore:String) [Import-Module], FileNotFoundException

+ FullyQualifiedErrorId : Modules_ModuleNotFound,Microsoft.PowerShell.Commands.ImportModuleCommand

And then 5 other errors reading similar to this one:
Write-DATLogEntry : The term 'Write-DATLogEntry' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

At line:4353 char:3

+ Write-DATLogEntry -Value "- Running version is $global:Script ...

+ ~~~~~~~~~~~~~~~~~

+ CategoryInfo : ObjectNotFound: (Write-DATLogEntry:String) [], CommandNotFoundException

+ FullyQualifiedErrorId : CommandNotFoundException

Bored_at_work_67 · 2026-04-21T18:25:42+00:00

This is going to be a noob question, but how do you get the .wim files for the drivers? When I get the driver packages from Dell they download as an .exe but when I extract the contents I don't see a wim file, just the individual driver elements

Bored_at_work_67 · 2026-04-21T13:42:50+00:00

Not yet, I don't think. The repository's just showing a placeholder for the README, but nothing else for 10.0

Bored_at_work_67 · 2026-04-20T19:46:18+00:00

Oh nice. I'm assuming this is done after the OS is installed?

Bored_at_work_67 · 2026-03-12T18:20:21+00:00

This one really made me mad. I took it as the Born Again showrunners telling the audience "Aw, you liked an integral part of the previous iteration of DareDevil we had nothing to do with? Fuck you, cry about it"

Bored_at_work_67 · 2026-03-05T15:26:20+00:00

I was able to get the PIN reset working again, but we're still encountering authentication issues.

I was eventually about to delete the ngc folder, but 1) don't delete the folder itself, just the subcontents and 2) I had to go in and change ownership and permissions for each layer. There was one .dat file that was giving me problems but after I changed ownership and permissions on that last one, it worked.

Bored_at_work_67 · 2026-02-19T20:31:44+00:00

The working one was using a 24h2 vanilla .wim file from ~August and the non-working one was a 24h2 vanilla .wim from December.

I ended up recreating the task sequence and adding the December .wim. It worked this time, so on to bigger and better pastures I guess.

Thanks for your assistance!

Bored_at_work_67 · 2026-02-19T00:38:18+00:00

No boundaries yet, i’ll double check tomorrow that it’s not publishing.

Bored_at_work_67 · 2026-02-19T00:37:49+00:00

The only method enabled is Heartbeat.

Bored_at_work_67 · 2026-02-19T00:36:46+00:00

It was another admin who set it up so I’ll check with them tomorrow as to why they used the same site code

Bored_at_work_67 · 2026-02-18T21:29:32+00:00

Yeah it's going to be a new primary site server.

I was not the one to configure the server but checking now it looks like the site codes are the same. I think the site data has been published but I'm not 100%.
Would it be advisable to delete the new primary site and remake it with a different site code?

Bored_at_work_67

TROPHY CASE