>Hi Ed,
>
>Thanks. I've looked at www.wisesolutions.com, but they have a bewildering array of products.
>
>I thought I had a handle on installation using Wise - for instance I thought that ActiveX controls should be installed the the System32 directory, but some of my colleagues here think they should go in c:\program files\common files\.
>

Under Windows 2000, you can specify the System32 directory, and (assuming it behaves right under Win2K) will relocate them and install for side-by-side DLL versioning automagically; this vastly reduces DLL Hell to a mere DLL Purgatory...

>> I have a couple of CLients who use Wise, and at least one of them does deployments to MetaFrame; I'll try to ask them what they
>>needed to modify (or if the did modify their install for WTS - they may have each user install it separately, for all I know.)
>
>Thanks, Ed. I've also sent an email to Wise today.
>

FWIW, I've started using VSI 1.1 for some of my initial deploys, and made some minor adjustments in my loader to deal with initia; install and updating the shortcuts created by VSI. It turned out to be easier to use in at least one Crystal Reports/VFP SP4 deployment scenario - I could've spent the time chasing my tail to figure out the exact order for installing with IS Pro, but it was easier to just add the CR components needed to the initial install file set, and carefully select the dependent MSMs needed by both SP4 and CR - MSVCRT.MSM, MSVCIRT.MSM, OLEAUT32.MSM and VFPRUN.MSM, took out the older versions of MSVCRT that came in the Seagate distribution, and built it so that themerge modules handled the sequencing for me.