The ADSM server for Win NT runs in real NT threads;
to see this add the "Threads" display to the task manager.
My currently quiet ADSM server running on NT is, in fact, using
33 threads.  The number varies, and averages around 30.
This system is a uniprocessor, by the way.

And, there are many references that NT threads can be
scheduled to run simultaneously on different processors
in a multiprocessor system.  You don't have to do anything
special to get this to happen; it is part of the original NT
design (see Inside Windows NT by Helen Custer for a
thorough discussion of thread scheduling and MP
synchronization in the NT kernel).

Finally, if you watch an NT system where ADSM is
busy and nothing else is running, you will see in the
performance monitor that the CPU usage in a multiprocessor
is about the same over a reasonable window (10s of seconds).
We have configured many multiprocessor NT systems
over the last year and have observed this expected behavior.

So, the answer is, ADSM on NT takes advantage of
multiprocesors now.

I'm not from IBM.

John Sorensen
SSSI