WCF Remoting and Thread Priority

The programming task is to run a simulation model, as a distributed
computing model, in the background on 250 departmental computers. I
intend to allocate work (per machine) into say "5-10 cpu second units"
of repetitive work, stealing CPU cycles when/where I can.

I have a service that uses WCF to host a remote object that performs
the allocated work. My objective is to have the installed service run
in the background and have no adverse effect on my users (they'
shouldn't notice the backgrond processing).

At service startup, I successfully can control the base priority using
the following statement(s):

System.Diagnost ics.Process p =
System.Diagnost ics.Process.Get CurrentProcess( );
p.PriorityClass = System.Diagnost ics.ProcessPrio rityClass.Idle;

The service appropriately reports having a "low" base priority in task
manager

However, when I have my remote object report its thread priority using

string priority =
System.Threadin g.Thread.Curren tThread.Priorit y.ToString();

The priority is reported as Normal (process priorityclass still reports
low/idle priority). This happens both when using WCF or the Net 2.0
remoting library to perform the distributed processing. So the thread
that the remote object is running under is running at a higher priority
than the base priority.

What I don't know is
a) Is this normal behavior, or behavior associated say with "remoting"?
b) If normal behavior, will this job have an adverse effect on my
user's computers. That is, would my remote object, noticably impact
the performance of their workstations?

Thank you for sharing you experiences...