One for the road: Stepping away from PowerGUI®

Today was one of my most difficult days in my 7½+ year career at Quest Software.  The same week that I was given a performance raise (I got that email on Monday), this afternoon I got a phone call from the director over my business unit letting me know that my position has been cut effective immediately.  Part of a book balancing effort it seems –  funny (or not so much) how life works sometimes.

I’ve accomplished a lot while working at Quest, and spent a ton of professional and personal energy on the company and its products, particularly PowerGUI (far too much energy if you ask my wife, and today I must say I’m tending to agree).

Since I started working with the PowerGUI team at Quest back in 2007 (back in the version 1.0.x days) I have:

  • been awarded the Microsoft MVP award for my community support Windows PowerShell four years in a row
  • received recognition as a Quest Software expert in Windows Management (only 1% of the company employees have received this recognition)
  • provided feedback and direction over the product and its features through 3 major release cycles and many minor releases
  • supported the product and the community as a PowerPack developer, then as a PowerShell Solutions Architect, and most recently as the Product Manager (although I never could get those other positions backfilled so I ended up wearing all three hats most of the time)
  • released dozens of extensions for the product, including PowerPacks for platforms such as Active Directory, VMware, Hyper-V, and Exchange, and Add-ons such as the Script Editor Essentials Add-on or others for specific features such as script signing, transcription, the PowerShell blue console theme, and many more
  • pushed the number of commercial features in PowerGUI Pro from two when I took over as Product Manager to over six in the current version with many more on the way
  • initiated strategic partnerships with key enterprises such as NetApp and Intel and helped them create their own PowerPacks for their platforms
  • helped drive traffic to the powergui.org site through my blog and through social media as we grew the number of downloads from 100000 to over 1.2 million
  • provided feedback and direction to internal teams at Quest with PowerShell support in their products
  • successfully presented well-received PowerShell-focused sessions at many user groups and also at conferences such as Microsoft TechEd, the TEC conference, the PowerShell Deep Dive (a mini-conference in the TEC conference), and TechDays Canada
  • been elected as President for the PowerShellCommunity.org site
  • coordinated and provided direction over the first ever PowerShell Deep Dive conference

Unfortunately, most of that is now a legacy as it came to an abrupt end today.  I’m still a PowerShell MVP, and I will still be involved with the PowerShell community, however my work on PowerGUI has stopped for now.

Before I step back from this though, and before I reorganize/refocus my efforts onto more important things, I wanted to share one more new PowerGUI feature that I recently created for the community that I have spent so much time with these past 4 years.  I still have a strong affinity for PowerGUI and a lot of my heart and soul has gone into this product, and this feature is just a small example of that effort.  The new feature comes as part of the Call Stack Window add-on that I just published in the PowerGUI Add-on library.  Here’s a screenshot showing you what this add-on looks like in action:

PowerGUI Script Editor Call Stack Window

This add-on adds a call stack window to your PowerGUI Script Editor every time you start debugging a script. Working with a call stack while you debug anything beyond the most simple of scripts is essential because it provides you with a list of all nested calls that led up to the current line of script in your debug session. You can use this to determine where functions are being called from by setting a breakpoint inside a function and then walking up the call stack to see the script used to call the function. Also, this window has double-click support, so if you would like to go to any location in the call stack, simply double-click on the location you wish to see and the add-on will take you there, even if the file in question isn’t open at the time.

I was considering putting this feature in the Pro version in a future release, but that is beyond my control now so I decided I’d share what I have today and let you guys have fun with it.  Since I created the feature in this add-on, it’s been an incredibly useful feature to me and I hope you guys enjoy it as well.  To get this Add-on, simply select Tools | Find Add-ons Online in your PowerGUI Script Editor and search for “Call Stack”.

That will most likely be my last PowerGUI-centric post for a while, and it will be my last post for at least a week while I take a much needed vacation before moving on to new things.

Thank you for your continued support through the past four years.  I hope this post finds you well.

Sincerely,

Kirk Munro
Former Product Manager of PowerGUI Pro and PowerGUI

P.S. If you are in need of someone with my skills, either as a Product Manager, a PowerShell MVP, an expert in Windows management (with a strong focus on Active Directory and Exchange although I’ve also gotten deeply involved in virtualization with Hyper-V and VMware as well), a social media/community site manager, or as a freelance writer, my schedule has all of a sudden become much less busy and I’m interested in filling up that time with new work once I come back from vacation, so please get in touch.

PowerGUI® 3.0 Hotfix: Double-clicking on a ps1, psm1, or psd1 file to open the Script Editor shows the Start Page as the active page in the Script Editor

This article describes an issue that was introduced into both PowerGUI and PowerGUI Pro when version 3.0 was released and provides a recommended solution to that issue.

Problem

While the PowerGUI Script Editor is closed, double-clicking on a ps1, psm1 or psd1 file or right-clicking on one of those file types and selecting “Open with PowerGUI Script Editor” will open the file you selected in the Script Editor as expected; however the Start Page will appear as the active tab in the Script Editor instead of the file you opened.

Affected Products

  • PowerGUI 3.0 (freeware)
  • PowerGUI Pro 3.0

Solution

To resolve this problem, a new version of the Script Editor Essentials Add-on has been released.  This version (3.0.0.75) includes a modification to the Script Editor behaviour such that any file you use to open the PowerGUI Script Editor will immediately become the active file.

To install this hotfix, please follow these steps:

If you are connected to the Internet

  1. Open the PowerGUI Script Editor.
  2. Run the following command from the embedded PowerShell console:
    $oldState = $PGSE.Configuration['/CollectAndSendInformation']
    if (-not $oldState) {
        $PGSE.Configuration['/CollectAndSendInformation'] = $true
    }
  3. Select Tools | Find Add-ons Online to show the Find Add-ons Online dialog.
  4. Type “Script Editor Essentials” into the text box at the top of the Find Add-ons Online dialog.
  5. Click on the Search button.
  6. Once the search results are returned, Select the Script Editor Essentials Add-on if it is not already selected.
  7. Click on the Install button to download, install and load the Script Editor Essentials Add-on.
  8. Once the Script Editor Essentials Add-on is installed, run the following command from the embedded PowerShell console:

    if (-not $oldState) {
        $PGSE.Configuration['/CollectAndSendInformation'] = $false
    }
  9. Close the PowerGUI Script Editor.

If you are not connected to the Internet

  1. Open your web browser and browse to http://www.powergui.org/entry.jspa?externalID=2952.
  2. Follow the steps outlined in the “Manual install” section on that page, copying the Add-on.ScriptEditorEssentials.zip between machines as appropriate.
  3. Close the PowerGUI Script Editor.

At this point you should be able to double-click on ps1, psm1 or psd1 files if you file association is set up and have those files open in the PowerGUI Script Editor as the active document.

Feedback

This solution is being provided based on the feedback of users who notified us about the issue two days ago on the forums.  If you have any questions about this solution, please let us know in the forums or in the comments on this post.

Thanks!

Kirk out.

vWorkspace PowerPack: A great example of the power and flexibility you get from PowerShell and PowerGUI®

Last week, the Quest vWorkspace guys showed their prowess once again when they released the first version of the vWorkspace PowerPack for PowerGUI® Pro and PowerGUI®.  I love this PowerPack because it really demonstrates how PowerGUI is so complementary to PowerShell.  To see what I mean, take a look at the following screenshot:

vWorkspace PowerPack - multi-farm management

This screenshot shows two major improvements to the vWorkspace management experience by demonstrating how you can use the vWorkspace PowerPack to perform management tasks across all farms, and by demonstrating how you can use the vWorkspace PowerPack to perform management tasks across all locations in a single farm or across all locations in all farms.  In the native vWorkspace management user interface, you can only work with one farm at a time, and you can only work with one location at a time.

Scaling management tasks out in a product like this can take a long time when you need to build the capabilities into a native management user interface, and these days in many cases PowerShell is provided as the vehicle to satisfy larger scale automation and management needs.  PowerShell is great and it definitely fits the bill for these medium to large enterprise needs, however it does not provide a user interface to facilitate those management scenarios.  This is where the administrative console in PowerGUI Pro and PowerGUI really shines, because it allows you to build out rich PowerPacks with enterprise-ready solutions with very low cost and effort.

I spoke directly with Adam Driscoll (author of PowerGUI VSX, member of the vWorkspace team, and one of two developers who created the vWorkspace PowerPack) about this, and it took them less than one week to put this PowerPack together.  That’s less than one week for two developers to create a rich, functional management user interface that not only provides many of the management capabilities that come with the vWorkspace management console, but that also adds additional enterprise capabilities that the vWorkspace management console does not provide natively.  Aside from the multi-farm management and multi-location management features I mentioned earlier, it also allows administrators to upgrade the vWorkspace VM tools on the VMs you select, and it simplifies how administrators search for provisioning objects like templates, sysprep customizations, parent VHDs, and so on.  And by building these capabilities into a PowerPack, vWorkspace administrators can perform custom filtering and sorting of the data in the grid, generate rich HTML reports for that data, export the data to an external file for use in other programs, and view the PowerShell scripts that are doing all of the work, all because those features come with the PowerGUI administrative console automatically.  That’s an amazing feat for one weeks worth of effort!

The really sweet part of all of this is that it gets even better very soon.  If you’ve been following my blog recently you’ve seen that we have released two betas of PowerGUI Pro 3.0 in the last little while which comes with many great features worth highlighting, however for now I only want to mention one: MobileShell.  In PowerGUI Pro 3.0, you can provide administrators with a custom mobile management solution, defined using PowerPacks and tailored for their needs using role-based access control (RBAC).  That means that once we release PowerGUI Pro 3.0 (which should happen very soon), the vWorkspace guys will be able to publish an update to their PowerPack that enables mobile management support so that vWorkspace administrators can have a mobile management solution for very little cost!  All they will need once the vWorkspace PowerPack is updated to support this mobile management scenario is a license of PowerGUI Pro 3.0 for each administrator who wants to manage their vWorkspace environment from their webkit-enabled mobile device.  Considering that it also allows those administrators to create executable files from PowerShell scripts, work with integrated version control in a best-in-class script editor, manage systems remotely using easy PowerShell remoting capabilities, find functions they are working with using go to definition support for functions, and more, the PowerGUI Pro price of $199/user is a pretty good value.

If you are at all interested in VDI, you should give vWorkspace a look because it’s an awesome solution that keeps getting better all the time.  If you use vWorkspace already I encourage you to take a look at the PowerShell capabilities that this team is providing, particularly in the PowerPack, because a ton of additional value is being provided here that is worth checking out.  You can find the installation instructions for the PowerPack on the vWorkspace PowerPack page on PowerGUI.org.

That’s it for this post.  If you have any questions or feedback, please don’t hesitate to reply in the comments below.

Thanks!

Kirk out.

PowerGUI Pro® 3.0 Beta 2 is now available

Hot on the heels of our first beta cycle for PowerGUI Pro 3.0, today we released beta 2 of PowerGUI Pro 3.0 to the web.  This release includes a lot of fixes and improvements based on the feedback we’ve received from you during our first beta cycle, so thank you for that feedback!

Here are some details about the improvements that have been made in the 2nd beta of PowerGUI Pro 3.0:

Improved snippets hierarchy

Several users indicated that some of our snippets were hard to find.  To resolve this issue, I’ve reorganized our snippets into an improved snippets hierarchy that should make it easier for you to find the snippets you are looking for and learn more about what you can do with PowerShell from our snippet collection.  A special thanks goes out to Denniver Reining, author of the very popular Snippet Manager Add-on.  Denniver was able to provide very useful feedback as I was going through the improvements in this release, which was very helpful.  To browse the new snippet hierarchy, simply press Ctrl+I while editing a document in the Script Editor.  Here’s a screenshot showing the top level representation of the new snippets hierarchy:

PowerGUI Pro 3.0 Snippet Hierarchy

Installer option to open Script Editor

Since the first release of PowerGUI we have provided an option at the end of the installation to open the PowerGUI Admin Console.  This is useful, but myself and many of our users have requested if we could open the Script Editor as well.  With this beta 2 release, you can now open the Script Editor or the Admin Console at the end of the installation.

PowerPack Shared Scripts are now loaded from regular nodes and actions

When you author a PowerPack, you can create a function library inside a shared script for the PowerPack.  This is useful, however until now shared scripts would only load when you clicked on a script node or script action.  This has now been changed so that shared scripts are now loaded from regular nodes and actions, allowing you to keep all of your PowerPack functions in one location and then create regular nodes and actions using those functions.

Performance improvements, usability improvements and lots of bug fixes

In addition to these items, we have improved the performance in some scenarios in MobileShell and in the Script Editor, we have addressed some usability improvements in the Script Editor, the Admin Console and MobileShell, and we have fixed a lot of bugs as well (it is a beta cycle after all, and what good would a beta cycle be if it didn’t include bug fixes?).

Don’t forget all of the new features that were in the first beta!

Besides these changes, if you’re just finding out about the beta of PowerGUI Pro 3.0, make sure you read my other blog post that highlights all of the new features like compiling scripts into executables, or the new MobileShell user interface that allows you to use PowerPacks from your smartphone or tablet – those features and many more were included in the first beta of this release.  If you want to try the awesome new MobileShell capabilities, this blog post will help you get that set up in your test lab: Configuring RBAC for MobileShell in PowerGUI Pro 3.0.

Great, so where can I get beta 2?

Beta 2 is available for download now, in the same location where we posted the first beta.  You can find it on the PowerGUI Pro 3.0 beta page.  When you are installing this beta, you will need to provide a license key.  License keys for the beta are included in the zip file for the beta, right beside the msi and exe installers for the PowerGUI Pro 3.0 components – look for the asc file in the Components folder.

Please share your feedback!

We will be running the second beta for a short period while we work on finishing up this release.  Your feedback is very important during this beta cycle, so please give the beta release a try and share your feedback by posting messages on the PowerGUI forums.  The sooner we get your feedback, the sooner we can respond to it.  I’m really looking forward to hearing what you like, what you don’t like, and what else you would like to see in this and future releases, so please share your thoughts with us.

Enjoy!

Kirk out.

Exciting PowerGUI® news at TechEd 2011 next week!

Next week I’ll be at the TechEd 2011 conference in Atlanta.  During this event I’ll be doing an Ask the Experts session on Tuesday, May 17, 2011 in the Quest Software booth from 12:30-1:00PM.  If you want to get the latest news on PowerGUI® Pro and PowerGUI®, come to that session!  I have some really cool things I’ve been dying to show you, so please stop by and say Hello!  If you can’t make that session, we’ll be demoing PowerGUI Pro all week in the Quest booth, so stop by if you want a quick look at what we’ve been working on.

If you’re wondering where else I’ll be, be sure to take a look at my blog post about PowerShell at TechEd 2011.  It includes sessions I will be possibly attending.  I’m also presenting an interactive session called WSV-473: Windows PowerShell 3.0: Why Wait? Get Next-Generation PowerShell Functionality Today!  If you cannot attend that session, there is a repeat as well: WSV473-INT-R: Windows PowerShell 3.0: Why Wait? Get Next-Generation PowerShell Functionality Today!

Also, why not go to TechEd in style!  Show your appreciation for PowerGUI at TechEd by sporting the latest PowerGUI desktop wallpaper on your laptop!

Hope to see you there!

Kirk out.

Learn more about PowerShell at TechEd 2011

TechEd North America 2011 is coming up fast next month, so I wanted to let you know how you can learn more about PowerShell while at the conference.  PowerShell has continually had a great presence at TechEd events, and this year is no exception.  Just searching the TechEd schedule builder using the keyword “PowerShell” reveals 7 pre-event online webcasts, 2 pre-event virtual labs, 4 pre-con seminars, 2 birds of a feather discussions, 5 interactive discussions, 16 breakouts, and 9 hands-on labs this year!  Those are not all specifically focused on PowerShell, but they definitely show the amount of attention that PowerShell gets at a conference like this.

PowerShell content at TechEd 2011

Below you will find a list of all of the PowerShell-related sessions and resources for TechEd so that you can make sure you have them added to your schedule.  The sessions that interest me the most are highlighted in bold.

Type and Level Title Speaker Date
Pre-event webcast
200 – Intermediate

PRE001-WC | Windows PowerShell Basics for IT Professionals

Peter Lammers Online, available now
Pre-event webcast
200 – Intermediate

PRE020-WC | Windows PowerShell Basics for IT Professionals (Part 2)

Sean Kearney Online, available now
Pre-event webcast
200 – Intermediate

PRE051-WC | PowerShell Week: Learn It Now before It’s an Emergency (Part 1 of 5)

Ed Wilson

Online, available now
Pre-event webcast
200 – Intermediate

PRE052-WC | PowerShell Week: Learn It Now before It’s an Emergency (Part 2 of 5)

Ed Wilson Online, available now
Pre-event webcast
200 – Intermediate

PRE053-WC | PowerShell Week: Learn it now before it is an emergency (Part 3 of 5)

Ed Wilson Online, available now
Pre-event webcast
200 – Intermediate

PRE054-WC | PowerShell Week: Learn it now before it is an emergency (Part 4 of 5)

Ed Wilson Online, available now
Pre-event webcast
200 – Intermediate

PRE055-WC | PowerShell Week: Learn It Now before It’s an Emergency (Part 5 of 5)

Ed Wilson Online, available now
Pre-Conference Seminar
($$$)

PRC14 | Automate Windows 7 (and Windows Server 2008 R2) Administration Using Windows PowerShell v2

Don Jones Sunday, May 15, 10:00 AM – 5:30 PM
Pre-Conference Seminar
($$$)

PRC07 | Microsoft SharePoint 2010 Administration for the Seasoned SharePoint Administrator

Shane Young, Todd Klindt Sunday, May 15, 10:00 AM – 5:30 PM
Pre-Conference Seminar
($$$)

PRC13 | Group Policy in Windows 7 and Windows Server 2008 R2

Jeremy Moskowitz Sunday, May 15, 10:00 AM – 5:30 PM
Pre-Conference Seminar
($$$)

PRC04 | Build a Better Development Shop with Microsoft Virtualization Technologies and Visual Studio 2010 Lab Management

Brian Randell Sunday, May 15, 10:00 AM – 5:30 PM
Interactive Discussion
400 – Expert

WSV471-INT | Build Reusable Tools in Windows PowerShell

Don Jones Monday, May 16, 1:15 PM – 2:30 PM
Breakout Session
300 – Advanced

WSV316 | Windows Server 2008 R2: Tips for Automating the Breadth of Your IT Environment

Dan Harman, Mir Rosenberg Monday, May 16, 3:00 PM – 4:15 PM
Interactive Discussion
400 – Expert

VIR471-INT | Virtualization FAQ, Tips and Tricks

Janssen Jones Monday, May 16, 3:00 PM – 4:15 PM
Birds-of-a-Feather
300 – Advanced

BOF04-ITP | PowerShell: Best Practices from the Field

Hal Rottenberg, Ed Wilson Tuesday, May 17, 8:30 AM – 9:45 AM
Interactive Discussion
200 – Intermediate

OSP273-INT | Microsoft Office 365 Administration and Automation Using Windows PowerShell

Ashwin Sarin Tuesday, May 17, 8:30 AM – 9:45 AM
Interactive Discussion
300 – Advanced

OSP382-INT | Windows PowerShell, the Power of the Pipe

Todd Bleeker Tuesday, May 17, 8:30 AM – 9:45 AM
Breakout Session
300 – Advanced

WCL303 | Advanced Troubleshooting with Resultant Set of Policy (RSoP)

Jeffery Hicks Tuesday, May 17, 1:30 PM – 2:45 PM
Breakout Session
300 – Advanced

WSV310 | Get Out of Dodge: Migrating to Windows Server 2008 R2 x64 

Rick Claus Tuesday, May 17, 1:30 PM – 2:45 PM
Breakout Session
300 – Advanced

DBI304 | What’s New in Manageability for Microsoft SQL Server Code-Named "Denali"

Denny Cherry Tuesday, May 17, 1:30 PM – 2:45 PM
Breakout Session
300 – Advanced

VIR325 | Anatomy of HP Cloud Foundation for Hyper-V

Brad Kirby Tuesday, May 17, 5:00 PM – 6:15 PM
Breakout Session
300 – Advanced

VIR314 | Understanding Server App-V, Sequencing and Deploying Datacenter Applications

Derrick Isoka Wednesday, May 18, 8:30 AM – 9:45 AM
Breakout Session
300 – Advanced

EXL318 | Monitoring Microsoft Lync 2010 Deployments

Arish Alreja, Jeffrey Reed Wednesday, May 18, 10:15 AM – 11:30 AM
Interactive Discussion
400 – Expert

WSV473-INT | Windows PowerShell 3.0: Why Wait? Get Next-Generation PowerShell Functionality Today!

Kirk Munro Wednesday, May 18, 12:00 PM – 1:00 PM
Breakout Session
400 – Expert

WSV406 | Advanced Automation Using Windows PowerShell 2.0

Dan Harman, Jeffrey Snover Wednesday, May 18, 1:30 PM – 2:45 PM
Breakout Session
300 – Advanced

WCL321 | Windows PowerShell Remoting: Definitely NOT Just for Servers

Don Jones Wednesday, May 18, 1:30 PM – 2:45 PM
Breakout Session
300 – Advanced

DEV338 | NuGet: Microsoft .NET Package Management for the Enterprise

Scott Hanselman Wednesday, May 18, 1:30 PM – 2:45 PM
Breakout Session
300 – Advanced

VIR310 | Inside the LAB: Building Your Own Private Cloud Infrastructure

Mikael Nystrom Wednesday, May 18, 1:30 PM – 2:45 PM
Breakout Session
300 – Advanced

WSV322 | Managing the Registry with Windows PowerShell 2.0

Jeffery Hicks Thursday, May 19, 8:30 AM – 9:45 AM
Birds-of-a-Feather
300 – Advanced

BOF14-ITP | Challenges in Automation for Microsoft Data Repositories (Microsoft SQL Server, DPM and SharePoint)

Kevin Kline Thursday, May 19, 8:30 AM – 9:45 AM
Breakout Session
300 – Advanced

VIR326 | Fluid Data Management at Indiana University

Janssen Jones Thursday, May 19, 8:30 AM – 9:45 AM
Breakout Session
300 – Advanced

EXL321 | Microsoft Lync Server 2010: Administering Lync Server Deployment

Anand Lakshminarayanan, Cezar Ungureanasu Thursday, May 19, 10:15 AM – 11:30 AM
Interactive Discussion
400 – Expert

WSV473-INT-R | Windows PowerShell 3.0: Why Wait? Get Next-Generation PowerShell Functionality Today!

Kirk Munro Thursday, May 19, 1:00 PM – 2:15 PM
Breakout Session
300 – Advanced

WSV315 | Windows PowerShell for Beginners

Jeffrey Snover, Mir Rosenberg Thursday, May 19, 1:00 PM – 2:15 PM
Breakout Session
300 – Advanced

DBI326 | Enterprise Data Mining with Microsoft SQL Server

Mark Tabladillo Thursday, May 19, 2:45 PM – 4:00 PM
Hands-on Lab
200 – Intermediate

WSV276-HOL | Introduction to Windows PowerShell Fundamentals

N/A Hands-on-lab, available in the TLC HOL area
Hands-on Lab
300 – Advanced

WSV371-HOL | Advanced Windows PowerShell Scripting

N/A Hands-on-lab, available in the TLC HOL area
Hands-on Lab
300 – Advanced

WSV378-HOL | Server Management and Windows PowerShell V2 (V3.0)

N/A Hands-on-lab, available in the TLC HOL area
Hands-on Lab
300 – Advanced

WCL376-HOL | Managing a Domain Environment More Effectively

N/A Hands-on-lab, available in the TLC HOL area
Hands-on Lab
300 – Advanced

WSV379-HOL | What’s New in Active Directory (V3.0)

N/A Hands-on-lab, available in the TLC HOL area
Hands-on Lab
200 – Intermediate

WSV273-HOL | Failover Clustering Introduction with Windows Server 2008 R2

N/A Hands-on-lab, available in the TLC HOL area
Hands-on Lab
300 – Advanced

WSV377-HOL | Migrating DHCP and File Services with Windows Server Migration Tools

N/A Hands-on-lab, available in the TLC HOL area
Hands-on Lab
300 – Advanced

EXL377-HOL | Managing Microsoft Lync Server 2010 Using Windows PowerShell and the Lync Server Control Panel

N/A Hands-on-lab, available in the TLC HOL area
Hands-on Lab
300 – Advanced

SIM373-HOL | Microsoft System Center Service Manager 2010 Data Warehouse and Reporting

N/A Hands-on-lab, available in the TLC HOL area

Quest Software Ask the Experts Session on PowerShell

There are other items that won’t show up in the schedule builder as well. For example, Quest Software has regular Ask the Experts sessions throughout the event, and one of those sessions will be focused on PowerShell, allowing you to ask questions to myself and Dmitry Sotnikov, watch some demos of the next version of PowerGUI® Pro, and have a chance to meet us at the event.  If this interests you, mark your calendar and join Dmitry and I in the Quest Software booth in the expo hall on Tuesday, May 17 from 12:30PM to 1:00PM, and bring your PowerShell and PowerGUI Pro questions!

WSV473-INT Windows PowerShell 3.0: Why Wait? Get Next-Generation PowerShell Functionality Today!

If you want to find me when I’m not working the PowerShell booth or answering questions during the Ask the Experts session on PowerShell, you can always come catch me at my session.  It is included in the session listing above.  I will be presenting a 400-level interactive discussion about PowerShell, WSV473-INT Windows PowerShell 3.0: Why Wait? Get Next-Generation PowerShell Functionality Today!  During this session I’ll be discussing different ways that you can get next-generation PowerShell functionality today so that you don’t have to wait as long until the next release.  This session will cover cool PowerShell features such as proxy functions, and it will also discuss Domain Specific Vocabularies, a topic I recently spoke about at the PowerShell Deep Dive.  You can read more about the session here.

Important Update:

This session has been scheduled for a second showing on Thursday, May 19, 2011 from 1:00-2:15PM, so if you can’t make the first one, come to the second!  Here’s the link to the update: WSV473-INT-R | Windows PowerShell 3.0: Why Wait? Get Next-Generation PowerShell Functionality Today!

Watch for additional opportunities to learn about PowerShell

Beyond these sessions, there are always other possible opportunities to learn about PowerShell while you are at TechEd 2011 in Atlanta.  The scheduled sessions at TechEd offer a ton of value already, but for me, the true value of a conference like TechEd comes from the unexpected and often unplanned side discussions that surprise you at a conference like this.  Some of my favorite discussions about PowerShell at conferences in the past have happened in an ad-hoc meeting, over breakfast, or in the PowerShell booth.  Never be afraid to start the discussion and ask others if they use PowerShell, and if possible keep your laptop handy so that you can pull it out and talk shop on the spot.  There is huge value in those discussions, and I highly recommend them.

That’s it from me for now.  If I hear about additional opportunities to learn more about PowerShell while at TechEd I’ll be sure to post them here.

Thanks for listening!

Kirk out.

Earth Day 2011 – PowerGUI® Style!

Today is Earth Day 2011, and you can celebrate your green side in style with the latest PowerGUI® wallpaper.  As an ecoholic myself, this wallpaper is definitely among my favorites.

Show your Earth Day pride, and download this beautiful desktop wallpaper today! If it doesn’t suit your style, check out the rest of the desktop wallpaper images we have in the Wallpaper category on PowerGUI.org.  There are plenty to choose from!

Kirk out.