Hi there
I would challenge your first statement and rephrase it as "I have an
application that won't run when the user is logged in as a ordinary user.
Since I don't know what the program is trying to do that causing it to fail,
I resort to making the users members of the Power Users group".
Does that sound more like it? The notion of a restricted administrator or a
restricted power user is really a false one. Oh, and the definition of a
power user? An administrator who hasn't made himself an administrator yet.
Anyway, what you need to do is to find out what the program is doing that it
shouldn't be. Some useful tools here are FileMon and RegMon from
www.sysinternals.com. Install and run these programs and then run the
poorly-written application.
The problem is almost certain to be either file permissions or registry
permissions. Once you've found the files, directories or registry keys that
the program is trying to write to, loosen the permissions on them.
You can use regedt32.exe (note, no "i") for registry permissions (and
Explorer, obviously, for file permissions).
Group Policy also has facilities for changing registry permissions and file
permissions. Otherwise, you can script file permission changes using
cacls.exe (built in) and registry permission changes using regini.exe and
several other (and, frankly, better) tools.
Hope this helps
Oli