No, if no updates are availalbe, the user is not prompted with any dialog.

If the user exists on the target machine, has the same password, has remote connections enabled and it's on a group that can connect to the server, then yes, it works.

That's Great! Glad i helped!

Well, i guess if someone tries to install a previous version for a reason, you should allow him to. That's my opinion of course.

Hi,

It's clear on the documentation also that debugging is only supported on Uncompressed Layout

Thank you.

I can't see why is not getting installed if SQLExpress is already installed but with a difference instance name. If instances are different, SQLExpress will install fine, and create the new instance. 1) It's done automatically if you specify the correct parameters (instance name etc) at the Applicat...

If you change your version number, you should also change your revision code (InstallAware does this by Default). You don't need to check it manually.

MAINTENACE turns into TRUE when a you click at the "Add/Remove" button.
NEEDSUPRADE turns into TRUE, when a new setup is trying to be installed with the same ProductCode but with a different revision code.

Maybe the assemblies have some kind of protection from business objects when detecting the run under terminal services?

For licensing purposes it might be locked not to run under Terminal Services. Have you checked that case?

You can check if the GUID (ProductCode) key exists at registry HKLM\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Uninstall\\{GUID HERE} using Check Registry Key.

If it does, then a previous version is installed. You can check for as many keys as you want.

As i said, you can detect if another installation has already been made on the target machine and do whatever you want.

From doing a side-by-side installation (the way i told you) to asking them if they want to upgrade, instead of doing a side-by-side installation.

Terminal Server 2000 had some strange behaviors occuring from Permissions issues. Check if the target directory has permissions to be access by the Terminal User group, and the default terminal user.

If this is not the case, contact again. Sorry for the trouble though.

It's not a good practice to do it this way. The best way is to create a seperate installer for your versions, with different ProductCodes and Revision. The only thing you have to be cautious about is when you do UnInstall of one of your products. Before uninstall starts, you should check IF a differ...

Check your PM.

It's better to use (Un)Install MSI plugin for the .msi package. That way you can capture the progress and cancel it at any time you want.