Packaging with only OS or OS+
Hi,
I would like to get some different views on this.
Packaging on a machine with only the OS installed, versus Packaging on a machine with OS + Office + e.g. Acrobat Reader.
Why is one better than the other. I know Wise says only OS, but in the 7 years that I am packaging at many different companies. The machine always had office and some other apps. on it.
Thanks
Greetz,
Gizsha
I would like to get some different views on this.
Packaging on a machine with only the OS installed, versus Packaging on a machine with OS + Office + e.g. Acrobat Reader.
Why is one better than the other. I know Wise says only OS, but in the 7 years that I am packaging at many different companies. The machine always had office and some other apps. on it.
Thanks
Greetz,
Gizsha
0 Comments
[ + ] Show comments
Answers (6)
Please log in to answer
Posted by:
aa006
18 years ago
Posted by:
wiseapp
18 years ago
I would agree with aa006 since repackaging on a clean build machine is completely different then compared to one with core apps. That's why wherever I go I write this to my client's documents that I would be requiring two images:
1. Clean Build (Vanilla image no apps just OS)
2. Core Build(OS+standard apps probably tier 1 or tier 2)
1. Clean Build (Vanilla image no apps just OS)
2. Core Build(OS+standard apps probably tier 1 or tier 2)
Posted by:
xythex
18 years ago
Core apps change. You may build a package requiring resources that were installed with your core apps and not even know it. Then down the road when your core apps change all of a sudden your app stops working. Packaging on a clean machine helps you build a more robust package, that will work no matter what changes on your target clients.
Posted by:
wiseapp
18 years ago
Posted by:
fetgor
18 years ago
I agree and disagree, if using a coporate PC - lets call it "System Components" like Mdac, Installshield, ODBC connections and so on are not captured, but if using a Clean XP this may be in the package, and therefor removed if uninstalling the package.
So it all depends how you work, I prefere to capture on a Clean System to find out what is beeing installed, and IF some "system comonents" are beeing installed, either remove them from the package or capture on a Coporate PC.
Hope this helps?
So it all depends how you work, I prefere to capture on a Clean System to find out what is beeing installed, and IF some "system comonents" are beeing installed, either remove them from the package or capture on a Coporate PC.
Hope this helps?
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.