This post has been republished via RSS; it originally appeared at: IIS Support Blog articles.
Many developers don’t have Administrator rights on the machines they use for development. IIS Express is used to allow these developers load and run projects in Visual Studio without Administrator rights.
If your project is not compatible with IIS Express and you want to run it on Local IIS without Administrator rights on the machine, try the two workarounds below.
Run the application pool under the non-admin user’s account
- Search for Internet Information Services in Start
- Go to Application Pools. Select DefaultAppPool
- Go to Advanced Settings on the right side
- Change Identity to your domain user account
- Reset IIS (Go to Command Prompt and run iisreset)
- Test running the VS project in Local IIS (without admin rights)
- If it doesn’t work, try the second suggestion below (SeDebugPrivilege)
If you want to use this workaround, please consider the risk below.
Before you change the ASP.NET worker process to run under a different account, consider the possible consequences if the ASP.NET worker process should be hacked while running under that account. The ASPNET and NETWORK SERVICE user accounts run with minimal permissions, reducing the possible damage if the process is hacked. If you must change the ASP.NET worker process to run under an account that has greater permissions, the potential damage is greater.
Give SeDebugPrivilige to the domain user account
- Search for “run” in Start
- Type gpedit.msc
- Navigate to “Local Computer Policy > Computer Configuration > Windows Settings > Security Settings > Local Policies > User Right Assignment > Debug programs“
- Add user’s account
- Restart the machine
- Test running the VS project in Local IIS (without admin rights)
If you want to use this workaround, please note that the user who has given Debugging permission can debug all services in Windows.