Hi Morris,

Useful as your solution sounds, it's not very recommended because it means decreased security. Your solution is like giving everyone in your domain Administrator privileges, because "it's such an hassle to set up the individual rights" (I have really heard this once).

The System account is, as it name implies, a high-privileged account. This means it can do as much as everything it wants on your local machine. This also means Web sites running under this account can do what they want. This is a problem when you're not the only one developing; other developers can create code that can read, write, delete, etc any file they see fit.
Also, when your ASP.NET box is ever hacked, the hacker will be able to run code as the system account.

So, IMHO, it's better to use a lower privileged account. The ASPNET or Network Service accounts are created for just thus purpose. Instead of making ASP.NET run as a System account, you should use this lower privileged account, and tweak and tune the rights on our server. It's not as quick as making everyone Administrator, but in the long run it's much more secure.

Cheers,

Imar


---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.