Re: create com object and register trouble

hey, I was just power user and was able to do my job on XP. I only need the
admin ID to allow me access to certain registry key. Certainly admin
power user is convenient but now the supposedly more secure Vista requiring
Admin to be developer is security regressive!

I can't believe this need of admin powered developer is the intend of Vista

There must a way to setup a developer is do his job of application
development, testing as power or standard user. I will accept the limitation
that I may need elevated privilege when and only when I do final production
deployment to users


"Michel Posseth [MCP]" <msdn@xxxxxxxxxxx> wrote in message
news:717403DA-0249-4651-9347-5903F856173E@xxxxxxxxxxxxxxxx
GS

<SNIP>
What is the proper way of setting up the environment for me as power user
to
create /build com object

</SNIP>

a developer should be a local admin to do his job properly

HTH

Michel



"GS" <gsmsnews.microsoft.comGS@xxxxxxxxxxxxxxxxx> schreef in bericht
news:ugVB7$08JHA.4000@xxxxxxxxxxxxxxxxxxxxxxx
a developer imho should not be using local admin all the time.

After all he has to do his own other task, email, web research....,
communicate with others. we don't have the luxury of total secure
cooperating internet community - it has been spoiled by a few highly
organized criminals, cyber space terrorist, and some espionage.

developers may be smart and savvy but they are also under intense
deadline
pressure and may even have to work long hours at times and that is the
time
someone becomes vulnerable to security fault pas




"Michel Posseth [MCP]" <msdn@xxxxxxxxxxx> wrote in message
news:B7499F9C-3A02-4778-90DC-2C33D79E15D5@xxxxxxxxxxxxxxxx
AFAIK a developer should be at least a local admin

imho a company who makes there software developers lower level users
in
there domain is not taking there devlopers role serious .

Michel


"GS" <gsmsnews.microsoft.comGS@xxxxxxxxxxxxxxxxx> schreef in bericht
news:eRQtspj8JHA.5704@xxxxxxxxxxxxxxxxxxxxxxx
I tried a build com class from vs 2008 on vista ultimate form a power
user.
despite
I have access to the files, folders,
and use administrator explicitly created the appropriate CLS ID
key
and
progid key as well as granting me full access on these keys
I get can not register ....... can not access registry .....

consequently no application nor vbs can create the com object.


What is the proper way of setting up the environment for me as power
user
to
create /build com object

I'm using net.3.5 sp1. vista ultimate is fully patched








.

Relevant Pages

  • Re: Use of credentials with UAC in vista
    ... user's account, from a command prompt with 'run as administrator' privledges, and it failed saying access denied. ... The user's account has power user permissions. ... There is no more Power User on Vista, ... It also appears from reading the above article that it did indeed cache my admin credentials. ...
    (microsoft.public.windows.vista.general)
  • Re: Adding a new user & computer
    ... the users will be add to the local admin group only. ... time they will be able to install windows update and install SBS ... >> If you create a user with the power user template, ... >> Microsoft SBS Product Support ...
    (microsoft.public.windows.server.sbs)
  • NT 4.0 Domain/XP Clients
    ... OUR xp clients can't install network printers AND after ... I usually log in as a Domain Admin and muck around, ... that would allow printing by the power user. ...
    (microsoft.public.windowsxp.print_fax)
  • Re: Help! The borg is at my doorstep!
    ... if the admins give full rights to each developer on each workstation, ... You can tell the admin group to make up special policy rules ONLY for your ... but thats a mondo trivial thing. ... that is configured as a developer workstation, and if you find it doesn't ...
    (microsoft.public.fox.programmer.exchange)
  • Re: Does Power Users really work?
    ... Power User is not going to give them the ability to run ... applications that require an Admin context. ... I set up Win2k pc's on our network ... > users that need to be set at Administrator Level just so ...
    (microsoft.public.win2000.security)
Loading