Windows 7 w/o admin rights
-
The company where I work is rolling out Windows 7 to the IT department. Bear in mind the vast majority of us in IT are developers. The problem is that the developers no longer have admin rights to the new machines. This is causing problems. My new machine hasn't been rolled out just yet, but I've heard some major grumbling and complaints that the developers are having problems doing their job, because of the lack of admin rights. My question is... Have any of you run into similar problems and what did you find as a solution?
-
The company where I work is rolling out Windows 7 to the IT department. Bear in mind the vast majority of us in IT are developers. The problem is that the developers no longer have admin rights to the new machines. This is causing problems. My new machine hasn't been rolled out just yet, but I've heard some major grumbling and complaints that the developers are having problems doing their job, because of the lack of admin rights. My question is... Have any of you run into similar problems and what did you find as a solution?
I'm going to be controversial here and say that I think it's a good thing that developers don't automatically have admin rights. Far too often I've seen devs take the lazy way with permissions issues and just want the code to run at admin level. This is a security nightmare, and not a stance that should be taken automatically. If you force a developer to run with the same security restrictions that the end users run with, then perhaps they'll stop developing applications that require admin privileges.
I'm not a stalker, I just know things. Oh by the way, you're out of milk.
Forgive your enemies - it messes with their heads
-
The company where I work is rolling out Windows 7 to the IT department. Bear in mind the vast majority of us in IT are developers. The problem is that the developers no longer have admin rights to the new machines. This is causing problems. My new machine hasn't been rolled out just yet, but I've heard some major grumbling and complaints that the developers are having problems doing their job, because of the lack of admin rights. My question is... Have any of you run into similar problems and what did you find as a solution?
Sadly, none of our machines have local admin access. There's nothing you can do except following procedure or finding another job.
-
The company where I work is rolling out Windows 7 to the IT department. Bear in mind the vast majority of us in IT are developers. The problem is that the developers no longer have admin rights to the new machines. This is causing problems. My new machine hasn't been rolled out just yet, but I've heard some major grumbling and complaints that the developers are having problems doing their job, because of the lack of admin rights. My question is... Have any of you run into similar problems and what did you find as a solution?
Do the devs need admin rights, or do they just want them? A little convenience in one spot can cause serious nightmares in another. Sometimes it truly is necessary to admin rights, but I think it's valuable to be coding and testing in a security environment your users will be using.
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
-
I'm going to be controversial here and say that I think it's a good thing that developers don't automatically have admin rights. Far too often I've seen devs take the lazy way with permissions issues and just want the code to run at admin level. This is a security nightmare, and not a stance that should be taken automatically. If you force a developer to run with the same security restrictions that the end users run with, then perhaps they'll stop developing applications that require admin privileges.
I'm not a stalker, I just know things. Oh by the way, you're out of milk.
Forgive your enemies - it messes with their heads
With win7 apps don't run with admin rights by default; so unless the dev is a moron who proceeds to bash his os back to win95 levels of security then runs without admin rights testing is still done by default (the major remaining issue being that the \bin\debug(release) folders have higher default permissions than than \program files\, but that's a VS issue not an OS issue. Edit: The problem with non-admin dev accounts is that what should take 5 minutes to download and install a tool to do X ends up taking an hour or two to play Mother-May-I with the IT dept. The Eclipse developers here have a major related issue because the Eclipse addon downloader doesn't play nice with with the BlueCoat content filter and whitelisting the address of an addin to allow access has a several hour timelag. Frustration levels with this have gotten high enough that at the last dev-IT tools/needs discussion several openly admitted that the standard process had become to disconnect from the lan, tether to their phone (without running VPN), and do the download that way.
3x12=36 2x12=24 1x12=12 0x12=18
-
With win7 apps don't run with admin rights by default; so unless the dev is a moron who proceeds to bash his os back to win95 levels of security then runs without admin rights testing is still done by default (the major remaining issue being that the \bin\debug(release) folders have higher default permissions than than \program files\, but that's a VS issue not an OS issue. Edit: The problem with non-admin dev accounts is that what should take 5 minutes to download and install a tool to do X ends up taking an hour or two to play Mother-May-I with the IT dept. The Eclipse developers here have a major related issue because the Eclipse addon downloader doesn't play nice with with the BlueCoat content filter and whitelisting the address of an addin to allow access has a several hour timelag. Frustration levels with this have gotten high enough that at the last dev-IT tools/needs discussion several openly admitted that the standard process had become to disconnect from the lan, tether to their phone (without running VPN), and do the download that way.
3x12=36 2x12=24 1x12=12 0x12=18
Dan Neely wrote:
With win7 apps don't run with admin rights by default
Errm, I know. With applications still being developed to run on Windows XP (and tested on XP as well), it's the quick test when they run the application outside of the debugger. Actually seeing the elevation prompt is a great way to tell them that they've done something they shouldn't.
I'm not a stalker, I just know things. Oh by the way, you're out of milk.
Forgive your enemies - it messes with their heads
-
I'm going to be controversial here and say that I think it's a good thing that developers don't automatically have admin rights. Far too often I've seen devs take the lazy way with permissions issues and just want the code to run at admin level. This is a security nightmare, and not a stance that should be taken automatically. If you force a developer to run with the same security restrictions that the end users run with, then perhaps they'll stop developing applications that require admin privileges.
I'm not a stalker, I just know things. Oh by the way, you're out of milk.
Forgive your enemies - it messes with their heads
Pete O'Hanlon wrote:
force a developer to run with the same security restrictions that the end users run with
Including the lack of
SeDebugPrivilege? :) -
Dan Neely wrote:
With win7 apps don't run with admin rights by default
Errm, I know. With applications still being developed to run on Windows XP (and tested on XP as well), it's the quick test when they run the application outside of the debugger. Actually seeing the elevation prompt is a great way to tell them that they've done something they shouldn't.
I'm not a stalker, I just know things. Oh by the way, you're out of milk.
Forgive your enemies - it messes with their heads
Agreed, although the issue I've seen most often is trying to write to data files in the app directory doesn't show up until someone tries installing it in program files. PS Your reply beat the edit to my last post, which in turn beat the minimum delay for a modified being appended to my subject line.
3x12=36 2x12=24 1x12=12 0x12=18
-
With win7 apps don't run with admin rights by default; so unless the dev is a moron who proceeds to bash his os back to win95 levels of security then runs without admin rights testing is still done by default (the major remaining issue being that the \bin\debug(release) folders have higher default permissions than than \program files\, but that's a VS issue not an OS issue. Edit: The problem with non-admin dev accounts is that what should take 5 minutes to download and install a tool to do X ends up taking an hour or two to play Mother-May-I with the IT dept. The Eclipse developers here have a major related issue because the Eclipse addon downloader doesn't play nice with with the BlueCoat content filter and whitelisting the address of an addin to allow access has a several hour timelag. Frustration levels with this have gotten high enough that at the last dev-IT tools/needs discussion several openly admitted that the standard process had become to disconnect from the lan, tether to their phone (without running VPN), and do the download that way.
3x12=36 2x12=24 1x12=12 0x12=18
Dan Neely wrote:
tether to their phone
Just did that for the first time using my Android while I was on travel. :cool:
-
Pete O'Hanlon wrote:
force a developer to run with the same security restrictions that the end users run with
Including the lack of
SeDebugPrivilege? :)Nemanja Trifunovic wrote:
Pete O'Hanlon wrote: force a developer to run with the same security restrictions that the end users run with Including the lack of SeDebugPrivilege?
On a locked down standalone network I have access to our admin has to explain why the developer accounts have that privilege instead of being default user accounts to the outside auditors almost every time they look it over. :doh:
3x12=36 2x12=24 1x12=12 0x12=18
-
Do the devs need admin rights, or do they just want them? A little convenience in one spot can cause serious nightmares in another. Sometimes it truly is necessary to admin rights, but I think it's valuable to be coding and testing in a security environment your users will be using.
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
At my last job I didn't have admin rights to start off with and that was a pain - mostly because of having to juggle between different projects that needed the different versions of the same DLLs registered and the default rights didn't allow them to be registered with regsvr32.dll, that kind of thing. I think Visual Studio had various problems as well. Was also a problem whenever having to install dependencies when moving to a new project and so on so eventually the admin got sick of having to enter his password on my computer every hour and gave me local admin rights.
-
The company where I work is rolling out Windows 7 to the IT department. Bear in mind the vast majority of us in IT are developers. The problem is that the developers no longer have admin rights to the new machines. This is causing problems. My new machine hasn't been rolled out just yet, but I've heard some major grumbling and complaints that the developers are having problems doing their job, because of the lack of admin rights. My question is... Have any of you run into similar problems and what did you find as a solution?
I've been developing, albeit not very broad range of, applications on my laptop for a year now, using VS 2010 and running as a pleb user. The only time I have to elevate is to publish a web application to c:\inetpub using the VS Publish command.
-
The company where I work is rolling out Windows 7 to the IT department. Bear in mind the vast majority of us in IT are developers. The problem is that the developers no longer have admin rights to the new machines. This is causing problems. My new machine hasn't been rolled out just yet, but I've heard some major grumbling and complaints that the developers are having problems doing their job, because of the lack of admin rights. My question is... Have any of you run into similar problems and what did you find as a solution?
Welcome to my world. I work for a defense contractor on an Air Force contract. Admin rights for "normal users" (of which I am a member) is unheard of - UNLESS you pass a CompTIA security course and fill out the appropriate paper work. This allows us to install tools we need (as long as it's on the "approved software" list). If we have to do admin type stuff, we have to logoff of our regular account, and login with our admin account because the act of logging in requires the appropriate CAC card, and they won't put both account decsriptions on the same card (how freakin stupid). Your only solution is to submit a request for admin rights, and detail the exact reasons you need such rights, and see what they say.
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001 -
Do the devs need admin rights, or do they just want them? A little convenience in one spot can cause serious nightmares in another. Sometimes it truly is necessary to admin rights, but I think it's valuable to be coding and testing in a security environment your users will be using.
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
The problem in most companies that aren't exeactly technology companies (with reagrds to software development), the IT department can be EXTREMELY slow to respond to installing softwarre. At my wife's company, it took them THREE WEEKS to install software she needed *that was mandated for her to use by management*. The only reason it didn't take longer was because she complained directly to her department VP, and he read the IT VP the riot act in the presence of the CIO. IT departments are almost always populated by self-important anal pores who have no regard for urgency of need, and they're so preoccupied with making sure that every minute procedure is followed that it clogs up productivity. I'd like an opportunity to run an IT department for a few months. Heads would *definitely* roll, and bodies would be stacked up for collection...
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001 -
I've been developing, albeit not very broad range of, applications on my laptop for a year now, using VS 2010 and running as a pleb user. The only time I have to elevate is to publish a web application to c:\inetpub using the VS Publish command.
You also have to elevate if you're installing a windows service during testing. That's why I try to do as much testing in a console app before committing the code and installing the windows service. Not having admin rights can be a royal pain.
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001 -
The company where I work is rolling out Windows 7 to the IT department. Bear in mind the vast majority of us in IT are developers. The problem is that the developers no longer have admin rights to the new machines. This is causing problems. My new machine hasn't been rolled out just yet, but I've heard some major grumbling and complaints that the developers are having problems doing their job, because of the lack of admin rights. My question is... Have any of you run into similar problems and what did you find as a solution?
Our machines were locked down tight to the point we couldn't install anything (no VS, Sql server or any other tools). We made the case for allowing us access and it was granted. Yes, I agree that we, as developers, should not ride roughshod over the rules but we do need a different machine than ordinary users as we are not ordinary users and we need access to very different tools. Bottom line was that without the proper tools and the ability to install and use them we simply can't create the software.
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair. nils illegitimus carborundum me, me, me
-
The company where I work is rolling out Windows 7 to the IT department. Bear in mind the vast majority of us in IT are developers. The problem is that the developers no longer have admin rights to the new machines. This is causing problems. My new machine hasn't been rolled out just yet, but I've heard some major grumbling and complaints that the developers are having problems doing their job, because of the lack of admin rights. My question is... Have any of you run into similar problems and what did you find as a solution?
spencepk wrote:
The company where I work is rolling out Windows 7 to the IT department.
You have my sympathy.
See if you can crack this: fb29a481781fe9b3fb8de57cda45fbef
The unofficial awesome history of Code Project's Bob! "People demand freedom of speech to make up for the freedom of thought which they avoid."
-
The company where I work is rolling out Windows 7 to the IT department. Bear in mind the vast majority of us in IT are developers. The problem is that the developers no longer have admin rights to the new machines. This is causing problems. My new machine hasn't been rolled out just yet, but I've heard some major grumbling and complaints that the developers are having problems doing their job, because of the lack of admin rights. My question is... Have any of you run into similar problems and what did you find as a solution?
I had that problem. I asked for admin access and they gave it to me. Usually, my not having admin access was because the helpdesk forgot to give it to me, so they tended to give it to me pretty quickly after asking for it.
