Bryce,

What exactly do you mean when you say

"do an ADSI task on a remote NT4 computer"

you mean, for example, if you were to run a script on your w2k wks that enumerated all services on an NT4 domain controller, it would fail. And installing ADSI on your DC fixed the problem ? Like Erik, said (and I know you know this) ... the whole purpose of the WinNT service provider is to provide backward-compatible support for NT ... no ADSI need be installed (on the "target" machine) ... this is very perplexing ?

Same with Mark's problem .. very weird ... so Mark - in your example, ADECCO is your domain name ?

-Shawn