Standard approach to the server environment for th

Question

For web application package vendors providing installer for some reason:

Would you share the "standard" approach to prepare fixed server environment for an asp.net application package? But some conditions I have:

1)My application requires iis, .net framework and sql server.

2)Windows Server itself, Sql Server licence and media is not provided by my company, end users provide them.(Usually standard edition.) When visiting end user site, Windows Os is already installed, but SQLserver media is not.

3)Install paths of sqlserver program, datas(mdf, ldf) can be changed by users according to server condition.

4)Users and my company officers don't want to change operational circumstances of endusers. Just want to change install procedure currently by manual manpower visiting physical sites of users.

5)Developper Environment:Visual Studio 2010.

6)We don't afford to buy Install Shield, or other non-free software.

I assume a concept that can be fulfilled by custom actions of WiX. But if such server environment should not be contained to a distributable installer which faces against the hostile circumstances of user servers ( install might fail for unknown reasons), I don't need uninstall function to my installer. But if WiX designers don't expect such installer, I might be in wrong path...

Any ideas?