taking deployment/operations considerations into account

I realize that one's actions/decisions are colored by one's experience, and that not many developers have ever worked in IT deployment/operations, but I'm increasingly frustrated by the fact that our developers do not take ease/consistency of configuration into account when developing our product.  Like Windows (up until Vista), they assume that the administrator of our product owns the machine outright, as well as dependencies such as a SQL Server database that may or may not be installed locally on the machine our software runs on.  These assumptions don't hold up in, for instance, third-party hosting environments (where you can't necessarily log on to the machine via Remote Desktop) or organizations where the separation of responsibilities precludes owning the whole machine (there are p
 lenty of organizations among our customers where the machine/OS-level administrator is not allowed to see the application data, and the application administrator is not
 allowed administrative access to the OS).

I'm wondering how much such issues are taken into account by the individuals on this mailing list?


Al


      ____________________________________________________________________________________
Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ