MDT 2008 - efficient way of 're-creating' task sequence after image update and re-import?

Discussion:

(too old to reply)

James

2008-11-26 15:55:54 UTC

Hello,

I have several custom wim images that I will be deploying using MDT 2008 LTI
process... I expect to have to update the wims a few times. The task
sequences I created to deploy these images have lots of customization and
take time to manually re-create. Whats the best way to handle this? or avoid
it? Can I just copy the old ts.xml file? I assume there is some relation
between the task sequence and the OS it deploys that may be broken if I just
create a default task sequence and then copy the ts.xml from existing task
sequence over the new one? Essestially, the task sequences will remain
unchanged, I will be updated the images they deploy...

anyone know?

James

2008-11-26 16:29:19 UTC

Permalink

update:

my assumption is that I can simply do the following. I'm basically looking
for confirmation from someone who knows and/or gotchas I should be aware of?

- OS is linked to the TS by the OS guid which is in OperatingSystems.xml and
the TS.xml

- I can simply create a new task sequence of the same type via the GUI and
then copy/paste my existing TS.xml content over this new one, then replace
the OS guid with the newly updated one.

thats it.

yes?

Post by James
Hello,
I have several custom wim images that I will be deploying using MDT 2008
LTI process... I expect to have to update the wims a few times. The task
sequences I created to deploy these images have lots of customization and
take time to manually re-create. Whats the best way to handle this? or
avoid it? Can I just copy the old ts.xml file? I assume there is some
relation between the task sequence and the OS it deploys that may be
broken if I just create a default task sequence and then copy the ts.xml
from existing task sequence over the new one? Essestially, the task
sequences will remain unchanged, I will be updated the images they
deploy...
anyone know?

unknown

2008-11-27 09:51:41 UTC

Permalink

Yes, you can just copy an existing TS.xml file to a new Task Sequence
folder...

Another way is to copy it to C:\Program Files\Microsoft Deployment
Toolkit\Templates and use it as a template when creating new task
sequences

Regards

Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by James
my assumption is that I can simply do the following. I'm basically looking
for confirmation from someone who knows and/or gotchas I should be aware of?
- OS is linked to the TS by the OS guid which is in OperatingSystems.xml and
the TS.xml
- I can simply create a new task sequence of the same type via the GUI and
then copy/paste my existing TS.xml content over this new one, then replace
the OS guid with the newly updated one.
thats it.
yes?

James

2008-12-01 15:23:19 UTC

Permalink

Hi Johan,

thanks for the reply. I wound up having problems doing this (first way, copy
ts file over the new unconfigured one and also tried just copy/pasting
contents over the new unconfigured one). Was not aware of the template
approach, I'll try that next time.

any idea why the following was happening to me?

I have the lab deployment point, of course, and also a seperate Deploy
deployment point, I build from the lab and deploy from the Deploy (actually,
I build from the lab and other users deploy from the deploy one, thats why I
went with the 2 seperate deployment points).

1. I created a new TS
2. copied existing TS.xml file over this new one
3. replaced OS guid with the appropriate one
4. selected the new TS to be available on my seperate Deploy deployment
point
5. ran update (files only) on the Deploy deployment point (verified the OS
files (a wim image in this case) are copied to Deploy and the
OperatingSystems.xml file is updated apropriately)
6. ran update (files only) on my lab deployment point

next time I run update (files only) on the Deploy deployment point all the
data for the OS's that were previously added to the Deploy deployment point
is gone. The OS files are gone, and their corresponding entries in
OperatingSystems.xml are gone. ???? They are still in the lab deployment
point but removed form the Deploy one? If you look at the Deploy deployment
point those TS's are still checked off to mark them as available for that
deployment point?

way confused as to why this happened... lost several hours trying to figure
it out then wound up having to just manually create 4 different task
sequences that are identical to an existing one except the wim file (OS)
deployed. :(

any ideas?

Post by unknown
Yes, you can just copy an existing TS.xml file to a new Task Sequence
folder...
Another way is to copy it to C:\Program Files\Microsoft Deployment
Toolkit\Templates and use it as a template when creating new task
sequences
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

unknown

2008-12-02 07:32:26 UTC

Permalink

Yeah, templates are great, and yes, you should always use two
deployment points, one for lab (creating reference images), and one
for production deployment.

As for your issue, I haven't seen that, and I have copied a lot of
TS.XML files... What do you mean by " all the
data for the OS's that were previously added to the Deploy deployment
point"? What data?

If the data is corrupt in the deploy DP, you can always rename the
Deploy\Control folder, and run Update (files only), on the Deploy DP.

There is no need to run Update (files only) on the lab DP, those files
are always updated anyway.

Regards

Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by James
Hi Johan,
thanks for the reply. I wound up having problems doing this (first way, copy
ts file over the new unconfigured one and also tried just copy/pasting
contents over the new unconfigured one). Was not aware of the template
approach, I'll try that next time.
any idea why the following was happening to me?
I have the lab deployment point, of course, and also a seperate Deploy
deployment point, I build from the lab and deploy from the Deploy (actually,
I build from the lab and other users deploy from the deploy one, thats why I
went with the 2 seperate deployment points).
1. I created a new TS
2. copied existing TS.xml file over this new one
3. replaced OS guid with the appropriate one
4. selected the new TS to be available on my seperate Deploy deployment
point
5. ran update (files only) on the Deploy deployment point (verified the OS
files (a wim image in this case) are copied to Deploy and the
OperatingSystems.xml file is updated apropriately)
6. ran update (files only) on my lab deployment point
next time I run update (files only) on the Deploy deployment point all the
data for the OS's that were previously added to the Deploy deployment point
is gone. The OS files are gone, and their corresponding entries in
OperatingSystems.xml are gone. ???? They are still in the lab deployment
point but removed form the Deploy one? If you look at the Deploy deployment
point those TS's are still checked off to mark them as available for that
deployment point?
way confused as to why this happened... lost several hours trying to figure
it out then wound up having to just manually create 4 different task
sequences that are identical to an existing one except the wim file (OS)
deployed. :(
any ideas?

James

2008-12-02 14:53:32 UTC

Permalink

Hi Johan,

thanks again. The data I'm refering to is 1. the operating system source
file(s) and 2. the actual entries inside the OperatingSystems.xml file
within the control folder of the deploy DP. To elaborate on 1: folder with
one wim image, for each OS in this case, the result of adding OS of type
custom wim to the workbench, then making a TS that deploys it, selecting
that TS as available to the DP, and updating, this copies the OS source
files to the DP, those get deleted from the deploy DP)

maybe something to do with my doing the update files only on the lab DP...
I'll experiment in a test environment before trying again, I'll also try the
template approach as that sounds better anyway.

1. if my clarification on what data I was refering to triggers any ideas on
what went wrong let me know

2. I did do a lot of adding/deleting TS's and updating the DPs during all
this... is the workbench pretty could about performing these operations
without things getting all mucked up from the high volume of occurences of
these actions?

thanks again, your help is appreciated.

Post by unknown
Yeah, templates are great, and yes, you should always use two
deployment points, one for lab (creating reference images), and one
for production deployment.
As for your issue, I haven't seen that, and I have copied a lot of
TS.XML files... What do you mean by " all the
data for the OS's that were previously added to the Deploy deployment
point"? What data?
If the data is corrupt in the deploy DP, you can always rename the
Deploy\Control folder, and run Update (files only), on the Deploy DP.
There is no need to run Update (files only) on the lab DP, those files
are always updated anyway.
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

unknown

2008-12-02 15:37:25 UTC

Permalink

No, it doesnt matter that you updated the lab dp (even thpough you not
have to)... The only thing that crosses my mind is that you might
have entered an invalid osguid in the TS.XML file, or that ther
operatingsystem.xml fiel got corrupt form some reason.

Try renaming the Control folder (in \Deploy), and update the Deploy DP
again (files only). This will refresh the DP.

Regards

Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by James
Hi Johan,
thanks again. The data I'm refering to is 1. the operating system source
file(s) and 2. the actual entries inside the OperatingSystems.xml file
within the control folder of the deploy DP. To elaborate on 1: folder with
one wim image, for each OS in this case, the result of adding OS of type
custom wim to the workbench, then making a TS that deploys it, selecting
that TS as available to the DP, and updating, this copies the OS source
files to the DP, those get deleted from the deploy DP)
maybe something to do with my doing the update files only on the lab DP...
I'll experiment in a test environment before trying again, I'll also try the
template approach as that sounds better anyway.
1. if my clarification on what data I was refering to triggers any ideas on
what went wrong let me know
2. I did do a lot of adding/deleting TS's and updating the DPs during all
this... is the workbench pretty could about performing these operations
without things getting all mucked up from the high volume of occurences of
these actions?
thanks again, your help is appreciated.

James

2008-12-02 22:36:45 UTC

Permalink

Johan,

just wanted to let you know the template route is working out great for me
so far... thank you! I was not aware of that option. I will also do as u
suggested to troubleshoot why the other way didn't work for me, after I get
caught up on this project.

thanks again.

Post by unknown
No, it doesnt matter that you updated the lab dp (even thpough you not
have to)... The only thing that crosses my mind is that you might
have entered an invalid osguid in the TS.XML file, or that ther
operatingsystem.xml fiel got corrupt form some reason.
Try renaming the Control folder (in \Deploy), and update the Deploy DP
again (files only). This will refresh the DP.
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by James
Hi Johan,
thanks for the reply. I wound up having problems doing this (first way, copy
ts file over the new unconfigured one and also tried just copy/pasting
contents over the new unconfigured one). Was not aware of the template
approach, I'll try that next time.
any idea why the following was happening to me?
I have the lab deployment point, of course, and also a seperate Deploy
deployment point, I build from the lab and deploy from the Deploy (actually,
I build from the lab and other users deploy from the deploy one, thats
why
I
went with the 2 seperate deployment points).
1. I created a new TS
2. copied existing TS.xml file over this new one
3. replaced OS guid with the appropriate one
4. selected the new TS to be available on my seperate Deploy deployment
point
5. ran update (files only) on the Deploy deployment point (verified the OS
files (a wim image in this case) are copied to Deploy and the
OperatingSystems.xml file is updated apropriately)
6. ran update (files only) on my lab deployment point
next time I run update (files only) on the Deploy deployment point all the
data for the OS's that were previously added to the Deploy deployment point
is gone. The OS files are gone, and their corresponding entries in
OperatingSystems.xml are gone. ???? They are still in the lab deployment
point but removed form the Deploy one? If you look at the Deploy deployment
point those TS's are still checked off to mark them as available for that
deployment point?
way confused as to why this happened... lost several hours trying to figure
it out then wound up having to just manually create 4 different task
sequences that are identical to an existing one except the wim file (OS)
deployed. :(
any ideas?

Post by James
my assumption is that I can simply do the following. I'm basically looking
for confirmation from someone who knows and/or gotchas I should be
aware
of?
- OS is linked to the TS by the OS guid which is in
OperatingSystems.xml
and
the TS.xml
- I can simply create a new task sequence of the same type via the GUI and
then copy/paste my existing TS.xml content over this new one, then replace
the OS guid with the newly updated one.
thats it.
yes?

Post by James
Hello,
I have several custom wim images that I will be deploying using MDT 2008
LTI process... I expect to have to update the wims a few times. The task
sequences I created to deploy these images have lots of
customization
and
take time to manually re-create. Whats the best way to handle this? or
avoid it? Can I just copy the old ts.xml file? I assume there is some
relation between the task sequence and the OS it deploys that may be
broken if I just create a default task sequence and then copy the ts.xml
from existing task sequence over the new one? Essestially, the task
sequences will remain unchanged, I will be updated the images they
deploy...
anyone know?