Sign in to follow this  
Followers 0
Guest BigTony

Registry Key Permissions

4 posts in this topic

I have several applications that work fine in Windows 2000 if the user has admin or power user rights. With may of these applications if I just change the program's Registry key permissions (give everyone full control) they work fine for "users". Is there a way to script these changes? :ph34r:

Share this post


Link to post
Share on other sites



I have several applications that work fine in Windows 2000 if the user has admin or power user rights.  With may of these applications if I just change the program's Registry key permissions (give everyone full control) they work fine for "users".  Is there a way to script these changes? :ph34r:

Look for a commandline utility called setacl.exe.

It can change File/Registry permissions.


Visit the SciTE4AutoIt3 Download page for the latest versions        Beta files                                                          Forum Rules
 
Live for the present,
Dream of the future,
Learn from the past.
  :)

Share this post


Link to post
Share on other sites

Cool this will save me tons of work - thanks so much for the fast reply.

Share this post


Link to post
Share on other sites

Why not using runas !!!

RUNAS USAGE:

RUNAS [ [/noprofile | /profile] [/env] [/netonly] ]

/user:<UserName> program

RUNAS [ [/noprofile | /profile] [/env] [/netonly] ]

/smartcard [/user:<UserName>] program

/noprofile specifies that the user's profile should not be loaded.

This causes the application to load more quickly, but

can cause some applications to malfunction.

/profile specifies that the user's profile should be loaded.

This is the default.

/env to use current environment instead of user's.

/netonly use if the credentials specified are for remote

access only.

/savecred to use credentials previously saved by the user.

This option is not available on Windows XP Home Edition

and will be ignored.

/smartcard use if the credentials are to be supplied from a

smartcard.

/user <UserName> should be in form USER@DOMAIN or DOMAIN\USER

program command line for EXE. See below for examples

Examples:

> runas /noprofile /user:mymachine\administrator cmd

> runas /profile /env /user:mydomain\admin "mmc %windir%\system32\dsa.msc"

> runas /env /user:user@domain.microsoft.com "notepad \"my file.txt\""

NOTE: Enter user's password only when prompted.

NOTE: USER@DOMAIN is not compatible with /netonly.

NOTE: /profile is not compatible with /netonly.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0