Windows PowerShell 3.0 Step by Step - Cdn.oreilly.com - O'Reilly

Get-PowerShellRequirements.ps1
Param([string[]]$computer = @($env:computername, "LocalHost"))
foreach ($c in $computer)
{
$o = Get-WmiObject win32_operatingsystem -cn $c
switch ($o.version)
{
{$o.version -gt 6.2} {"$c is Windows 8 or greater"; break}
{$o.version -gt 6.1}
{
If($o.ServicePackMajorVersion -gt 0){$sp = $true}
If(Get-WmiObject Win32_Product -cn $c |
where { $_.name -match '.NET Framework 4'}) {$net = $true }
If($sp -AND $net) { "$c meets the requirements for PowerShell 3" ; break}
ElseIF (!$sp) {"$c needs a service pack"; break}
ELSEIF (!$net) {"$c needs a .NET Framework upgrade"} ; break}
{$o.version -lt 6.1} {"$c does not meet standards for PowerShell 3.0"; break}
Default {"Unable to tell if $c meets the standards for PowerShell 3.0"}
}
}
Deploying Windows PowerShell to down-level
operating systems
After Windows PowerShell is downloaded from http://www.microsoft.com/downloads, you can deploy
it to your enterprise by using any of the standard methods. Here are few of the methods that you can
use to accomplish Windows PowerShell deployment:
■■ Create a Microsoft Systems Center Configuration Manager package and advertise it to the
appropriate organizational unit (OU) or collection.
■■ Create a Group Policy Object (GPO) in Active Directory Domain Services (AD DS) and link it to
the appropriate OU.
■■ Approve the update in Software Update Services (SUS) when available.
■■ Add the Windows Management Framework 3.0 packages to a central file share or webpage
for self service.
If you are not deploying to an entire enterprise, perhaps the easiest way to install Windows
PowerShell is to download the package and step through the wizard.
note To use a command-line utility in Windows PowerShell, launch Windows PowerShell
by choosing Start | Run | PowerShell. At the PowerShell prompt, type in the command
to run.
4 Windows PowerShell 3 Step by Step