When we started using Bamboo it was created using an individuals Active Directory login and running it through the console, without thinking about the ramifications of that. We would like Bamboo to run as a service, but when it is started as a service instead of in console and associated with an individual user. When we run it as a service now none of the jobs or configuration show up. The main issue is if there is any trouble shooting that needs to be done on the server it has to be done by the user who was set up Bamboo, which is not sustainable.
We hoped to either create a generic active directory account and transfer stuff over and run Bamboo in console or as a service it would not be much more trouble.