Comments on: Windows 7 is Missing NETDOM.EXE http://iboyd.net/index.php/2009/10/23/windows-7-is-missing-netdom-exe/ Sat, 21 Jan 2012 20:35:52 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Fog and windows 7 http://iboyd.net/index.php/2009/10/23/windows-7-is-missing-netdom-exe/comment-page-1/#comment-16458 Fog and windows 7 Wed, 02 Mar 2011 20:47:47 +0000 http://iboyd.net/?p=224#comment-16458 [...] means no AD integration. Here's what I've found. Win7 has NETDOM, it's just not installed. This guy has a pretty good article on how to install it. However, that's only half of the battle because the [...] [...] means no AD integration. Here's what I've found. Win7 has NETDOM, it's just not installed. This guy has a pretty good article on how to install it. However, that's only half of the battle because the [...]

]]> By: Boyd http://iboyd.net/index.php/2009/10/23/windows-7-is-missing-netdom-exe/comment-page-1/#comment-14921 Boyd Mon, 31 Jan 2011 15:52:21 +0000 http://iboyd.net/?p=224#comment-14921 Hi Leleche, Thanks for the heads up about the special characters. I'm sure there are plenty of other people that use special characters for their "domain join" accounts. I'm not sure if the <em>right</em> way to join a domain is through mini-setup, but we've always done it after mini-setup... it just seems to be more reliable. To keep it unattended, I use the <a href="http://technet.microsoft.com/en-us/library/cc766314%28WS.10%29.aspx" target="_blank" rel="nofollow">SetupComplete.cmd</a> file: Thanks for commenting! Hi Leleche,

Thanks for the heads up about the special characters. I’m sure there are plenty of other people that use special characters for their “domain join” accounts.

I’m not sure if the right way to join a domain is through mini-setup, but we’ve always done it after mini-setup… it just seems to be more reliable. To keep it unattended, I use the SetupComplete.cmd file:

Thanks for commenting!

]]> By: Leleche http://iboyd.net/index.php/2009/10/23/windows-7-is-missing-netdom-exe/comment-page-1/#comment-14887 Leleche Sun, 30 Jan 2011 21:43:37 +0000 http://iboyd.net/?p=224#comment-14887 Thanks for posting this script, this worked out great for us at our company. I ended up using it within a Landesk Provisioning script for our Windows 7 deployment. Some of our newer Dell systems (e6410, e4310) do lot properly load a network driver during Mini-setup, and therefore I needed to add the PC to the domain after it was in Windows. The other bonus that this script gives is being able to specify which OU to place the computer, which is great. One note I just wanted to add is that I had to wrap the password in a single quotes because we use special characters that Powershell tries to interpret ($, %). Thanks for posting this script, this worked out great for us at our company. I ended up using it within a Landesk Provisioning script for our Windows 7 deployment. Some of our newer Dell systems (e6410, e4310) do lot properly load a network driver during Mini-setup, and therefore I needed to add the PC to the domain after it was in Windows. The other bonus that this script gives is being able to specify which OU to place the computer, which is great.

One note I just wanted to add is that I had to wrap the password in a single quotes because we use special characters that Powershell tries to interpret ($, %).

]]> By: Boyd http://iboyd.net/index.php/2009/10/23/windows-7-is-missing-netdom-exe/comment-page-1/#comment-12417 Boyd Sun, 12 Dec 2010 05:21:56 +0000 http://iboyd.net/?p=224#comment-12417 Hey Geert, If you call that .cmd file from the command line instead of clicking on it, I don't think you'll be prompted. Regarding the OU path issue, make sure that you're putting the complete OU string between parentheses. You may also want to verify that your OU string is complete and correct. Remember, it needs to include your domain, like this: -OUPath ("OU=Computers,DC=MY,DC=DOMAIN,DC=COM") If it still doesn't work, let me know! Hey Geert,

If you call that .cmd file from the command line instead of clicking on it, I don’t think you’ll be prompted.

Regarding the OU path issue, make sure that you’re putting the complete OU string between parentheses. You may also want to verify that your OU string is complete and correct. Remember, it needs to include your domain, like this:
-OUPath (“OU=Computers,DC=MY,DC=DOMAIN,DC=COM”)

If it still doesn’t work, let me know!

]]> By: Geert Vervoort http://iboyd.net/index.php/2009/10/23/windows-7-is-missing-netdom-exe/comment-page-1/#comment-12303 Geert Vervoort Thu, 09 Dec 2010 15:02:06 +0000 http://iboyd.net/?p=224#comment-12303 Oh and I forgot, the /OU parameter failes to put the computer in the correct OU, possible because there is a space in OU "Site brussel", how do I go about fixing this? Oh and I forgot, the /OU parameter failes to put the computer in the correct OU, possible because there is a space in OU “Site brussel”, how do I go about fixing this?

]]> By: Geert Vervoort http://iboyd.net/index.php/2009/10/23/windows-7-is-missing-netdom-exe/comment-page-1/#comment-12302 Geert Vervoort Thu, 09 Dec 2010 14:24:15 +0000 http://iboyd.net/?p=224#comment-12302 Hi Boyd, Very useful page, thanks! I created a .cmd file as in the article, including lowering the executionpolicy to unrestricted. But, powershell still deems it necessary to warn me about the possible harm that could be done running the script, and it prompts me if I really want to continue. So it still requires user intervention. Is there a way to avoid this message and thus the prompt to continue or not? Hi Boyd,

Very useful page, thanks!
I created a .cmd file as in the article, including lowering the executionpolicy to unrestricted.
But, powershell still deems it necessary to warn me about the possible harm that could be done running the script, and it prompts me if I really want to continue.
So it still requires user intervention. Is there a way to avoid this message and thus the prompt to continue or not?

]]> By: Darren Townley http://iboyd.net/index.php/2009/10/23/windows-7-is-missing-netdom-exe/comment-page-1/#comment-10122 Darren Townley Wed, 20 Oct 2010 19:32:36 +0000 http://iboyd.net/?p=224#comment-10122 I am new to Powershell and scripting. I am using the above script with an answer file to join our domain. We install a lot of new PC's and I am trying to find a way to delete this script after the computer joins the domain. The script is in a syspreped image. I also am trying to find a way to join the domain on top of an existing computer account or delete the existing account before joining the domain. We do a lot of re-imaging of our computer labs. This is why I would like to join on top of an existing account. We use to be able to do this with a .vbs script with xp and Vista. We are now using windows 7 and want use Powershell to do this. I am new to Powershell and scripting. I am using the above script with an answer file to join our domain. We install a lot of new PC’s and I am trying to find a way to delete this script after the computer joins the domain. The script is in a syspreped image. I also am trying to find a way to join the domain on top of an existing computer account or delete the existing account before joining the domain. We do a lot of re-imaging of our computer labs. This is why I would like to join on top of an existing account. We use to be able to do this with a .vbs script with xp and Vista. We are now using windows 7 and want use Powershell to do this.

]]> By: WT http://iboyd.net/index.php/2009/10/23/windows-7-is-missing-netdom-exe/comment-page-1/#comment-7879 WT Wed, 11 Aug 2010 18:01:30 +0000 http://iboyd.net/?p=224#comment-7879 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) 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 http://iboyd.net/index.php/2009/10/23/windows-7-is-missing-netdom-exe/comment-page-1/#comment-5989 Dhiraj Sat, 27 Mar 2010 13:45:36 +0000 http://iboyd.net/?p=224#comment-5989 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. 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 http://iboyd.net/index.php/2009/10/23/windows-7-is-missing-netdom-exe/comment-page-1/#comment-5387 Boyd Tue, 02 Feb 2010 03:13:05 +0000 http://iboyd.net/?p=224#comment-5387 Yes... something like this should work: <pre> $credential = get-credential Add-Computer -DomainName "MY.DOMAIN.COM" -Credential $credential -OUPath ("OU=Computers,DC=MY,DC=DOMAIN,DC=COM") </pre> 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")
]]>