PowerShell 2.0 for Windows Server 2008 R2

This post is simply a brief moan about a particular instance of poor documentation on Microsoft’s web sites, and an attempt to fill that gap.

I’ve been reading the Pragmatic Programmer which advocates learning new languages on a regular basis, and also learning your computer’s shell language instead of just relying on the GUI.  I’ve dabbled in a bit of PowerShell and I have a sense of how powerful it is for manipulating SharePoint, SQL Server, the Windows OS, and anything else you might like to manipulate with script, but haven’t made the time to really learn it, so I thought that would be a great way to apply those recommendations.  So I thought I’d get onto by Windows Server 2008 R2 development VM and download the latest version of PowerShell (2.0). 

That’s why I thought I’d write this quick post.  If you followed the above thought process, you might experience the same confusion I did as a PowerShell newbie.

You might run across pages like this one (which I found useless, not least of which was because it talks about running SCONFIG.CMD, which is supposed to just be installed on your Win Server 2008 box by defult, but apparently isn’t):

http://support.microsoft.com/kb/976736

Or messages like the post shown on this page:

WinMgmtFrame

Huh?  I’m running Windows Server 2008 R2, why is it telling me to go to the Windows 7 Solution Center?  (And if you go there, you’ll find that’s not helpful).

Anyway the answer is found on this page:

http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_programs/powershell-v2-missing-in-ultimate-x64-v1-only/f614919f-a427-47b2-b220-4ed8dc29b415

(The answer being, if you simply launch the PowerShell icon and issue the “get-host” command, you find that PowerShell 2.0 is installed on Windows Server 2008 R2 by default, so there’s nothing you need to do).

And some more info (and a refreshing Microsoft admission that they themselves are responsible for the confusion):

http://blogs.msdn.com/b/powershell/archive/2010/05/14/powershell-v2-is-available.aspx

I do agree with some of the comments on that page.  Dear MS, if you’re going to rename a product (e.g. renaming “PowerShell” to “Windows Management Framework”, or at least rolling PowerShell into this larger “suite”), how about a little bit better documentation and more consistency on MSDN and/or TechNet?  Like something that comes up easily in search engines.  I tried searching in Bing on the MSDN or TechNet sites for a simple phrase like “PowerShell Windows Server 2008 R2” and found the search results were fairly useless.  Maybe we’re spoiled in this age of search engines, but it did seem to waste at least a half hour of my life, which seems a slightly high price to obtain a simple fact.  Maybe this post may someday save somebody else a half hour.

Now let’s see, where was I… oh yeah, I wanted to start learning PowerShell!  ;-)

Comments

Post a Comment

Popular posts from this blog

Parsing MSTEST results (.trx files) programmatically (in C#)

  Hello, it’s been quite awhile since I’ve posted anything; I’ve been quite busy.  I just felt like sharing this.  This is an extension of other people’s ideas, but I’ve taken it slightly further and thought it might be useful to somebody. I came across a situation where I needed to programmatically examine a .trx file for specific strings.  The .trx file was large (31MB) because it contained the output of around 5000 unit tests.  Around 800 of those tests were failed tests, and they were failing for a specific reason (which is not important now).  The point is, I wanted to programmatically examine the error messages that were being output, and do something (which is also not important now), based on certain strings that might be found in the error message of each failed test. Searching led me to this post in Rasheed’s blog , which was a great starting point for what I wanted to do.  As described in that post, first I had to: Use XSD.EXE (see MSDN here ) to generate classes bas
Read more

The description for Event ID ( 3 ) in Source ( TFSShellExt ) cannot be found.

So I’ve been on a few projects for my employer Hitachi Consulting UK .  For one of them, the client was maintaining the TFS server.  At some point I finished my work on that project and moved on to other projects.  But for some reason I couldn’t get rid of the reference to the TFS server.  Visual Studio kept trying to connect to it when I would launch Visual Studio 2010, and it was failing to connect because I was no longer authorized to hit that URL, because I’m no longer on the project.  This would lead to errors in the Windows Application log that looked like the one described in this post . I tried to clear the cache (by deleting the cache folder) as described in the aforementioned post, and also here .  But every time I tried to delete it the cache folder kept coming back.  It seems to have something to do with TFS Power Tools. In the end what solved it for me was deleting the Cache folder, running Task Manager, killing the two processes “TfsComProviderSvr.exe”, then re-bootin
Read more

Request.Browser.IsMobileDevice

It's known that the .Net framework's "Request.Browser.IsMobileDevice" is not entirely reliable in all cases as evidenced by the fact that our MVC2 site wasn't correctly detecting Android as a mobile, and as evidenced by some hits you can see in this search: http://www.bing.com/search?q=request.browser.ismobiledevice&src=IE-SearchBox&FORM=IE8SRC If we really want reliable mobile detection we need to incorporate the WURFL database (a giant XML file of every mobile device - see http://wurfl.sourceforge.net/ ) and from what I’ve seen, the preferred implementation of this for .Net appears to be “51degrees.mobi” … http://51degrees.codeplex.com/ On the MVC2 project I’ve been working on recently, I was using 51degrees.mobi in development; it seemed very effective, and you can do incredibly granular detection with it, but was a bit heavyweight for my particular project, the requirements of which were (in the case of mobile detection) simply to detect wheth
Read more