Software Deployment

Thanks everybody for your input.
It's much appreciated.

Gizsha

I think buz there are good chances of capturing registry files & other unwanted files... we usually use only OS & wise software on our wise base build......then u don't have to worry about ther registry files other things....

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)

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.

You're right Xythex, That's what I prefer, I make my packages on a vanilla image and then test my apps package on the core build which probably has all or specific applications and is also incooperated with domain policies.

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?