Hey bud. I will read the code when you clean it up alittle [Wink] thanks for the links too !

Heres the scoop. The information I recieved about there being a hack for NETDOM and NT4 was incorrect. I have it from good authority that NETDOM 5 will not (under any circumstances) run under NT4 ... this I proved myself today, by replacing some key DLL's and having the machine blue screen on me on reboot [Wink] (true).

Just by way of some background, we want to write a script that will be pushed to our NT4 workstations (by Tivoli) and have the workstations automatically joing AD *and* join into the proper workstation OU.

This is my plan then ... NETDOM 1.8 will run on NT4 and it will join an NT4 workstation to the AD domain - however, 1.8 does not support the /OU switch ... 1.8 will join the wkstn to the default OU for computers only. Figure that with a little bit of KIX/ADSI scripting, can have the wkstn perform a AD move from the default OU to its HOME OU ... will have to provide credentials to ADSI to do this, we will see how reliable that is.

Plus, have also heard rumours that NETDOM 1.8's JOINDOMAIN feature is (to put it mildy) un-reliable [Frown]

[ 07. August 2003, 01:23: Message edited by: Shawn ]