A Podcast about Windows PowerShell.
In This Episode
We have a great show for you guys today. Several weeks back we had Jeffrey Snover on the show. We had teased at the time that there was a third portion to the interview that deals with WinRM and WS-MGMT. We’re going to play that today for you. Also on tap: news, resources, and a bunch of PowerShell tips for you.
News
The news is sponsored by Sapien Technologies.
- BGShell now has a Codeplex page
- Microsoft Forefront 2008 (code-named Stirling) looks to be built on PowerShell. Here’s a blog post.
- PowerShell Plus supports the new CTP2 STA feature
- This is big because it allows for you to play with all of the new WPF stuff we’ll be talking about later in the show.
Interview
Admin Script Editor provides a true integrated scripting environment for
PowerShell. Advanced features include an integrated PowerShell debugger,
advanced code generating tools for Active Directory, Databases, XML files
and more. Let’s not forget about the exclusive PowerShell forms designer.
What’s coming up? Soon its innovative and feature-rich ScriptPackger tool
will offer support for the dynamic installation of cmdlets! Come see for
yourself– Admin Script Editor v3.5 is available for a 45 day trial at
AdminScriptEditor.com.
We hope you enjoy the Jeffrey Snover clip on Win-RM and WS-MGMT.
Resources
- Very cool (and important) series on PowerShell & WPF from James Brundage on the Powershell Team blog. Read this one first, he explains the rationale behind focusing on WPF: PowerShell and WPF: WTF
- WPF & PowerShell – Part 1 ( Hello World & Welcome to the Week of WPF )
- WPF & PowerShell – Part 2 (Exploring WPF (and the rest of .NET) with Scripts)
- WPF & PowerShell — Part 3 (Handling Events)
- WPF & PowerShell — Part 4 (XAML & Show-Control)
- WPF & PowerShell – Part 5 ( Using WPF & PowerShell Modules)
- WPF & PowerShell – Part 6 (Running Functions in the Background)
- Beware the custom console. Kirk Munro does a great job of explaining the problems that can result from custom consoles.
- Disturbing hint seen on “The Industry Insiders” MSDN blog about a possible SQL Server 2008 “closed console”. Go leave feedback on the blog post and voice your opinions.
- Slides from a presentation that Keith Hill gave to a local user group to which he’s a member.
- Here’s an excellent post from Joel at HuddlesMasses.org in which he goes into great detail about regarding the new Modules feature in CTP2. He’s figured out a ton of stuff which is not documented anywhere else yet so be sure to check it out.
- Here’s a link to Jaykul’s (whose real name is Joel–not Jaykul!) Select-Grid script.
- Speaking of TechEd earlier, Carter from VMware on the VI PowerShell blog has posted an entry with code and a video of a demo he’ll be showing at TechEd.
- Don Jones has an article in the latest TechNET magazine where he talks about different output types
- Also on VMware, Brandon Shell has put up a few screencast demos in a new “Playing around” series he’s doing on the BSonPosh blog. The series is not exclusive to VMware, he also talks about Citrix, AD and more.
- Video 1: Intro to VMWare VI Toolkit for Windows
- Video 2: Controlling VMWare VMs with VI Toolkit
- Video 3: Vmotion with VI ToolKit
Tips
- A basic tip on using the backtick character to escape in a string. From Richard Siddaway’s blog
- watch out for strings that look like collections
- From Oisin and his blog Nivot Ink: Manipulating remote SharePoint Lists with PowerShell. The article is from late February but it came up earlier this week on the #powershell IRC channel (irc.freenode.net).
One-Liner
$a = (get-clipboard).split(“`n”).trim()
Get Involved!
- We love feedback. You can tell because we ask for it at the beginning and end of every show.
You can reach us by email to feedback@powerscripting.net. Also, please write reviews and vote for us on iTunes, Podcast Alley, Digg, and other podcast portals you use. And blog comments are great, too. - Don’t forget to visit www.quest.com/powershell to get the free book offer (while supplies last).
- Other ways to interact with us:
- Facebook Group (forums, networking)
- Twitter (jonwalz & halr9000)
- IRC: #powershell on irc.freenode.net (web client available on powershelllive.com/irc)
CLICK HERE TO SUBSCRIBE!
Thanks for the props Hal. I’m actually in an email discussion with the PM and lead developer from the SQL team right now about my issues with the closed console. Loud alarms were ringing in my head when I discovered that a few weeks ago. Hopefully they’ll be persuaded to go with the command-line switches and standard console approach instead by RTM.
–
Kirk Munro [MVP]
Poshoholic
http://www.poshoholic.com
I have to say Win-RM and WS-MGMT sound really cool!
Concerning SQL 2008 the only reason I can think of is security, as in allowing a “full powershell” session to touch the database would be a security risk. Taking that to the next level you could say that you don’t trust the host you are administering the SQL server from. My suggestion would be that you shouldn’t administrer the host from a machine you don’t trust.
Kirk, did they give any reason?
I didn’t hear back directly from Michiel (the team lead for the PowerShell work in SQL Server), however he posted his response as a number of us PowerShell MVPs were pushing them about this. Here is a link to the details from the horses mouth:
Michiel Wories’ WebLog : SQL Server Powershell is here!:
http://blogs.msdn.com/mwories/archive/2008/06/14/SQL2008_5F00_Powershell.aspx
I just posted a comment on that blog just now expressing my concern with shipping sqlps.exe as is today. Hopefully he’ll let it through and reply in his comments as he has to others who expressed concern. And if you are concerned about this mini-shell, tell Michiel about it in the comments on that blog post!