Too complicated to explain in subject

  • Thread starter Thread starter Eric
  • Start date Start date
E

Eric

First of all, forgive my ignorance if this is something
fairly simple and/or routine.

We're trying to figure out how to give each user Power
User rights (or at least rights to register dll's) on
their local machines without having to visit each machine
individually and doing it manually. Ideally, this would
be done with GPO's, but we've yet to figure out how to do
so.

Some software we run registers dll's every time it's
launched as a way to check for updated versions of the
files. As far as I know, this can't be done without
Power User rights, or above.

Any thoughts and/or suggestions would be appreciated.
 
Hi Eric,

Here are a couple thoughts.

If you are OK with all users having Power User membership on
all machines, then you could use the Restricted Groups feature
of GPO. This would not be a suitable way to go if you wanted to
have Users 1, 2, and 3 be PU on machines A and B, Users 4 and 5
on machine C, etc.. But, if you can chunk into a few sets of accounts
and of machines, then it may not be too bad.

What I would try however, is altering the reg permissions on the
keys that reregistering the app will cause to be touched.
If you do not know what these are, then a tool such as regmon
will let you trace this (from www.sysinternals.com)
Once identified, you could use GPO to set the permissions on
that/those key(s) so that Users have ability to write them.

Roger
 
Thanks for the advice, Roger. I'm not sure how I could
issue Power User rights via the restricted groups policy,
since Power User isn't a group that's built-in on Win2k
Server. Am I missing something simple?

As far as the registry goes, I did what you suggested,
but find it impossible to sift through the 2000+ registry
reads and/or changes that occur when the program I
mentioned launches.

Any other suggestions you, or anyone else, may have would
be appreciated.

Eric
 
Back
Top