Episode 32 – Citrix does PowerShell


A Podcast about Windows PowerShell.

In This Episode

We have a great show lined up for you today.  We're interviewing Peter Schulz with Citrix to talk about their PowerShell product Workflow Studio.  And as always: News, Resources, Tips, and more!


Today's news is brought to you by SAPIEN Technologies.


This interview is brought to you by iTripoli.
"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 the exclusive PowerShell forms designer.  Come see for yourself-- Admin Script Editor v3.5 is availble for a 45 day trial at AdminScriptEditor.com."

Our interview today is with Peter Schulz from Citrix.  Enjoy.  Here's our notes from the conversation:

  1. Intro
    1. Peter Schulz has been with Citrix for over 8 years in Consulting, Engineering, Product Marketing, and is now the Technical Product Manager for Citrix Workflow Studio, a new IT Process Automation tool that is currently available as a technology preview.
    2. Background
    3. PowerShell's adoption inside Citrix
  2. Workflow Studio
    1. Background / Why the acquisition?
    2. Features
      1. Overview
      2. Built-in tasks
        1. How are these made?
        2. Can a user create new ones?
        3. How often will Citrix be updating them?
        4. Selected Categories / tasks
          1. AD: Create Random Password
          2. input/output: user choice
          3. flow control: split task
      3. Can workflows be executed on remote systems directly?
      4. You can double-click on a task and you drill down into a function?  How does this work?
    3. Will the product remain free?
      1. There will always be a free version similar to what is in the tech preview now.  The commercial version will of course have more stuff in it.
    4. Ship date?
      1. Second half of this year
    5. How are customers using it so far?
    6. Vision / future plans
      1. .net 3.5
  3. For more information?
    1. Peter's blog: http://community.citrix.com/blogs/citrite/petersc
    2. Workflow Studio download link: http://citrix.com/wfsinsider
    3. Community page: http://community.citrix.com/display/cdn/Citrix+Workflow+Studio


Do you have what it takes to be the ultimate script warrior? Find out with Quest’s PowerPack Challenge ’08.
Quest Software is sponsoring a PowerShell Scripting contest where you can test your skills and get paid. Just create some cool PowerShell scripts using Quest’s PowerGUI and then post them to our site. You’ll get a score and our celebrity judges will weigh in as well.
Do you have the muscle to bring home the prize? Check out the details here.


  • Variable expansion in strings. We've talked about it before, but I saw someone fighting with it just yesterday.
    • "$object.parameter something else" does not work. Use "$($object.parameter) something else" instead
  • From Poshoholic: Essential PowerShell: Name your custom object types
    • One important thing that is often overlooked when people are writing scripts that do this is that they can also give those objects a type name.
  • Sepeck on the #PowerShell IRC channel (irc.freenode.net) shared a link with us about his experiences with PowerShell help files.  It's a good before-and-after story with a lesson.  :)  He links to one of Don Jones' articles with further advice on the topic.


  • [system.directoryservices.activedirectory.domain]::GetCurrentDomain().DomainControllers | fl Name

A big thanks to Peter Schulz for coming on the show tonight.  We're looking forward to interviewing the Kirk and Dmitry from the PowerGUI team.  Send in your questions!  As always, you can contact the show by email to [email protected].  You can also leave us reviews on iTunes and comments on the blog.  Don't forget to check out Quest's contest details at quest.com/powerscripting.
Other ways to interact with us: Facebook Group (forums, networking), Twitter (jonwalz & halr9000)

Comments are closed.