J
Jay
Here lies my quandry:
I have written a service that makes registry changes.
The problem I run into is that, if I create the service under any
account other than 'User' (i.e. 'LocalSystem', 'LocalService'), access
to the registry is denied. If I create the service under the 'User'
account, any time the user changes his network password (which is
vigorously mandated in my workplace) he must also change it for the
service.
I have done some research, and my best bet seems to be impersonating
the current user, since every user has administrative priveleges.
However, all examples I have located are either in ASP.NET or VB 6.0.
I have written a service that makes registry changes.
The problem I run into is that, if I create the service under any
account other than 'User' (i.e. 'LocalSystem', 'LocalService'), access
to the registry is denied. If I create the service under the 'User'
account, any time the user changes his network password (which is
vigorously mandated in my workplace) he must also change it for the
service.
I have done some research, and my best bet seems to be impersonating
the current user, since every user has administrative priveleges.
However, all examples I have located are either in ASP.NET or VB 6.0.