Powershell unable to "see" dnscmd.exe
Solution 1
This sounds like the work of the File System Redirector to me. Are you running on a 64bit OS?
For example, when you make a call to C:\Windows\system32\dnscmd.exe on a 64bit OS using PowerShell (x86), this will be redirected to C:\Windows\SysWow64\dnscmd.exe. The redirection occurs at the point the folder is accessed so even though you are explicitly providing the path to the executable, you'll still be diverted. This can be disabled on the current thread via calls to native Windows APIs or can be avoided through the use of certain variables and aliases.
More information here: http://msdn.microsoft.com/en-us/library/aa384187%28VS.85%29.aspx
Solution 2
Its the File System Redirect, but you can bypass
Instead of
C:\windows\system32
(which the redirector will grab) use
C:\windows\sysnative\dnscmd.exe
Solution 3
What do you get when you execute:
Get-Command dnscmd.exe -CommandType Application
Related videos on Youtube
ChickenSniper
Just another Server admin trying to make things work :)
Updated on September 17, 2022Comments
-
ChickenSniper over 1 year
Am at a complete loss with this one. Recently a number of my powershell scripts have started failing as they are unable to find the command dnscmd.exe.
What has me at a loss is that the executable exists and works and I can run it just fine in the command prompt. I have tried the following in powershell to run the command:
- dnscmd
- & dnscmd
- & dnscmd.exe
- & c:\windows\system32\dnscmd.exe
All return "The term dnscmd is not recognized as the name of a cmdlet, function,script file or operable program...."
Can anyone enlighten me as to why powershell is completely unable to see the command, where the normal command prompt/windows explorer etc.. can? Using powershell 2.
-
tony roth almost 14 yearsare you sure that you have the dns admin tools loaded on "this" particular workstation/server?
-
ChickenSniper almost 14 yearsYep, I can confirm the admin tools are installed. I run them just fine from the command prompt on the same machine.
-
ChickenSniper almost 14 yearsGet-Command : The term 'dnscmd.exe' is not recognized as the name of a cmdlet, function, script file, or operable progr am. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
-
ChickenSniper almost 14 yearsJust a link to a screenshot - dl.dropbox.com/u/8408796/dnscmd.JPG Confirmed that c:\windows\system32\ is in the powershell path.
-
ChickenSniper almost 14 yearsoddly the Windows 7 & Windows Server 2008 machines I am testing this on do not recognise the SysNative alias. Any thoughts on why this may occur? :)
-
ChickenSniper almost 14 yearsScratch that - found out it was because I was running 64 bit Powershell, and not 32, which meant the Wow64 layer was not kicking in.
-
Falcon Momot over 10 yearsYou could also add the folder it is in to the path variable.
-
FooBee over 9 yearsThis is a very old question and it has an accepted answer. Also, your solution doesn't fit the problem, as the DNS tools were installed, they just disappeared. See the accepted answer and the comments to the question.
-
Anchal Sarraf over 3 yearsYou saved my day. Thank You so much. This worked : C:\windows\sysnative\dnscmd.exe