I would elevate the service that Jenkins is running under to a local admin. You can then reduce the amount of privileges by trial and error to the appropriate level for your organization.
This isn't a Windows 2012 issue as it occurs on 2008. On Sunday, November 25, 2012 9:26:07 PM UTC-5, Drew Mace wrote: > > I'm trying to install Jenkins on a Windows Server 2012 Standard edition > box but hit a snag - I am getting an error: Service 'Jenkins' (Jenkins) > failed to start. Verify that you have sufficient privileges to start > system services. I ran the installer as administrator (elevated privs). > Anyone have any ideas what i could try?
