Rad,

Thanks for the feedback and information. Very good suggestions which may apply to some Companies out there.

1. I think this LDAP move is only for a computer that is already in the AD.
In our case the Computer is not in AD, it is a freshly ghosted image that we are adding to the AD typically from Workgroup.
If you know or find an ADSI/WMI call that can do it without the need for NETDOM.EXE that would be cool.

2. Not sure about other Companies, but we have 100's and 100's of OUs for Computers. That is why I don't enum them.
For our business unit they typically will only go into 1 of 3 locations, so spending the time to enum all the OUs is not very efficient.
Perhaps someone that is an Enterprise Admin in our Company that might want to do this in any of the OUs might want to use the enum process.
Or smaller Companies.

3. Would really like to find a valid method to add NT 4.0 systems to the AD...
If I can use AD Users and Computers to manually add a computer to an OU and set it to be
assigned to pre-2000 then I would think I should be able to do it in script as well...
Just need to find that method. As you say, if that could be done, then wouldn't need NETDOM.EXE at all [Big Grin]

Thanks again for the feedback Rad. Good ideas.

[ 30. May 2003, 20:22: Message edited by: NTDOC ]