I have a W2KServer that is always locally logged in as "admin" and uses InCD for a weekly backup task. That all works fine.
I find that whenever non-admin Terminal Services clients logon, they "usually" get lousy performance and the processes list shows a second copy of InCD.exe running at 99% of the CPU. Terminate the task, and everything is fine.
These terminal services users don't need InCD services, and the manual process termination is sometimes difficult due to the slow response - and a lot to ask of an unsophisticated user.
InCD appears nowhere in any startup folders, and one copy of "InCD File System Service" is listed under services, but it isn't obviouly configurable...
Any ideas?
I find that whenever non-admin Terminal Services clients logon, they "usually" get lousy performance and the processes list shows a second copy of InCD.exe running at 99% of the CPU. Terminate the task, and everything is fine.
These terminal services users don't need InCD services, and the manual process termination is sometimes difficult due to the slow response - and a lot to ask of an unsophisticated user.
InCD appears nowhere in any startup folders, and one copy of "InCD File System Service" is listed under services, but it isn't obviouly configurable...
Any ideas?
