What you’re seeing
- Changes made to a pasted task sequence also show up in the original one.
- Both task sequences in Deployment Workbench share the same ID or refer to the same folder in the deployment share.
- Builds that use the original sequence suddenly behave like the modified variant.
- Deleting the copy removes or breaks the original as well.
Common causes
Every environment is different, but these are the causes our engineers find most often:
- Copy and paste in Deployment Workbench creates a linked reference to the same underlying task sequence, not an independent duplicate.
- MDT stores each task sequence's steps in an XML file tied to its ID, so two entries with the same ID share one file.
- Workbench treats pasted items much like shortcuts within its folder structure, which is easy to mistake for a true copy.
Why it matters
A task sequence defines exactly how new and rebuilt PCs are set up, including which applications, drivers and security settings they get. If the production sequence is silently changed, every machine imaged afterwards can come out wrong, missing software or carrying test settings, and the problem may not surface until users start reporting issues. Tracking down and rebuilding affected machines costs far more time than the original change, and imaging may need to pause until the sequences are separated.
How AskTechGurus fixes it
Skip the trial and error. A certified engineer works on your actual system, finds the root cause, and fixes it properly.
Tell us what’s happening
Submit a ticket in about two minutes. Paste the error, describe what changed, and pick your tier. No charge to submit.
A certified engineer diagnoses it
A vetted, US-based systems engineer claims your ticket, usually within minutes during business hours, and investigates over a secure remote session you can watch and end at any time.
Fixed and verified with you
The engineer resolves the root cause and confirms with you that it’s working. You don’t just get a workaround, and you get a plain-English summary of what was wrong.
Pay only when it’s resolved
Fixed price from $99, invoiced only after you approve the fix. If it isn’t resolved, you don’t pay.
Frequently asked questions
Have the machines we imaged recently been set up incorrectly?
If they were built after the change, they may carry the variant's settings. An engineer can compare the sequences and help you identify which builds are affected.
Can the original task sequence be recovered?
Often, yes, from a backup of the deployment share or by reconstructing it from what changed. We confirm the differences before restoring anything.