Comments on: Windows 7 is Missing NETDOM.EXE

By: WT

WT — Wed, 11 Aug 2010 18:01:30 +0000

I found that if you copy \sytem32\netdom.exe and \system32\en-us\netdom.exe.mui from a machine where you installed RSAT (only the AD tools) to the same location on any other machine (win7) that netdom will run fine. I did not try to mix 32/64 bit so I can’t comment on interchangebility. Anyway this let me continue using the methodology I had been using, for vista and now win7 ghost and \windows\setup\scripts\SetupComplete.cmd
(no powershell, rsat)

By: Dhiraj

Dhiraj — Sat, 27 Mar 2010 13:45:36 +0000

Good, i have created these two files. domainjoin.ps1 & domainjoin.bat. now when i ran domainjoin.bat, it’s asking for the username/password to run. how can i run it under username/password privileges which i have specified in domainjoin.ps1 file.

By: Boyd

Boyd — Tue, 02 Feb 2010 03:13:05 +0000

Yes... something like this should work:

$credential = get-credential
Add-Computer -DomainName "MY.DOMAIN.COM" -Credential $credential -OUPath ("OU=Computers,DC=MY,DC=DOMAIN,DC=COM")

By: Marka

Marka — Mon, 01 Feb 2010 16:00:34 +0000

Nice script, thanx. But … is there possibility for password prompt within script? Thank you M.

By: Boyd

Boyd — Wed, 09 Dec 2009 17:13:50 +0000

Thanks, I added an update to this post this morning as I stumbled upon netdom.exe after I needed to install some RSAT components for the dsquery and dsadd tools on a server. Thanks for the advice about moving NETDOM as well. I’m also wondering is whether NETDOM is platform (x86 vs. x64) specific. I’ll have to investigate.

By: james p morgan

james p morgan — Wed, 09 Dec 2009 16:10:34 +0000

Windows 7 and Vista both have their own NETDOM.EXE, for 32-bit and 64-bit.

You have to install:

Install RSAT (After you have extracted the tools): (took me awhile to find the link)

http://www.microsoft.com/downloads/details.aspx?FamilyID=7d2f6ad7-656b-4313-a005-4e344e43997d&displaylang=en

start /w pkgmgr /n:%SystemDrive%\Install\RSAT\Windows6.1-KB958830-x86.xml

Enable some RSAT tools (including NETDOM)

start /w pkgmgr /iu:RemoteServerAdministrationTools-Roles-AD-DS-SnapIns;RemoteServerAdministrationTools-Roles-AD-DS;RemoteServerAdministrationTools-Roles-AD;RemoteServerAdministrationTools-Roles;RemoteServerAdministrationTools

You will then have a “c:\windows\system32\netdom.exe” that supports the ‘older’ Netdom syntax.

HOWEVER, IF YOU MOVE THE ‘NETDOM.EXE” FROM THE ‘SYSTEM32′ SUB-DIR IT WILL NOT WORK???!!
IT WILL JUST ‘EXIT’ UPON EXECUTION??

BUT , if you WANT to move it, which i did. you have to do ‘something’ EXTRA.

To whatever sub-dir you move the RSAT NETDOM.EXE to :

1) FOR EXAMPLE, create a sub-dir called : %temp%\EN-US

2) COPY /Y “%SYSTEMROOT%\SYSTEM32\EN-US\NETDOM.EXE.MUI” “%TEMP%\EN-US

Then if you execute NETDOM.EXE from “%TEMP%” you should ‘see’ the familiar ‘help’
messages..

NOTE: I have not, as of Dec 8, 2009 actually TESTED the FULL ‘moved’ NETDOM.EXE functionality,
but WILL in the next day or so,.

ALSO, someone made the comment that if it was moved’ to another compouter it would not work also,
I will verify that statement also.

Hope this helps, as i DONT like the Powershell approach..

J P Morgan james_p_morgan@hotmail.com