Contents tagged with Powershell

  • TechEd session report: What’s Coming in Windows PowerShell V2?

    Posted by MBrant on June 12 2008, 9:59 PM. Posted in Powershell, TechEd 2008.

    “What’s Coming in Windows PowerShell V2?” by Jeffrey Snover, who is the partner architect for Windows PowerShell, and Narayanan Lakshmanan, Software Design Engineer.Jeffrey started the session by talking about the acceptance/implementation state of the current Powershell. In the 18 months since it launched, Powershell has been downloaded over 2 million times. Also allot of Microsoft teams are implementing the Powershell extensions in their solutions. Exchange, SQL,  SCOM, SCVMM and SCDPM teams have or have announced Powershell support. So adoption is doing good. Jeffrey also noted on how passionate the team is. Not only did work 200% on Powershell, they also helped write multiple books on Powershell available today. That’s dedication.He went on by stating that most of the press have made misconception on Powershell. Powershell isn’t a CLI or and CMD-replacement. It’s an automation scripting platform with multiple API’s and is accessible through the Powershell CLI. To prove that Powershell isn’t just a shell, he demoed a new cmdlet called “Gridview”. Gridview, invoked by adding it as an extra argument on commands, shows an powerfull GUI displaying the results of the command in a grid control. This allows you to sort, filter and organize the data as you please. This is called GUI over Powershell.One other subject was production scripting which doesn’t differ that much from the old scripting in powershell 1 with the exception with a couple of extra scripting features. They said they are supporting transactions. Transactions … in a CLI/scripting language? Jeffrey said they were the first ones to support such a feature. As you may expect when looking at transactions from SQL, they support rollback of commands. Mostly on the registry. It is limited, as you might expect, but be sure to check it out of you’re  a powershell dev.Furthermore they talked about Mobile Objects Model. MOM allows you take a part of your script/command, send it over the network and execute in a remote computer without the need of the whole app/script/execution to be on that remote computer. The object your working with will be serialized to a XML text stream and deserialized on the remote end.  A real nice feature which I’m sure a lot of deployment scripting experts will love.Also they talked about native code implementation. From v2 on you can use VB, C# and F# code in your Powershell scripts and make use of the full .NET platform. Job support allows you to run scripts in the background and control those as you wish. Remote or local. Restricted namespaces allow you to run scripts in a more secure, locked-down environment. Also eventing and triggering is now supported.They fixed the PS-Space bug. They said if you don’t know what it was, good for you. If you do, you can’t wait to get v2.Community was central to this release and powershell. They said they really listened to feedback and fixed  a lot of bugs and improved the engine and made it faster.The session itself was quite in-depth and I recommend Powershell gurus read through the PPTX! Also check out the Powershell team blog: http://blogs.msdn.com/Powershell

  • Windows PowerShell V2 Community Technology Preview 2 (CTP2)

    Posted by bink on May 4 2008, 12:47 AM. Posted in Powershell.

    Windows PowerShell V2 CTP2 introduces several significant features to Windows PowerShell 1.0 and Windows PowerShell V2 CTP that extends its use, improves its usability, and allows you to control and manage the Windows environment more easily and comprehensively.
     
    Use the Download link on this page to download the installation package for the Windows PowerShell V2 CTP2. Windows PowerShell V2 CTP2 introduces several significant features to Windows PowerShell 1.0 and Windows PowerShell V2 CTP that extends its use, improves its usability, and allows you to control and manage the Windows environment more easily and comprehensively.
  • This software is a pre-release version and should not be deployed in a production environment. It will not work the way a final version of the software does. Features will change before final release.
  • The goal of this CTP2 release is to provide a preview to the community on early thinking and direction on key V2 features and get early feedback on them.
  • Windows PowerShell V2 CTP2 release is compatible with and replaces previous versions of Windows PowerShell. You must uninstall any previous version of Windows PowerShell to install the Windows PowerShell V2 CTP2 release.
  • Windows PowerShell V2 CTP2 uses the execution policy setting from the previous installation, if present. The Windows PowerShell installer does not remove or change the execution policy when you uninstall Windows PowerShell.
  • The Windows PowerShell V2 remoting features work correctly only on Windows Vista with Service Pack 1 (SP1) and on Windows Server 2008.
  • Windows PowerShell background jobs (PsJobs) rely on the remoting features of Windows PowerShell V2. To use PsJobs, remoting must be enabled on Windows PowerShell, even if the PsJob runs only on the local computer.Selected New Features in Windows PowerShell V2 CTP2 (Please refer to Release Notes and Help topics for more details)
  • PowerShell Remoting
  • Graphical PowerShell
  • ScriptCmdlets
  • Modules
  • Transactions
  • Eventing
  • Restricted Runspaces
  • RunspacePools
  • Background Jobs
  • Data Language
  • Script Internationalization
  • Script Debugging
  • 51 New Cmdlets
  • Parser Tokenizer API
  • New PowerShell Hosting APIs
  • Metadata APIs for Command and ParametersDownload At Source
  • PowerShell mandatory after June 30, 2008

    Posted by sumeethevans on November 27 2007, 5:51 PM. Posted in Powershell.

    This kind of was mentioned by Richard and Don, but I thought I would spell it out explicitly. According to Jeffrey Snover, PowerShell is becoming a part of the Common Engineering Criteria (CEC) 2009 at Microsoft. Meaning that every server product released by Microsoft in their financial year 2009 (which starts July 1, 2008) needs to ship with PowerShell support.Of course, a product can get an exemption, and of course support can vary to something as advanced as Exchange 2007 cmdlets, or as basic as PowerShell in SQL 2008, but nevertheless this is a huge success for PowerShell. After all, it was similar requirement for MOM report packs which made Operations Manager so ubiquitous.According to Jeffrey, there are currently 20 Microsoft teams working on PowerShell support in their products, and then there are VMware, and Citrix, and Quest, and /n Software, and PowerGadgets, and many more vendors adding PowerShell to their stuff.

    Continue At Source

    via http://www.techlog.nl

  • The Hey, Scripting Guy! Archive: Volume 1 (August 2004 - June 2006)

    Posted by bink on November 8 2007, 2:58 AM. Posted in Tools & Utils, Powershell.

    The first three years of the Hey, Scripting Guy! column (give or take a month) gathered together in one fully-searchable archive. This HTML help file includes all the text, graphics, and hyperlinks for well over 800 Hey, Scripting Guy! columns.
     
    Download At Source (link seems broken now, check later)
     
  • What's New in CTP of PowerShell 2.0

    Posted by bink on November 7 2007, 1:27 PM. Posted in Powershell.

    1.       PowerShell Remoting<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p></o:p>

    Windows PowerShell 2.0 provides support for executing Cmdlets and Scripts remotely. PowerShell Remoting allows managing a collection of remote machines from a single client. Managing remote computers using PowerShell 2.0, requires that PowerShell 2.0 be installed on all the computers taking part in the operation; that is the client computer and the computer(s) being managed.

    For more information:<o:p></o:p>

    ·         get-help About_Remoting

    ·         get-help Invoke-Expression

     

    Enable Remoting: PowerShell Remoting feature relies on Windows Remote Management (WS-Man) technology. In order for remoting to work, make sure that the WS-Man Winrm service is installed and started. To verify that Winrm service is running, do the following:<o:p></o:p>                                PS> get-service winrm<o:p></o:p>Setup places a PowerShell script (Configure-Wsman.ps1) in $pshome folder that configures WS-Man settings. To configure WS-Man for PowerShell remoting feature, please run the configure-WSMan.ps1 script from PowerShell folder (run elevated for Windows Server 2008 or Windows Vista SP1). This script does not start or stop WinRM service.<o:p></o:p>                & $pshome\Configure-Wsman.ps1 <o:p></o:p>

    Known issue: 

    ·         To use Remoting Cmdlets and features, PowerShell must be started as administrator/elevated. <o:p></o:p>

          ·         PowerShell 2.0 Remoting features will not work correctly on Windows Vista RTM. Please install Windows Vista Service Pack 1 (SP1) Beta to enable PowerShell Remoting features.

    2.       Background Jobs

    <o:p>Continue At Source</o:p>
  • Windows PowerShell 2.0 Community Technology Preview (CTP)!!

    Posted by bink on November 6 2007, 8:43 PM. Posted in Powershell.

    Windows PowerShell 2.0 CTP introduces several significant features to Windows PowerShell 1.0 that extends its use, improves its usability, and allows you to control and managethe Windows environment more easily and comprehensively.
     
    Use the Download link on this page to download the installation package for the Windows PowerShell 2.0 CTP. Windows PowerShell 2.0 CTP introduces several significant features to Windows PowerShell 1.0 that extends its use, improves its usability, and allows you to control and managethe Windows environment more easily and comprehensively.
  • This software is a pre-release version. It will not work the way a final version of the software does. Features will change before final release.
  • The goal of this CTP release is to provide a preview to the community on early thinking and direction on key 2.0 features and get early feedback on them.
  • Windows PowerShell 2.0 CTP release is compatible with and replaces Windows PowerShell 1.0. You must un-install PowerShell 1.0 to install the PowerShell 2.0 CTP release.
  • Windows PowerShell 2.0 CTP release will continue to use the execution policy setting of PowerShell 1.0, if present. PowerShell 1.0 installer does not remove or change the execution policy on un-installation.
  • PowerShell 2.0 Remoting features will not work correctly on Windows Vista RTM. Please install Windows Vista Service Pack 1 (SP1) Beta to enable PowerShell Remoting features.
  • When Windows PowerShell 2.0 CTP is launched with an execution policy of “Restricted,” it will display an error message while loading the types and formatting files. To prevent this error message, change the execution policy to one that enables PowerShell’s scripting features – such as RemoteSigned. For more information about PowerShell’s execution policies, type “Get-Help about_signing”.
  • Graphical PowerShell is a very early alpha version meant for previewing early thinking and getting feedback.
  • PsJobs rely on the remoting features of Windows PowerShell 2.0. To use PsJobs, remoting must be enabled on Windows PowerShell, even if the PsJob runs only on the local computer.Selected New Features in Windows PowerShell 2.0 CTP (Please refer to Release Notes and Help topics for more details)
  • PowerShell Remoting
  • Graphical PowerShell
  • ScriptCmdlets
  • Restricted Runspaces
  • RunspacePools
  • Background Jobs
  • Data Language
  • Script Internationalization
  • Script Debugging
  • 24 New Cmdlets
  • Parser Tokenizer API
  • New PowerShell Hosting APIs
  • Metadata APIs for Command and ParametersAfter you install this product, you might have to restart your computer.
  • Download At Source

  • Free PowerShell Logo bumper sticker

    Posted by bink on August 22 2007, 2:35 PM. Posted in Powershell.

    Show your support for Microsoft Windows PowerShell with a FREE PowerShell Logo bumper sticker!  Enter your shipping information in the form below and we will send you a couple stickers - one for your car, one for you laptop, etc.  For showing your PowerShell support, you will automatically be entered for a chance to win this new PowerShell Skinned XBox 360.You will also get special offers and discounts for /n software products including our NetCmdlets for Windows PowerShell, and our upcoming PowerShell Remoting solution.Signup at source

    Download PowerShell NetCmdlets

    Created :  06/05/2007Size :  648 KB

  • Videos on Windows PowerShell for IT Professionals

    Posted by bink on August 22 2007, 2:00 PM. Posted in Powershell.

    Don Jones and Jeffrey Snover: The Value of Windows PowerShell for IT Professionals Don Jones, author, trainer and scripting guru for www.ScriptingAnswers.com and www.Sapien.com discusses the value of PowerShell for IT Administrators and Enterprise IT Management with Jeffrey Snover, Architect for Windows PowerShell and Microsoft Management Console.  Don Jones is the author with Jeffrey Hicks of PowerShell TFM from Sapien Press. 
    Jeffrey Snover and Dmitry Sotnikov: Learn and Master Windows PowerShell with Quest Software’s PowerGUIJoin Jeffrey and Dmitry as they demonstrate the free graphical user interface for running Windows PowerShell cmdlets (commands) and writing scripts. PowerGUI consists of a GUI that allows you to easily inspect and execute Windows PowerShell cmdlets as well as a “click-through macro” for writing Windows PowerShell scripts.  As Jeffrey says, this is what Microsoft originally wanted to do but we ran out of time because of testing. Download Quest Software’s PowerGUI at www.PowerGUI.org
    Dmitry Sotnikov: Using Windows PowerShell to manage Windows Server 2008 Active Directory and Read-Only Domain ControllersWindows PowerShell is included as part of Windows Server 2008. Join Dmitry Sotnikov from Quest Software and Scott Ottaway from Microsoft as they demonstrate the use of Windows PowerShell to manage new features in Server 2008 including new Active Directory features and Read-Only Domain Controllers. Go to http://www.quest.com/activeroles-server/arms.aspx to download the free Quest Software Active Directory cmdlets and their free GUI for executing PowerShell cmdlets and writing Windows PowerShell scripts.
  • Free Windows Powershell e-book

    Posted by bink on May 17 2007, 2:46 AM. Posted in Powershell.

    Frank Koch Technology Advisor Microsoft Schweiz, did release an English version of the PowerShell book he released in German some time ago.The book is available for free and you can share it with all your colleagues or friends if you leave it as it is. The books can be used with or without the demo files available at his blog as well.Windows PowerShell book(free)
  • MMS: Windows Powershell will be included in Longhorn Server!

    Posted by bink on March 29 2007, 4:07 AM. Posted in Powershell.

    Windows Powershell will be in Longhorn Server! Seems obvious, but it didnt make it in Vista.Next version of powershell will include powershell remoting enabling remote access to powershells via WS-Management to do this in a secure and standard manner.   Quest Provides free AD cmd-let:  http://www.quest.com/activeroles_server/arms.aspx<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /?><o:p></o:p>  PowerGUI freeware, GUI on top of Powershell which basicly enable you to use every cmdlet available in powershell even third party or own cmdlets. PowerGUI is completely extensible with custom cmdlets and custom filters, which can be exported and imported to XML.   www.powergui.org    from msdn blog: /n software (www.nsoftware.com) announced PowerShell Remoting which provides a secure, remoting solution for Windows PowerShell based on SSH that provides interactive, object-based remoting and remoting to non-Windows devices and operating systems. While the first version of Windows PowerShell provides native support for remoting via WMI, it does not provide interactive remoting for other Windows data sources such as the registry or certificates.  /n Software has also previously announced NetCmdlets which provides extensive networking management capabilities via cmdlets. At the Microsoft Management Summit in San Diego today we announced that Windows PowerShell will be included in Windows Server code-named “Longhorn” and will be available in Beta 3 of “Longhorn”.   That's right, every version of Windows Server will ship with PowerShell!   http://blogs.msdn.com/powershell/