{"id":2220,"date":"2011-05-25T08:30:00","date_gmt":"2011-05-25T06:30:00","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/powershell-overview\/"},"modified":"2011-05-25T08:30:00","modified_gmt":"2011-05-25T06:30:00","slug":"powershell-overview","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/powershell-overview\/","title":{"rendered":"A brief PowerShell 2.0 overview"},"content":{"rendered":"

SQL Server 2008 has PowerShell and I am going to speak about the way they work together. However, some basics on PowerShell are needed to get the big picture. So let’s start with an introduction to the PowerShell technology.<\/p>\n

During the Microsoft Techdays in Basel, Marc van Orsouw presented PowerShell. I would like to present you an overview of PowerShell based on his presentation while adding some microsoft msdn website definition and my commentar.<\/p>\n

\"\" What is PowerShell?<\/h3>\n

Windows PowerShell is an extensible command-line shell and associated scripting language from Microsoft. It is not case sensitive.<\/p>\n

In PowerShell, administrative tasks are generally performed by cmdlets (pronounced command-lets), specialized .NET classes implementing a particular operation.<\/p>\n

Sets of cmdlets may be combined together in scripts, executables (which are standalone applications), or by instantiating regular .NET classes (or WMI\/COM Objects).<\/p>\n

This works by accessing data in different data stores, like the filesystem or registry, which are made available to the PowerShell runtime via Windows PowerShell providers.<\/p>\n

In this article, I will use PowerShell 2.0 ( included in Windows 7 and Windows 2008 R2).<\/p>\n

\"powershell<\/p>\n

The first step: your rights<\/h3>\n

Before running any script, you must change your policies while default is restricted.
\nTo see your current policy : Get-ExecutionPolicy<\/span><\/p>\n

There are four policies:<\/p>\n