E
eselk2003
I'm working on a new application that a parent may want to install,
and that they would not want their kids to be able to uninstall. I
can't go in to many more details than that.
Unfortunately there is still a HUGE amount of software out there that
will not work correctly if we force the user to make their kids run
under a non-admin account, in XP or Vista, so we don't want to require
them to do this. However, if the child is running as an admin, is
there really any way we could stop them from uninstalling/disabling
our application? An admin has full access to everything on the PC,
right?
I know we could make it pretty dificult, by doing things that are
typical of viruses or spyware programs, like injecting our code in to
system process, or replacing system DLLs, etc... but what I'm looking
for is a documented and recommended method for one admin user to be
able to install something and then prohibit any other user (even
admins) from removing it. I'm not writing spyware, really.
I suppose what I'm looking for may be some type of custom permissions
provider, that for example would not allow an admin user to adjust
permissions on certain objects (files and registry settings) or
terminate certain processes.
I'm a programmer, but I'm asking this question here because I'd also
like to know about any non-programming options.
and that they would not want their kids to be able to uninstall. I
can't go in to many more details than that.
Unfortunately there is still a HUGE amount of software out there that
will not work correctly if we force the user to make their kids run
under a non-admin account, in XP or Vista, so we don't want to require
them to do this. However, if the child is running as an admin, is
there really any way we could stop them from uninstalling/disabling
our application? An admin has full access to everything on the PC,
right?
I know we could make it pretty dificult, by doing things that are
typical of viruses or spyware programs, like injecting our code in to
system process, or replacing system DLLs, etc... but what I'm looking
for is a documented and recommended method for one admin user to be
able to install something and then prohibit any other user (even
admins) from removing it. I'm not writing spyware, really.
I suppose what I'm looking for may be some type of custom permissions
provider, that for example would not allow an admin user to adjust
permissions on certain objects (files and registry settings) or
terminate certain processes.
I'm a programmer, but I'm asking this question here because I'd also
like to know about any non-programming options.