>Hi Ed, you're up early ;-)
>
>>Not using Setup Wizard - both InstallShield and Wise can do this, but you have to be aware of the deployment scenario.
>
>We use Wise InstallBuilder 8.0, but I can't find anything about Terminal Server in the documentation.
>
>Can you explain also what you mean by "deployment scenario".

Deployment scenario - the environment that you're deploying into. IE the difference between standalone and a network environment.

You're effectively deploying this app to multiple "independent" systems - each user has his/her own registry hives. You need to ensure that the registration takes place in the context of the All Users environment, rather than the conext of the current user.

Under Terminal Server, the HKEY_CURRENT_CONFIG is multi-valued, in the same way that HKEY_CURRENT_USER is mapped to the hive for the currently logged-in User under HKEY_USERS. In InstallShield Pro, I have to ensure that I install the DLLs side-by-side to the application directory, and then populate the registry hives of all recipient users through the Default settings. You may need to upgrade your version of Wise to an Enterprise version - I know that this functionality with IS Pro requires a different version of IS Pro to handle the Terminal Server/MetaFrame deploy issues. I'm nowhere near as familiar with Wise as IS, but I would not be surprised to find that an Enterprise environment version of the Wise Installer is needed to avoid the need to install under each user, or at a minimum, that you'd need to resort to writing some script to get the job done. 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.)

>
>Best.
>
>Matt.