In said:Does anyone know how to run a process as the SYSTEM user account?
I am doing some registry modifications that are being blocked when
the code is run as Administrator.
In said:Does anyone know how to run a process as the SYSTEM user account?
I am doing some registry modifications that are being blocked when
the code is run as Administrator.
run under the System account. Once it is up runI am doing some registry modifications that are being blocked when the code
is run as Administrator.
Ed
----
Ed,
Use the AT command to schedule CMD.EXE to run interactively. This will
account. You can use the Processes tab on TaskRegedit.exe from this CMD window and it will also run under the System
Manager to confirm this.
Bill Peele
Microsoft Enterprise Support
run under the System account. Once it is up runI am doing some registry modifications that are being blocked when the code
is run as Administrator.
Ed
----
Ed,
Use the AT command to schedule CMD.EXE to run interactively. This will
account. You can use the Processes tab on TaskRegedit.exe from this CMD window and it will also run under the System
Manager to confirm this.
Bill Peele
Microsoft Enterprise Support
that cannot be done under Administrator, simply because that is one of
the safety mechanisms in place to prevent horrible mistakes. <G>
that cannot be done under Administrator, simply because that is one of
the safety mechanisms in place to prevent horrible mistakes. <G>
In said:run under the System account. Once it is up run
account. You can use the Processes tab on Task
That would be fine ... only that I am calling a DLL from
InstallShield that modified registry keys for some hardware device
install/uninstalls. There is no explicit uninstall INF or
hardware drivers that I can find in the various Microsoft MSDN
SDK's and API's ... I find that if I manually remove the driver
keys that are created by the hardware device installation then the
device no longer appears in the hardware enum. However, these
registry keys, although owned by Administrator, have access rights
for SYSTEM (obviously to prevent accidental deletion).
Since we would like to be able to uninstall our device and we need
to be able to do this from within running C++ code what I am
digging for is a programmatic way to do this rather than a
command-line way to do this.
In said:run under the System account. Once it is up run
account. You can use the Processes tab on Task
That would be fine ... only that I am calling a DLL from
InstallShield that modified registry keys for some hardware device
install/uninstalls. There is no explicit uninstall INF or
hardware drivers that I can find in the various Microsoft MSDN
SDK's and API's ... I find that if I manually remove the driver
keys that are created by the hardware device installation then the
device no longer appears in the hardware enum. However, these
registry keys, although owned by Administrator, have access rights
for SYSTEM (obviously to prevent accidental deletion).
Since we would like to be able to uninstall our device and we need
to be able to do this from within running C++ code what I am
digging for is a programmatic way to do this rather than a
command-line way to do this.
I do have "command-line" ideas (regini.exe for one), but
unfortunately none using the APIs. Can we assume you've been to
various developers groups (or MSDN) for assistance?
I am guessing, but it seems you know exactly what you need to do and
where (change and propagate registry ACLs in order to enable deletion
of a key), but not how (programmatic) to do it. And it does not
appear to me to be a "key locked by a process" issue but one of
default permissions. Good luck.
I do have "command-line" ideas (regini.exe for one), but
unfortunately none using the APIs. Can we assume you've been to
various developers groups (or MSDN) for assistance?
I am guessing, but it seems you know exactly what you need to do and
where (change and propagate registry ACLs in order to enable deletion
of a key), but not how (programmatic) to do it. And it does not
appear to me to be a "key locked by a process" issue but one of
default permissions. Good luck.
In said:I have searched the MSDN library relatively thoroughly (for a
software developer with 8+ yrs exp)
Yes that is correct ... however you cannot open the key with
Administrator in order to add Admin to the ACL user rights for
that key object ... a chicken and egg thing ... whereas if you
were able to run the DLL or call the DLL from a process that had
SYSTEM rights then it would work ... hmmm can you use the command
line to call an EXE that is just a dummy to call the DLL? The
problem is that the uninstaller DLL is called directly from within
the InstallShield uninstaller routine (I used to do alot of
install work).
In said:I have searched the MSDN library relatively thoroughly (for a
software developer with 8+ yrs exp)
Yes that is correct ... however you cannot open the key with
Administrator in order to add Admin to the ACL user rights for
that key object ... a chicken and egg thing ... whereas if you
were able to run the DLL or call the DLL from a process that had
SYSTEM rights then it would work ... hmmm can you use the command
line to call an EXE that is just a dummy to call the DLL? The
problem is that the uninstaller DLL is called directly from within
the InstallShield uninstaller routine (I used to do alot of
install work).