|
We all have local admin rights on our work computers.
We also have anti-virus and email spam/virus check which are installed company wide (domain admin-rights)
I'd rather be phishing!
|
|
|
|
|
I'm actually using my work laptop as personal laptop as well.
Full rights, full access 
I'm glad my company has that kind of trust in its developers 
|
|
|
|
|
Sander Rossel wrote: I'm actually using my work laptop as personal laptop
Danger, Will Robinson! *flails arms*
|
|
|
|
|
Admin rights on my desktop and dev servers. A very locked down (via external policy from the data owners) account on the airgapped secure network. Fortunately that network also comes with an admin who views his job as making sure we can do ours while obeying security policy.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
I have full admin on my box, and I actually don't want it.
I want to have a limited user account because then I can truly replicate a user's bug report, which many times can't be repro'd because I have higher sysauth than they do. At home, I run a limited user account, and have a local admin for installations. That's what I'd prefer at my company, but they don't allow that.  The only options are : "limited user + no local admin", or "practically domain admin levels of godliness".
If I have a repeated action I need to do that always needs elevation, I find that the vast majority of the time I can accomplish it via command prompt. So I elevate the CMD instance once, leave it open and just kick off the repeat stuff I need to deal with that way.
|
|
|
|
|
None of our end users have local admin rights.
All developers have local admin rights.
I even have access to all the servers, although the sys admin will not allow me to make any changes to AD which I respect.
We have a decent firewall and good AV software. I am expected/trusted to be very careful and if I need to use a server I am under strict instructions to never user an internet browser on the server without first checking with the sys admin.
I think denying developers admin rights shows a lack of knowledge on the part of the sys admin. Developers need to understand security issues, for goodness sake.
If the developers don't understand computer security, at least at the level of how to avoid malware and viruses, the company is in deep poop and needs to hire new developers pretty damn quickly.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
modified 3-Sep-15 16:14pm.
|
|
|
|
|
I am the admin.
But everyone else is having local admin rights.
|
|
|
|
|
First week on the job with this same policy. Can't log in as admin, but can elevate privileges through annoying prompts. I'd say, I've come to love portable "installers" xcopy the files you need and it just works.
|
|
|
|
|
stgagnon wrote: Do you have admin rights on your PC?
Yes.
If the restriction is truly keeping you from producing work for the company, can't you get your supervisor involved.
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"You can easily judge the character of a man by how he treats those who can do nothing for him." - James D. Miles
|
|
|
|
|
no, our supervisor is in the same situation. Doesn't work like that.
And the mandate comes from a very high gov office. There's nothing you can do and no one you can complain to.
|
|
|
|
|
I have local admin rights.
I used to work for a company that did not give ANY of the engineers/developers, admin rights - that sucked.
|
|
|
|
|
I'm very lucky. At work I have all the necessary clearances to be granted a smart-card that gives me admin authorization to install software and such, if needed.
But 65,000 of my coworkers have no such luxury. If they want to update something or do anything that requires admin access, they have to open a service ticket and wait. A tech may come the same day to help them, if they are lucky.
|
|
|
|
|
While I have admin rights my manager has to fight for them every year. the same fight, the same argument and the same result... I get my rights approved. A monumental f***ing waste of time and effort and they have been doing this for over 10 years.
The argument BTW is that we need to support a critical windows service, the fact that the service has not been used in 6 years has not been disclosed to them.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Where I am now (and also at my previous job) you could request local admin rights and "I'm a developer" was enough justification. But now they are trying to take it away and have us request it only when we need it. The request, of course, also requires our boss' approval so that would delay the process significantly.
Certainly most developers here don't need local rights all the time, maybe only when installing third party software and such. Most stuff we write doesn't get installed locally.
But, we few developers (i.e. only me) who actually develop tools and utilities for ourselves do need to install locally whenever we make a change and having to wait even a few hours can be a significant delay.
So, when they asked me for justification of why I need local rights I sent screenshots of me trying to use gacutil without rights.
And it worked.
This week I got an email saying I'd soon have a separate local account that I can use. 
I don't know how that will work out, but I envision having a shortcut that will launch a dos box running under that user.
|
|
|
|
|
This sounds like a serious case of rectocranial inversion, and the only known cure is to eliminate the individual who invoked the limit on the development team. You have to have admin rights, at least on your own machine, to do the job. And someone in your group needs admin rights to the entire network, in order to implement your solution.
Will Rogers never met me.
|
|
|
|
|
In my last job they wouldn't let developers have admin rights on their laptops, and we had to request rights every time needed them.
I pointed out that we were developing Windows desktop and services with installers and we might need to install/uninstall multiple times a day, still no go.
The only answer was to raise about 25 requests in a single day until they caved as we were inundating the requests system with support tickets.
In my new job I get full admin.
|
|
|
|
|
If all else fails, annoy them into submission.
|
|
|
|
|
I work at a large global IT consultancy company. I have almost full admin rights. There are some programs that are enforced on all computers. This is usually not the case in smaller national companies here, where u often may chose and order the computer and applications that fits you best. And there are some regulations on which applications we are allowed to install. Butt otherwise I have full admin rights. It would be quite hard to develop otherwise. But as I am a consultant, and every customer has different demands, I always develop in virtual machines where I have the windows and database versions etc. matching the customers environment. So in those I have absolutely no restrictions, since I create them myself.
I also use my computer privately at home, but of course I also work from home every now and then.
Working for a global company, I have seen that the culture and level of responsibility and trust given to the individual differs quite much from country to country, and some times from company to company. In Sweden, developers are usually given a high level of own responsibility. After all, as developers, we are the ones who have the expertise how to best solve our asignments. The IT-department cant but blocks in our way or we would yell at our bosses who would force the IT-department to remove those blocks so that we can do our job.
|
|
|
|
|
I'm lucky is this respect, i'm both the software developer and network admin so i have domain admin rights. I have given the other developers local admin rights though as i know how much of a pain a restricted user account can be when you're debugging software.
Plus, you'd think a software developer actually knows what they're doing with a computer when compared to the people in sales or accounts, or even those pesky web developers who nag for admin rights just so they can install itunes and other such crap...
Personally i know i wouldn't be able to do half of my job if i didn't have admin rights
|
|
|
|
|
Hey Suzanne,
There are a lot of workarounds for this:
1. if it won't get you in trouble and if you have a local admin account, use it to grant your user local admin accounts
2. use a shim: https://petermassa.com/?p=197[^]
3. launch a windows explorer, powershell or cmd window with runas admin and don't close that process. you can use it then without having to reenter the credentials every time.
the command line for the device manager is:
mmc devmgmt.msc
I hope it helps 
Dan
|
|
|
|
|
Of course I have admin rights on my machine. I run Visual Studio .NET 2003 occasionally, which requires admin rights just to run under Win7. I'm responsible for our installers, which also require admin rights. I'm also the DSJB(*), which means I keep our source control and build servers running, so I also have admin rights on those machines.
Every time this topic has come up with our corporate IT organization, I've told them that removing my admin rights will make it impossible to do my job and bring product development to a screeching halt. That plus the fact the IT yabbos have never been able to fault any of my group's access to admin rights, makes this a non-issue.
(*) Departmental Sh!t-Job Boy
Software Zen: delete this;
|
|
|
|
|
Gary Wheeler wrote: Of course I have admin rights on my machine. I run Visual Studio .NET 2003 occasionally, which requires admin rights just to run under Win7.
What breaks without admin rights? I have 2003 installed on my box to look at some legacy stuff occasionally; but have never had to run-as admin to force anything I need to work.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
In order to get VS2003 to run under Win7 and above, I have the following properties set on its shortcut:
- Run this program in compatibility mode for Windows Vista (service pack 1)
- Disable visual themes
- Disable desktop composition
- Run this program as administrator
IIRC, items #1 and #4 are required for VS2003 to find registry settings and its own files properly. Believe it or not, items #2 and #3 correct a fault in the "find in files" operation that locks up without these checked.
Even with these set, there's a bug in the debugger (oh the irony) that fails to close a handle to the solution's .PDB file. After you've run your app under the debugger once, you have to exit VS2003 and restart in order to recompile your solution.
Software Zen: delete this;
|
|
|
|
|
huh. I don't have any of those set and it works for me. Is it just the C++ mode that's screwed up; the project I run in it is 99% .net/winforms. (There's a little C++ for a 3rd party UI component, but I never touch any of it.)
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
Yeah, these are all C++/MFC projects and settings. That's probably why there are differences.
I don't think the C++ compiler and linker are too affected by admin rights, although I can see where COM stuff might have issues with type library registration and accesses that required admin rights. I do know that native-mode debugging uses CPU debugging features (breakpoint/watchpoint registers and so on) that may not be used by .NET.
We have a substantial body of C++ utility code that got its start as long ago as 2000 (written using VC6), and then has been ported through VS2003, VS2008, and now VS2015. The biggest changes between each step have been correcting for new compiler diagnostics and replacing deprecated library function calls.
Software Zen: delete this;
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
