Powershell commands to change operating system image in task sequence

Question

Hello,
I am looking for a way to script changing a task sequence to use a different OS image file. So far the only thing I can find using the powershell MDT module is the "import-mdttasksequence" command, but it looks like that can only create a whole
new task sequence.
My end goal is to automate our master image builds  and the last step is to take the captured master wim file, import it into the Operating Systems folder, and then update the associated custom image task sequence to use that new OS image. With
"import-mdttasksequence" I have to create a new task sequence with a new ID, when I already have one present that would be easier to just update to point to a different OS image. I do not see anyway to edit task sequence steps using the powershell
module.
Is this possible? Maybe using Get-Item to get the OS GUID and then editing the task sequence XML file directly?
MDT 2013
Server 2008 R2
Regards,
Darren

Answer 1

Hi Darren,
If I understand correctly, you can use the same name for the captured WIM file? Then you can just copy it to the operating systems and it will be picked up by your TS.
I've found this
thread on the forums that probably has your solution in it.
From that thread:
I now capture to the Captures folder and name the WIM file after the task sequence ID. So for example, my "Update Windows 8 General Purpose" task sequence with ID "8_GP" now creates "\\server\DeploymentShare$\Captures\8_GP.wim"
In the Scripts folder on the deployment share I created "Relocate.cmd" with the following contents:
MOVE /Y "%DEPLOYDRIVE%\Captures\%1.wim" "%DEPLOYDRIVE%\Operating Systems\%1"
And finally, I added a step at the end of my task sequences that runs this custom command (no
Start in value defined):
cmd /c %SCRIPTROOT%\relocate.cmd %TaskSequenceID%
This works great and MDT does in fact recognize the changed .wim file in Operating Systems and copies it to linked deployment shares, so no worries there.
Hope this helps.