Create a package from the differences between two disk images
I am looking for suggestions. I am supporting an organization that deploys disk images on CD; instead of installing packages. For example, the image of the software baseline is spanned across about 5 CD's and we install a new image whenever the software is upgraded. The software includes Windows XP and many different applications. I would like to figure out how I can create an installation package of the differences between the two images. But I cannot think of a way to do it. Is is possible to diff two images that are spanned on multiple CD's? Or is it possible to install the software on two disks and diff the disks and create an installation package from that? I cannot affect the process that deploys the CD's to us in this way, but I can try to make my site's operation more efficient. Any ideas are appreciated. Thanks
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
aogilmor
18 years ago
I've seen this type of "throw everything in but the kitchen sink" image management and it never seems to work well because once you've got an image deployed it's hard to change/manage, etc. not to mention every app had better be perfect, because if one app is squirrely your whole image is bad.
Better IMHO to take a base image approach and layer apps on top of that as needed. This approach seems to work best. As for deployment method, read up on some of the boards here. Everything from batch files to GPO to SMS to whatever..... but it doesn't have to be real fancy to be effective.
Better IMHO to take a base image approach and layer apps on top of that as needed. This approach seems to work best. As for deployment method, read up on some of the boards here. Everything from batch files to GPO to SMS to whatever..... but it doesn't have to be real fancy to be effective.
Posted by:
revizor
18 years ago
Can't agree more with what you are saying, aogilmor.
Just think about some minor application upgrade - all of the amount of rework in order to essentially overwrite a few files?
If one would deploy all apps as a single package, this would be a nightmare.
Edwardsgs,
my advice is: divide and conquer! MS Office goes separately, AutoCAD goes separately, Jim's killer screensaver app goes separately...
Just think about some minor application upgrade - all of the amount of rework in order to essentially overwrite a few files?
If one would deploy all apps as a single package, this would be a nightmare.
Edwardsgs,
my advice is: divide and conquer! MS Office goes separately, AutoCAD goes separately, Jim's killer screensaver app goes separately...
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.