Currently the only way to enable logging for the Windows service is to edit the registry, which isn't a good idea for most Windows users.  Startup problems, where SlimServer shuts down almost immediately upon startup, are a particular problem that the web based setting of debugging can't help with.  Even if the debug options are made persistent (bug 2737) there will be no easy way to set them if SlimServer isn't running and the user can't access the web interface.  I'm thinking of something that is either a part of SlimTray, or else is launched from SlimTray, that turns on logging (--d_info?) and permits the designation of a log file location.