kennysarmy Posted December 11, 2020 Posted December 11, 2020 I've got a task sequence which installs our Windows 10 image. I want to tinker with this to create a new task sequence that has a newer version of windows as the base WIM. I'd rather not edit the original so thought it would be relatively easy to take a copy - but can't see how to do it through the GUI :/ Any ideas?
CHiLL Posted December 11, 2020 Posted December 11, 2020 (edited) Are you using SCCM? If so, right clicking the TS shows a copy option, which will create a clone of the selected TS, which you can then modify. I'm not sure about WDS/MDT though Edited December 11, 2020 by CHiLL
Chuckster Posted December 11, 2020 Posted December 11, 2020 Create a new task sequence... call it whatever you want with a unique ID. Go through the rigmarole of creating it. Once created, go to the Control Folder and locate the Task Sequence folder of the original one from its ID. Copy the ts.xml file and paste it into the folder of the newly create Task Sequence. HTH 3
Davit2005 Posted December 11, 2020 Posted December 11, 2020 (edited) Create a new task sequence... call it whatever you want with a unique ID. Go through the rigmarole of creating it. Once created, go to the Control Folder and locate the Task Sequence folder of the original one from its ID. Copy the ts.xml file and paste it into the folder of the newly create Task Sequence. HTH ^ ^ I've done this many times on MDT. Once done just go back into MDT and where you can change things such as the image used for the task etc. You should be able to identify the folder for the task you want to copy in the control folder which you should have in both your deployment and build folders. Edited December 11, 2020 by Davit2005 1
kennysarmy Posted December 11, 2020 Author Posted December 11, 2020 I'm guessing I need to create a new Answer file from scratch or can I copy that too?
kennysarmy Posted December 11, 2020 Author Posted December 11, 2020 Sorted it Updated the deployment share. Then opened Windows System Image Manager. Updated the Windows Image that it was pointing to - opened the old answer file - asked me if it needed to update then resaved to the new MDT location. Imaging a PC now and seems to be working OK.
snagrat Posted December 11, 2020 Posted December 11, 2020 Isn’t that the issue with ADK 2004 and BIOS devices. There is a fix for it if it is.
kennysarmy Posted December 11, 2020 Author Posted December 11, 2020 Isn’t that the issue with ADK 2004 and BIOS devices. There is a fix for it if it is. Possibly but I double checked my answer file and of course it's pointing at the previous image - doh. Will update answer file file and try again - looks like PC imaged - but it's going through the parts of the setup that my answer file would normally manage. I'm getting there - and it is Friday!
mrstrong Posted December 11, 2020 Posted December 11, 2020 I had an odd mdt failure a while back, I think a task sequence had bombed out and when I fixed it and ran it again mdt got confused and wouldn't complete. I managed to fix by completely wiping the disk so mdt had a clean slate to start work on. re copying a task sequence I've used this before from Johan Arwidmark (one of the mdt "gurus") https://deploymentresearch.com/duplicating-task-sequences-in-mdt-2013-lite-touch/
mrstrong Posted December 11, 2020 Posted December 11, 2020 oh you're not switching image are you from 64 to 32 bit ? would need to change unattend file e.g. replace amd64 with x86 or vice versa
kennysarmy Posted December 11, 2020 Author Posted December 11, 2020 oh you're not switching image are you from 64 to 32 bit ? would need to change unattend file e.g. replace amd64 with x86 or vice versa Hi, No - just from 1903 EDU to 20H2 - all 64 bit.
Steve21 Posted December 11, 2020 Posted December 11, 2020 Any packages you're injecting like .NET that you might not have updated for the new OS/WIM? Steve
kennysarmy Posted December 14, 2020 Author Posted December 14, 2020 Any packages you're injecting like .NET that you might not have updated for the new OS/WIM? Steve Good shout. Currently though I can't even get it to work with a standard task sequence and unedited answer file. More testing today.
kennysarmy Posted December 14, 2020 Author Posted December 14, 2020 So deployment fails again with the error as above and still... All appears to be working: Running action : Install Operating System - 100% Then: Applying unattend.xml with DISM.EXE Then fails. This is with a new task sequence with no changes to the unattend.xml - just the basic one that's created when you create the task sequence. This is the answer file if anyone can spot the obvious error! OnError 0 1 .\Operating Systems\Windows10Edu20H2\Sources\install.wim /IMAGE/INDEX 1 OnError true en-US 0409:00000409 en-US en-US en-US true Balcarras School Balcarras School true Pacific Standard Time about:blank EnableAdmin 1 cmd /c net user Administrator /active:yes UnfilterAdministratorToken 2 cmd /c reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v FilterAdministratorToken /t REG_DWORD /d 0 /f disable user account page 3 reg add HKLM\Software\Microsoft\Windows\CurrentVersion\Setup\OOBE /v UnattendCreatedUser /t REG_DWORD /d 1 /f disable async RunOnce 4 reg add HKLM\Software\Microsoft\Windows\CurrentVersion\Explorer /v AsyncRunOnce /t REG_DWORD /d 0 /f 0409:00000409 en-US en-US en-US 0 "" 1 9 9 1 "" "" "" Default 1 l4244728 true true Administrator . l4244728 true 999 wscript.exe %SystemDrive%\LTIBootstrap.vbs Lite Touch new OS 1 true Work 1 true true true Balcarras School Balcarras School 0409:00000409 en-US en-US en-US \Drivers
kennysarmy Posted December 14, 2020 Author Posted December 14, 2020 I'm going to download the ISO for 1909 instead and go through the process with that base image to see if it's something specific to 20H2
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now