New
#1
Runtime Broker quick question
I just noticed there are two Runtime Broker applications in the Component Services DCOM Config. Both are
active. Is this common or do I have a problem. Thanks...
I just noticed there are two Runtime Broker applications in the Component Services DCOM Config. Both are
active. Is this common or do I have a problem. Thanks...
It is normal.
I have {9CA88EE3-ACB7-47c8-AFC4-AB702511C276} and {15c20b67-12e7-4bb6-92bb-7aff07997402}
You are welcome. A more interesting question is why there are 2 (there are lots more but lets forget them).
I don't know the answer to that - perhaps one is supposed to shoot off high priority jobs and the other deals with more background stuff.
RunTime Broker isn't a job - is is more like a job-queue that you put things on to be processed as and when the time comes and there is some time to do it. There are possible permission differences but I can't see that being interesting. Perhaps it is just a mistake and they just got confused with the GUID.
It would be idle speculation on my part but if it was deliberate I'd have expected a different name (perhaps "RunTime Broker II (the sequel)" or "WalkTime Broker") for the lower priority queue.