While using CMD.exe, I got into a number of bad habits. One of those is the habit of eliminating whitespace for various commands. The problem is that that causes problems with PowerShell. More precisely stated \u2013 it doesn’t work. Here is what you get:\n<\/p>\n
PS> ipconfig\/all In PowerShell, you have to put a space to separate the command name and the parameter (.e.g. ipconfig \/all )\n<\/p>\n I know that and yet time and time again, I type it incorrectly. It is just burned into my head. After having tried to reprogram my brain, I’ve finally given up, accepted my weaknesses and done the following:\n<\/p>\n PS> function ipconfig\/all { ipconfig \/all } Windows IP Configuration<\/p>\n Host Name . . . . . . . . . . . . : jpsdesk10 I put this in my profile so it is always available. I’m still a flawed person, but now I’m a productive flawed person. J<\/span>\n\t<\/p>\n Enjoy!\n<\/p>\n Jeffrey Snover [MSFT] While using CMD.exe, I got into a number of bad habits. One of those is the habit of eliminating whitespace for various commands. The problem is that that causes problems with PowerShell. More precisely stated \u2013 it doesn’t work. Here is what you get: PS> ipconfig\/allThe term ‘ipconfig\/all’ is not recognized as a cmdlet, function, […]<\/p>\n","protected":false},"author":600,"featured_media":13641,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-8741","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-powershell"],"acf":[],"blog_post_summary":" While using CMD.exe, I got into a number of bad habits. One of those is the habit of eliminating whitespace for various commands. The problem is that that causes problems with PowerShell. More precisely stated \u2013 it doesn’t work. Here is what you get: PS> ipconfig\/allThe term ‘ipconfig\/all’ is not recognized as a cmdlet, function, […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts\/8741","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/users\/600"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/comments?post=8741"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts\/8741\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/media\/13641"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/media?parent=8741"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/categories?post=8741"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/tags?post=8741"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
The term ‘ipconfig\/all’ is not recognized as a cmdlet, function, operable p
rogram, or script file. Verify the term and try again.
At line:1 char:12
+ ipconfig\/all <<<<
PS>\n<\/span><\/p>\n
PS> ipconfig\/all<\/p>\n
Primary Dns Suffix . . . . . . . : ntdev.corp.microsoft.com
<\/span>\u2026<\/span>..
\n\t\t<\/span><\/p>\n
Windows PowerShell\/Aspen Architect
Visit the Windows PowerShell Team blog at: http:\/\/blogs.msdn.com\/PowerShell|
Visit the Windows PowerShell ScriptCenter at: http:\/\/www.microsoft.com\/technet\/scriptcenter\/hubs\/msh.mspx<\/p>\n","protected":false},"excerpt":{"rendered":"