At the moment the installers ability to integrate as a service means that it has to ship with some software called JavaWrapper. This makes the configuration of Confluence way more complex than before, because now we have to ways of configuring settings. This is especially annoying since people who are used to configuring Java Apps and App Servers will have to learn a new way of changing settings, where the old one is perfectly fine (and complicated enough to learn). We should either get rid of this service thing (which seems overkill for an evaluation, and too complicated to many normal business users anyway), or make sure our documentation is updated, which will be very difficult to make easy to understand. Take this page for example: http://confluence.atlassian.com/display/DOC/Fix+%27Out+of+Memory%27+errors+by+increasing+available+memory - it now has two options: On windows do this, on Mac do that. You would need at least two more cases, and also link to the JavaWrapper software for further docs - not exactly easy. Also, we need a decision whether the installer should be an "Evaluation Installer" for now. My gut feeling tells me that people will run the installer on the desktop box, never shut it down again and make it run as a production server, which it is not. There needs to be a clear statement that it is fine to do so for a couple of days, but if you buy and use it you need to pass it on to the IT guys department. We might see a big increase in installer issues that will eat up what we have gained in the first place.