Every now and then we see a prockees.exe process active which seems to be part of indicium.
Can anyone tell me what this thing does? It also seems to start on a certain trigger, but we are unable to determine what trigger that is, because it’s not always active.
It also looks like there is only one prockees process active per server although we are running multiple indicium services per server. Does this impact the service due to the prockees process not being bound to a specific service (i.e., performance or environment separation).
Thanks in advance
Best answer by Tim WaalewijnView original