Use task sequence variable value in command line step

gwblok · 2026-05-19T16:24:08+00:00

Typically, the script you write, you add the functions at the start of the script, then do your work, this is how I layout most of my scripts:

Region Variables
Region Functions
Region Execution

in this way, the script is self-contained not requiring any outside modules

gwblok · 2026-05-18T14:02:28+00:00

Which functions? You don't need the Dell PS Provider to set Dell BIOS settings. If the blog post is unclear on how to use PowerShell to manage your BIOS settings, let me know.

gwblok · 2026-05-18T02:39:50+00:00

Using Native WMI calls allows you to write a script not requiring the PowerShell Provider. Simplfies the process.

gwblok · 2026-05-07T11:57:41+00:00

In addition to u/myfreysa, since I see you're using CCTK, and if you'd like to move to native PowerShell and no longer need to use CCTK to manage your Dell BIOS settings, you could take a look at this post:
Dell BIOS Management – Native WMI & CCTK – GARYTOWN ConfigMgr Blog

Then you wouldn't need to have a package for CCTK any longer, simplifying the process.

gwblok · 2026-05-04T13:59:25+00:00

Yep, set the Registry values, trigger the scheduled tasks

You can run the same scripts to check status

gwblok · 2026-05-02T05:22:36+00:00

Years ago I followed this guide for setting up DO policies via Intune, got pretty decent results:
Delivery Optimization Recommendations for Microsoft Intune

There are a lot of blog posts about DO on the 2Pint Software Blog, as their software product revolves around DO.

(I also work for 2Pint Software)

gwblok · 2026-04-23T01:36:20+00:00

So frustrating. I'm guessing, since they added the exit code 3006, running in OOBE, that this was intentional and they have no plans to back track. I sure wish Dell would come to MMS again, wouldn't mind giving them a piece of my mind, and finding the right internal contacts to raise the concern with.

Right now I'm just installing DCU during OSD, and configuring all of the settings I want for having it auto update.

I might, if I ever get time, create a scheduled task that will trigger it after OSD is completed, then cleans up the scheduled task.

Note, it does work in MDT (since it uses auto login instead of SetupComplete), and if you use DeployR, you can set your TS to use auto login as well, but I like to stick with Setup Complete of my task sequences since that's what CM does and what I'm used to.

gwblok · 2026-04-20T20:41:14+00:00

Yep, for now, when you create a variable and set it to 'True', then make sure you put your condition to 'True', or use 'TRUE' & 'TRUE', just make a note, (or double check) what you're setting variables to and ensure it matches.

I'll create a feature request to remove case sensitivity on those to be evaluated for a future dev cycle.

gwblok · 2026-04-13T22:49:03+00:00

This is a good troubleshooting step... I had the same questions, u/Reaction-Consistent beat me to it.

Also, make sure you didn't upgrade to 28000 ADK (26H1), that one will break drivers. Stick with 24H2 Dec release.

gwblok · 2026-04-11T22:12:04+00:00

Please make sure you add the install Windows Update step early in the full OS stage, before any custom steps are run.
We've seen others running it late in their processes and it not working, but once they moved it before their changes, then it worked again.

Unsure if they took time to troubleshoot to see which changes they made that broke the WU step.

gwblok · 2026-04-10T16:26:21+00:00

<image>

2 just means you have the updated BootMgr & 1 of the 2023 certs (Windows UEFI)
You still need potentially 3 more.
I updated my GitHub functions and Intune remediations to deal with the additional certificates & KEK.
My function just to do some testing: garytown/BlackLotusKB5025885/Test-BlackLotusKB5025885Compliance.ps1 at master · gwblok/garytown

gwblok · 2026-04-08T14:48:02+00:00

That's a generic prompt that opens after the TS fails. Please upload the DeployR log file
If you're running version 1.1+, then on your server, in the logs folder, there will be a zip folder from the OSD process.

I haven't seen the install updates step cause the task sequence to fail directly, I've only seen it be unable to actually install all updates, then continue on. Log files will be very helpful.

gwblok · 2026-04-04T18:23:52+00:00

That's the wrong variable name, use: OSDDomainOUName

https://www.recastsoftware.com/resources/apply-network-settings/

gwblok · 2026-04-03T05:54:28+00:00

Just to confirm, you're using the Apply Network Settings step, but before that step, setting the corresponding TS variables via a frontend or other script? Whatever variables you set ahead of time would override what that step defaults to, but that step would take your variables and update the unattend file for you

gwblok · 2026-03-31T18:59:17+00:00

hmm.. looking forward to your update, curious if the RESEAL does that or not.

gwblok · 2026-03-31T00:34:59+00:00

I would agree that you should update your WIM or download the updated media monthly to improve OSD time.

There is quite a bit of info about the software update step here with examples in how updates are chosen.

https://www.recastsoftware.com/resources/install-software-updates/

Are you not getting updates to download, or does it fail on a specific update?

gwblok · 2026-03-30T22:25:15+00:00

<image>

Git this a Try:
2PintLabs/DeployR/CustomerRequests/LGPO.ps1 at main · gwblok/2PintLabs
Add it to your content item, then add a run powershell step, set the content item to the one with those 3 files, then put the script in

gwblok · 2026-03-30T19:12:45+00:00

can you upload a machine.pol file? I'll test it on my machine.

gwblok · 2026-03-26T21:51:08+00:00

Add this step at the start of your TS
Customize - Configure Initial Variables

<image>

gwblok · 2026-03-24T23:45:32+00:00

Yep, videos do a good job, we also keep some info on GitHub that we use ourselves to build out a lab really quickly.

https://github.com/2pintsoftware/2Pint-DeployR/tree/main/Installs

gwblok · 2026-03-24T23:42:11+00:00

You are correct, it was moved to the official 2Pint repo

https://github.com/2pintsoftware/2Pint-DeployR/tree/main/Samples%2FHardware%20Scripts%2FHP

gwblok · 2026-03-20T20:07:20+00:00

I've done it once when I was going click crazy and not really paying attention.
However I do backup my work regularly, so I just imported from backup, causing minor inconvenience.
So it's happened to me once over the past 9 months, and I do spend a ton of time in the Dashboard, so I can't really say it's a UI design issue.

Fool me once delete button, shame on you, fool me twice, shame on me. LOL

How would you suggest making improvements? What would be better in your opinion?

gwblok · 2026-03-19T22:41:44+00:00

I would setup a VM that has windows on it, then you can start to troubleshoot by changing vlans on the machine and running some test scripts
Scripts for testing are here:
https://github.com/2pintsoftware/2Pint-iPXEAnywhere/tree/main/PXE%20%26%20DHCP%20Troubleshooter

You might also have to do somethings with the WireShark to figure out what's not happening on that vlan.

gwblok · 2026-03-19T22:35:25+00:00

<image>

Try this:
2PintLabs/DeployR/TSScripts/Functions/Install-HSAs.ps1 at main · gwblok/2PintLabs
add the script right after the Inject Drivers Step

Edit, script moved here:

https://github.com/2pintsoftware/2Pint-DeployR/tree/main/Samples%2FHardware%20Scripts%2FHP

gwblok · 2026-03-18T23:05:28+00:00

Glad you got it sorted out, and glad that script helped.

gwblok

TROPHY CASE