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.
If Bamboo goes to the setup wizard when started as a service, the most likely explanation is that the user the service runs under doesn't have permission to read the Bamboo home directory, so that's what I'd be looking at.
There is nothing that should prevent Bamboo from running as a service using an Active Directory account.
Premier Support Engineer
Thank you for your quick response Christian! For clarification running as a service my normal Bamboo homepage shows up as it always does. It displays the projects, plans recent build information etc. I get an internal server error message within Bamboo when I try to edit or drill down into a plan with any detail. I have made sure that the Windows User has permissions to the Bamboo home directory and installation directory. Any other thoughts?