Automating the world one-liner at a time…
The MVP summit started yesterday and we meet with our MVPs today. This is one of my favorite events of the year. MVPs are people in the community that are very active (and helpful [yes - they look at both :-)] ) in a particular technology community. We get them all together each year and have a good exchange of ideas. We tell them what we are doing and where we are going and they give us great feedback. MVPS are in invaluable source of real-world feedback on our technology.
I'm really excited this year because I'm co-presenting a sort of "State of PowerShell" talk with Kenneth Hansen. Ken took the lead on the deck and I'm really excited by the approach he took. There are a number of "big picture" things that Ken and I have discussed that we don't think other people see and we've trying to figure out how to communicate these. I reviewed the deck with Ken on Friday and I think he has done a great job presenting those ideas. It is one of those "behind the scenes" talks where we discuss what the problem is, our approach, where we are and were we are going. Hopefully this is one of those talks where people walk away saying, "NOW I understand why you did that".
MVPs are great because they'll tell you if you are being incoherent or obvious. An honest mirror is both difficult to find and extremely valuable. We'll find out today as we give the talk at 9.
Experiment! Enjoy! Engage!
Jeffrey Snover [MSFT] Windows Management Partner 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
Total foobar. Maybe an MVP can help MS, does NOT seem to be able to....
I started out my career in a UNIX env. and always missed a real shell language in windows. PS came out & and thought, 'finally after all these years', so I installed 1.0. Bad decision...it turns out or at least as I understand this post (http://support.microsoft.com/kb/92613)
because if you install a Windows service pack as an upgrade after you install Windows PowerShell 1.0, you cannot uninstall Windows PowerShell 1.0.
So, that means if you have upgraded a gazillion computers in your env. you will have to roll ALL the uprades back!!! Or at least that is my understanding from what I have read. Sigh, everything was so much easier in the UNIX world. I could install/uninstall different shells with ease.
My experience of rolling out an upgrade will be break a bunch other things. Last time resulting is a low level format, reinstall the OS and all the applications. grrr!!!
Tell me there is another way to get rid of Powershell 1.0.
And I was just about to promote getting rid of Perl as our sysadmin tool of choice. BTW, you can install/uninstall Perl repeatedly without problems.
Why does everything in Windows have to be so foobar?
Once again a discouraging Windoze experience
Are the slides going to be posted by chance?
Psst... Keep me in mind if a MVP slot opens up. :) I'm a former Tablet PC MVP and kinda dropped off the face of the earth for a year. When I re-emerged I decided I'm focusing on PowerShell.
And to the commenter above: You can indeed remove PowerShell 1.0. I think the uninstaller just gets a little confused. The uninstaller can be invoked manually. I believe the location is:
Hey guys I'm using powershell a lot and I would like to give some Ideas for future development to the Powershell team, how can I do that, UI stuff, thanks.
Thanks for the hint Josh but alas I had already ventured there.
Here's quote from a post that pretty much sums up my situation
1) After checking show updates there is not a powershell or windows hotfix
listed in the add remove programs.
2) in my C:\Windows directory there is not a $NtUninstallKB926139
3) There is not a powershell directory in my system32 folder
4) there is not a powershell directory in my registry under
When i download the install [note: they are referencing the 2.0 version] it still tells me I need to uninstall previous
version before I can install this one!!!
WTF!!! this is so frustrating.
To me this indicates a lack of cohesiveness and synergy between groups at MS. I was really starting to like powershell but this has put a damper on my enthusiasm for installing on other machines. I guess I just have to wait until it is part of the official environment.