What sort of things require elevated privileges on your machine?
-
Our IT department wants to remove Admin privileges on all user's accounts EXCEPT those that can provide adequate justification for the need. (A sensible policy, I suppose, especially for non-devs.) The problem is, I've had admin privs for so long, that I've basically forgotten what sort of day-to-day activities I might no longer be able to do without them. (Like, back in the day, you couldn't edit the Windows Registry without them. Is that still the case?) So my question for you developers & techies is: if you don't have elevated privileges, what sorts of things does that prevent you from doing? And for those who still have the rights, what do you use them for? MSDN has compiled an excellent list with regard to Visual Studio[^], but I would like compile a broader and more extensive list for developer activities in general. So I would like to enlist your help to compile a long list of activities for which administrative privileges are required. [Of course, if Windows provided sudo, I'd be set...]
I work a lot with hardware - exotic hardware like X-Ray generators, X-Ray detectors, Input/Output boards - and our software is often required to lock some functions of the system (like kiosks) or setting itself to real time priority. Often we need to debug processes while they're running. And we need many programs for diagnostic and so on... basically wthout Admin rights we would be useless.
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver "When you have eliminated the JavaScript, whatever remains must be an empty page." -- Mike Hankey "just eat it, eat it"."They're out to mold, better eat while you can" -- HobbyProggy
-
Our IT department wants to remove Admin privileges on all user's accounts EXCEPT those that can provide adequate justification for the need. (A sensible policy, I suppose, especially for non-devs.) The problem is, I've had admin privs for so long, that I've basically forgotten what sort of day-to-day activities I might no longer be able to do without them. (Like, back in the day, you couldn't edit the Windows Registry without them. Is that still the case?) So my question for you developers & techies is: if you don't have elevated privileges, what sorts of things does that prevent you from doing? And for those who still have the rights, what do you use them for? MSDN has compiled an excellent list with regard to Visual Studio[^], but I would like compile a broader and more extensive list for developer activities in general. So I would like to enlist your help to compile a long list of activities for which administrative privileges are required. [Of course, if Windows provided sudo, I'd be set...]
At the place I work, a lot of computers can barely even open non-approved executeables without specific privileges. A lot of the computer is locked down for specific users if they don't have a specific need to use a lot of things. They even let us install python to monkey around with, and I wasn't even able to run it outside of IDLE. Makes sense though, as it can prevent a lot of unapproved programs from running and loading the computer with viruses.
-
Our IT department wants to remove Admin privileges on all user's accounts EXCEPT those that can provide adequate justification for the need. (A sensible policy, I suppose, especially for non-devs.) The problem is, I've had admin privs for so long, that I've basically forgotten what sort of day-to-day activities I might no longer be able to do without them. (Like, back in the day, you couldn't edit the Windows Registry without them. Is that still the case?) So my question for you developers & techies is: if you don't have elevated privileges, what sorts of things does that prevent you from doing? And for those who still have the rights, what do you use them for? MSDN has compiled an excellent list with regard to Visual Studio[^], but I would like compile a broader and more extensive list for developer activities in general. So I would like to enlist your help to compile a long list of activities for which administrative privileges are required. [Of course, if Windows provided sudo, I'd be set...]
-
Our IT department wants to remove Admin privileges on all user's accounts EXCEPT those that can provide adequate justification for the need. (A sensible policy, I suppose, especially for non-devs.) The problem is, I've had admin privs for so long, that I've basically forgotten what sort of day-to-day activities I might no longer be able to do without them. (Like, back in the day, you couldn't edit the Windows Registry without them. Is that still the case?) So my question for you developers & techies is: if you don't have elevated privileges, what sorts of things does that prevent you from doing? And for those who still have the rights, what do you use them for? MSDN has compiled an excellent list with regard to Visual Studio[^], but I would like compile a broader and more extensive list for developer activities in general. So I would like to enlist your help to compile a long list of activities for which administrative privileges are required. [Of course, if Windows provided sudo, I'd be set...]
If you write installers, you will probably need admin privileges to test and debug them. Most build chains work fine without admin privileges. Debuggers, on the other hand, almost have to have them. Diagnostic tools, such as memory analysis apps, usually need elevated privileges. For what it's worth, the last time some moron in corporate IT tried to take away my admin privileges I asked him how he was going to explain our development coming to a screeching halt. I have two servers I administer along with my development box. Without admin privileges I can't do my job.
Software Zen:
delete this; -
Our IT department wants to remove Admin privileges on all user's accounts EXCEPT those that can provide adequate justification for the need. (A sensible policy, I suppose, especially for non-devs.) The problem is, I've had admin privs for so long, that I've basically forgotten what sort of day-to-day activities I might no longer be able to do without them. (Like, back in the day, you couldn't edit the Windows Registry without them. Is that still the case?) So my question for you developers & techies is: if you don't have elevated privileges, what sorts of things does that prevent you from doing? And for those who still have the rights, what do you use them for? MSDN has compiled an excellent list with regard to Visual Studio[^], but I would like compile a broader and more extensive list for developer activities in general. So I would like to enlist your help to compile a long list of activities for which administrative privileges are required. [Of course, if Windows provided sudo, I'd be set...]
I wanted to do some performance testing on a WPF application, the SDK requires admin rights, not just for the installation but for the testing.
Never underestimate the power of human stupidity RAH
-
Our IT department wants to remove Admin privileges on all user's accounts EXCEPT those that can provide adequate justification for the need. (A sensible policy, I suppose, especially for non-devs.) The problem is, I've had admin privs for so long, that I've basically forgotten what sort of day-to-day activities I might no longer be able to do without them. (Like, back in the day, you couldn't edit the Windows Registry without them. Is that still the case?) So my question for you developers & techies is: if you don't have elevated privileges, what sorts of things does that prevent you from doing? And for those who still have the rights, what do you use them for? MSDN has compiled an excellent list with regard to Visual Studio[^], but I would like compile a broader and more extensive list for developer activities in general. So I would like to enlist your help to compile a long list of activities for which administrative privileges are required. [Of course, if Windows provided sudo, I'd be set...]
Some VS debugging sessions require admin rights, at least under some configurations. I think debugging code running in full IIS might require it, though I'm not sure of the exact details. Also attaching to services or other processes as an administrator usually needs admin rights. Writing to program files, windows/system folders, editing the registry all need rights. I think they might also be required to start/stop/restart some services, and I believe even viewing some Windows event logs requires admin rights, though might depend on the specific logs. I think a lot of it depends on policies and what rights are assigned to other apps/folders/executables.
-
Our IT department wants to remove Admin privileges on all user's accounts EXCEPT those that can provide adequate justification for the need. (A sensible policy, I suppose, especially for non-devs.) The problem is, I've had admin privs for so long, that I've basically forgotten what sort of day-to-day activities I might no longer be able to do without them. (Like, back in the day, you couldn't edit the Windows Registry without them. Is that still the case?) So my question for you developers & techies is: if you don't have elevated privileges, what sorts of things does that prevent you from doing? And for those who still have the rights, what do you use them for? MSDN has compiled an excellent list with regard to Visual Studio[^], but I would like compile a broader and more extensive list for developer activities in general. So I would like to enlist your help to compile a long list of activities for which administrative privileges are required. [Of course, if Windows provided sudo, I'd be set...]
-
Our IT department wants to remove Admin privileges on all user's accounts EXCEPT those that can provide adequate justification for the need. (A sensible policy, I suppose, especially for non-devs.) The problem is, I've had admin privs for so long, that I've basically forgotten what sort of day-to-day activities I might no longer be able to do without them. (Like, back in the day, you couldn't edit the Windows Registry without them. Is that still the case?) So my question for you developers & techies is: if you don't have elevated privileges, what sorts of things does that prevent you from doing? And for those who still have the rights, what do you use them for? MSDN has compiled an excellent list with regard to Visual Studio[^], but I would like compile a broader and more extensive list for developer activities in general. So I would like to enlist your help to compile a long list of activities for which administrative privileges are required. [Of course, if Windows provided sudo, I'd be set...]
-
I'm trying this on a fellow developers machine, but the VM is dead slow because windows defender wants to scan the VM folder. I don't have the rights to exclude the folder, and the developer said that if you change it, the next time you log on to the domain it will set it back. Any idea how to get around this?
-
Our IT department wants to remove Admin privileges on all user's accounts EXCEPT those that can provide adequate justification for the need. (A sensible policy, I suppose, especially for non-devs.) The problem is, I've had admin privs for so long, that I've basically forgotten what sort of day-to-day activities I might no longer be able to do without them. (Like, back in the day, you couldn't edit the Windows Registry without them. Is that still the case?) So my question for you developers & techies is: if you don't have elevated privileges, what sorts of things does that prevent you from doing? And for those who still have the rights, what do you use them for? MSDN has compiled an excellent list with regard to Visual Studio[^], but I would like compile a broader and more extensive list for developer activities in general. So I would like to enlist your help to compile a long list of activities for which administrative privileges are required. [Of course, if Windows provided sudo, I'd be set...]