Welcome to MSDN newsgroup.
Regarding on the ASP.NET debugging with non-Admin user account problem,
here are some of my suggestions:

Generally, our document does indicate that we can debug ASP.NET app under a
non-admin account, however, mostly we'll fail to get it work due to many
certain permission settings.  I suggest you try the following things first:

1. Disable anonymous access for that IIS virutal dir(of the asp.net webpp),
and ensure integrated windows authentication. Then, when try debugging ,
use Filemon tool to check whether there're any file system accessing fails,
if so, try adjust the proper NTFS permission setting to resolve them.

2. If the #1 still dosn't work, I'm afraid we may have to use another means
to workaround the problem, we can temporarily change the ASP.NET' worker
process idenity to our logon user(non-Admin account), also make sure that
grant sufficient permission (such as modify, write permission to the
ASP.NET's temporary dir) to the the account, then we can try debugging
again under the non-admin account, the detailes steps are:

1.  Open the machine.config file from the
%windir%\Microsoft.NET\Framework\v1.xxxxx\CONFIG folder.
2.  Locate the <processModel> section.  I believe it's the fourth
occurrence of
"<processModel>".
3.  Change the "userName" attribute to "STONEEAGLE\josh"  (the domain MUST
be in
all caps).
4.  Change the "password" attribute to your password.

5.  Close and save the machine.config file.
6.  At a command line, run "IISRESET" to restart the worker process under
your
account.

7. try using VS.NET to debug the web app again

#If any certain access denied error occur, we can use filemon to check
first.

Hope helps. Thanks,

Regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)