Update on running as Admin...

In addition to my informal poll about running as Admin here on my blog, I've been running a similar poll on the home page of http://www.graymad.com. So far, the results are not encouraging. A full 70% of those who have responded to the poll say that they run as Admin "Always". 20% run as admin "Rarely", and only 10% "never" run as Admin. Surely we, as a community, can do better than this.

So I'm going to re-issue my challenge...how about some help from my fellow dotnetweblogs.com bloggers? If you're running day-to-day using an Admin account, try for a week running without Admin privileges. I know it's possible, and it's not all that difficult. Let's try to set a good example for the developer community, and do our part to increase security for everyone!

For those who missed it, Keith Brown of DevelopMentor has an excellent article on this topic that was recommended to me by Anil John. I've been using his suggestion of keeping a command prompt opened using an Admin account, and that's definitely made life as a non-Admin much easier.

2 Comments

  • I will be honest and admit the I am trying to make the jump. I recently put W2K3 on my workstation and have a non-admin, non-poweruser account that I have but I am one step away from completely making the jump. I simply cannot get VS.NET to let me debug web apps!





    Arrgghhh. Once I am through this problem, I will swallow the red pill the rest of the way!

  • Keith,<br/><br/>


    Have you tried running VS.NET as an Admin account, using the Run As... command (right click the icon for VS.NET and select Run As...)? I'm able to debug ASP.NET apps using this technique.<br/><br/>


    Andrew

Comments have been disabled for this content.