I Understand the a whitepaper exists which explanes that running a
multithreaded application on a Windows 2000 domain controller is a
really bad idea.  I would like
a copy of that paper. Could someone please tell me where I can get a
copy.  Please don't say Microsoft.com.  I can't find anything on that
site.

wow, there are so many multithreaded applications that can run on a
domain controller. i do know of performance implications when a domain
controller is used as an intensive file server but this is the first
time i've heard that multithreaded applications shouldnt run on a
domain controller or are a bad idea especially since a lot of the
other default background services on windows are multithreaded
applications themselved.

As scubapup points out, many system processes run in multiple threads.
This applies to the OS on a domain controller as much as to any other
OS. As such I would suggest that it is impossible not to run
multithreaded processes on a domain controller.

There is a slight issue of semantics as a process is not an
application but, when it comes to using system resources there is no
real difference. Fundamentally, if something is running it is using
resources regardless what it is.

What may exist is something that looks into running intensive
applications as varied as SQL Server or EMule on domain controllers
and details how they affect the response time of the server to
clients.

Guys - Thanks for the input.  Maybe I should have been more clear in
my question.  I beleave that the reason why a multithreaded/
multitransactional app. should not run on a box that is an AD domain
controller IS because a lot of OS and other background stuff running
on the domain controller is multithreaded.  I know that the satelite
network tool I am talking about will not work well on a server that is
a domain controller and works fine on that same server when it is a
member server.  I have seen the white paper I am asking about.  I just
can't currently find it.