-
Notifications
You must be signed in to change notification settings - Fork 268
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some networking modules are not compatible with Windows 7 #136
Comments
I believe these cmdlets are PSv3 and later, I don't think it's an OS version issue. Ymmv. In general, we've tried to avoid requiring anything later than PSv2, but obviously there are some exceptions. |
I've got PSv4 on my Win7 box but the cmdlets there don't run. The modules do not show up with Get-Command either. |
PS version specific cmdlets, OS specific cmdlets, third-party cmdlets... I can't keep them all straight. Linux's RPM has a --whatprovides so you can find out where a file comes from. It would be nice if PowerShell had something similar. |
Add to that, I think PSv5 will only run on Windows 8.1/2012 family OSs too. |
Make sure you are including the ".ps1" extension at the end of the cmdlet name. |
Some Windows 8+ modules are CDXML based. They can’t be made available on Windows 7 because the underlying WMI classes aren’t available; NetTCPIP is one of those modules. Here is a list of modules that might not work on Windows 7 due to the classes not being available. |
I noticed in a run I did on a Win 7 host, some PowerShell cmdlets are only available to Windows 8.1 / Server 2012 family of operating systems. Below is a copy of the error message.
Get-NetRoutes reports error on localhost: "The term 'Get-NetRoute' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again."
Get-NetIPInterfaces reports error on localhost: "The term 'Get-NetIPInterface' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again."
This article here mentions the use of Net TCP/IP cmdlets:
https://technet.microsoft.com/en-us/library/hh826123%28v=wps.630%29.aspx#feedback
My suspicion is that this may affect Windows 2008 Server OSes also if you try to run those modules. I'm sure there are other ways of getting this information, but wanted to highlight the issue. YMMV.
The text was updated successfully, but these errors were encountered: