lsass.exe,cmrss.exe,smss.exe

[SlowCoder]

What are the ramifications of using as a name for a program? Processes named lsass.exe,cmrss.exe,or smss.exe are protected by the Task Manager, and can't be terminated from the Task Manager. They all run under the SYSTEM user. In testing I found that naming a user process any of these didn't appear to cause any problems, and the process executes under the current user. Logging off seems to properly terminate the user process.

So, after all that, what are the ramifications of naming a process (executable) any of these?

[ɹəuəllıʍ ʇɐb]

You can name a program anything you want, as long as you don't replace the existing ones. Also make sure that they are not in the PATH before the existing system programs. At the end the only thing that remains is the possible confusion - what is what? So better use a unique name for every program.

[SlowCoder]

You can name a program anything you want, as long as you don't replace the existing ones. Also make sure that they are not in the PATH before the existing system programs. At the end the only thing that remains is the possible confusion - what is what? So better use a unique name for every program.

The utility wouldn't be replacing them. Just "borrowing" their name.

I work in education (K-12), and since the advent of 2000, it is very easy for a user to open the Task Manager, and pretty much force-terminate any process, save the ones listed. I write various utilities that monitor certain aspects of students actions, and the kids are pretty smart, and can sometimes figure out how to terminate the programs. As far as I know, there' s no way to keep that from happening. So, this is my latest idea.

[random/random]

Why not just disable task manager?

E.g., using this regfile : http://www.kellys-korner-xp.com/regs_edits...gerdisable2.reg