rights

On some machine we have the following error at service install: "Service ... failed to start. Verify that you have sufficient privileges to start system services." Service is installed fine tho, just that it can't be started as Network Service from Services.msc. Service starts and runs good if started from console it's executable... Same thing happens with another service started as Local System. On other machines everything is fine. Service starts as network service with no problems. We think is a problem with windows rights, like error says, but how to check? And what to do? Thanks, Adrya

Can anyone tell me, what's the real difference between group and role? I've been trying to figure this out for some time now and the more information I read, the more I get the sense that this is brought up just to confuse people and there is no real difference. Both can do the other's job. I've always used a group to manage users and their access rights. Recently, I've come across an administration software, where is a bunch of users. Each user can have assigned a module (whole system is split into a few parts called modules ie. Administration module, Survey module, Orders module, Customer

Does anyone know what would be the minimum rights I would need to grant to a domain user account in order to run a windows service as that user? For simplicity, assume that the service does nothing over and above starting, stopping, and writing to the "Application" event log - i.e. no network access, no custom event logs etc. I know I could use the built in Service and NetworkService accounts, but it's possible that I may not be able to use these due to network policies in place. Two ways: Edit the properties of the service and set the Log On user. The appropriate right will be automatically

I'm having some trouble with my C# app that uses win32_networkingadapterconfig. The problem is that I can't use the altering functions in win32_networkingadapterconfig when I use the app on a user that dont have admin rights. I have tried to "run as administrator", but no luck. And I have tried to make a manifestfile with this content in the trustInfo part: <security> <applicationRequestMinimum> <PermissionSet class="System.Security.PermissionSet" version="1" Unrestricted="true" ID="Custom" SameSite="site" /> <defaultAssemblyRequest permissionSetReference="Custom" /> <