>One of the thoughts I had are as follows:
>The end-user inserts the CD which has all the different installation components, such as iis setup, workstation install, sql install (or existing selection), etc.
>
>The user has the option to use an existing SQL instance or to install a new express instance. For this i must search the network and 'offer' all the different options (also existing database selection for enterprise interface to my app).
>
>I think it would be 'dumb' to have to install SMO just so that i can show the user the different options. And then he might choose to use an existing sql, which means we just installed smo on a machiene which he/she didn't really need.
>
>what are your thoughts on that?

If this serves only at installation time, then I agree that it should not remain there, if installed, after the installation. If you can find another alternative to negotiate with that without installing SMO, then, that would be better. Otherwise, you would need to setup a post installation process to deinstall it after. But, I wouldn't recommmend that way. Keeping it simple is always preferred. Let us know about the approach to resolve the issue once you find it.