Discussion:
can I just copy a new wim image file over existing?
(too old to reply)
James
2009-01-22 16:49:37 UTC
Permalink
Hello,

using MDT 2008 update 1. I have several custom wim images in the workbench
that I deploy. When I have to update these images can I simply re-run the
build and then copy the resultant wim file right over the existing one and
continue use, without having to actually add a 'new' operating system, and
then re-create the task sequence?

or does mdt track info about the image that would not be updated by doing
this, and cause problems... I ask because if you look at the properties of a
custom wim OS in the workbech you can see it has info about it, including
size, which will likely be different for the new wim.
unknown
2009-01-25 19:05:28 UTC
Permalink
You can ovwerwrite with a new wim file (note, they are case
sensitive)...

Regards

Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com
Post by James
Hello,
using MDT 2008 update 1. I have several custom wim images in the workbench
that I deploy. When I have to update these images can I simply re-run the
build and then copy the resultant wim file right over the existing one and
continue use, without having to actually add a 'new' operating system, and
then re-create the task sequence?
or does mdt track info about the image that would not be updated by doing
this, and cause problems... I ask because if you look at the properties of a
custom wim OS in the workbech you can see it has info about it, including
size, which will likely be different for the new wim.
James
2009-01-27 16:01:07 UTC
Permalink
thanks Johan.
Post by unknown
You can ovwerwrite with a new wim file (note, they are case
sensitive)...
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com
Post by James
Hello,
using MDT 2008 update 1. I have several custom wim images in the workbench
that I deploy. When I have to update these images can I simply re-run the
build and then copy the resultant wim file right over the existing one and
continue use, without having to actually add a 'new' operating system, and
then re-create the task sequence?
or does mdt track info about the image that would not be updated by doing
this, and cause problems... I ask because if you look at the properties of a
custom wim OS in the workbech you can see it has info about it, including
size, which will likely be different for the new wim.
Continue reading on narkive:
Loading...