I am running Windows Server 2003 R2 Enterprise 64 bit SP2 Integrated, and when I try to run dcdiag to check out possible domain issues I get following. What are the Windows Server 2003 Support Tools? Where can I get them from? The Windows Server 2003 Support Tools are a set of software tools for administrators. Netdom.exe; The Support Tools are not. Windows Server 2003 Support Tools. In Windows XP SP2 Support Tools is a lower number.

Hi together i try to join my computer after the Windows 7 installation. When i use the netdom.exe Tool i got following error. Command: C: Windows system>netdom join%computername% /Domain:education.com /OU:ou=TEST,dc=education,dc=com /UserD:administrator /PasswordD:anything Error Message ===>The procedure entry point I_NetNameValidate could not be located in the dynamic link library NETAPI32.dll. I found the utility djoin.exe, but i don't know if this is the correct utility to join a computer automatic into the domain. Perhaps anybody have experience with this function and can explain the correct syntax and utility. Can I also use netdom.exe with Windows 7 or is this utility no more support on Windows 7?? With best regards.

Hi VistaGuyRay i tried following command: netdom join%computername% /Domain:education.com /OU:ou=TEST,dc=education,dc=com /UserD: education administrator /PasswordD:anything but i got the same error message: The procedure entry point I_NetNameValidate could not be located in the dynamic link library NETAPI32. Tidy Files Label Program. dll. I suppose the problem is only in Windows 7, with Windows Vista ist works perfect. With best regards The ' The procedure entry point I_NetNameValidate could not be located in the dynamic link library NETAPI32.dll.'

Message is caused by the new NETAPI32.dll in Windows 7 which doesn't contain the entry point required. For those who still cannot WAIK methods (join through unattended.xml) due to external factors a) such as requiring VPN/802.1x before network has been established b) 3'rd party deployment solutions You can consider two options; - Use a powershell script to join when network has been established. Command Add-Computer - Deploy NETDOM.exe together with NETAPI32.DLL from Windows 2003 SP2 Deploy the files to a (temporary) destination that doesn't come into conflict with the existsing NETAPI32.dll in Windows 7 system. NETCOM and NETAPI32.dll in the same location should resolve the missing entry point problem - if you have spelled everything correctly that is;) Sincerly, Jon E.