LLMpediaThe first transparent, open encyclopedia generated by LLMs

Windows PowerShell

Generated by DeepSeek V3.2
Note: This article was automatically generated by a large language model (LLM) from purely parametric knowledge (no retrieval). It may contain inaccuracies or hallucinations. This encyclopedia is part of a research project currently under review.
Article Genealogy
Parent: MS-DOS Hop 4
Expansion Funnel Raw 52 → Dedup 0 → NER 0 → Enqueued 0
1. Extracted52
2. After dedup0 (None)
3. After NER0 ()
4. Enqueued0 ()
Windows PowerShell
Windows PowerShell
NameWindows PowerShell
DeveloperMicrosoft
Released14 November 2006
Latest release version5.1
Latest release date02 August 2016
Operating systemWindows 7, Windows Server 2008 R2 and later
GenreCommand-line interface, Scripting language
LicenseProprietary software

Windows PowerShell. It is a task automation and configuration management framework from Microsoft, consisting of a command-line shell and associated scripting language built on the .NET Framework. Initially released for Windows XP, it has become a core administrative tool across the Windows NT family, including Windows Server 2012 and Windows 10. It is designed to help IT professionals control and automate the administration of the Windows operating system and applications that run on Windows.

Overview

The development of this framework was led by Jeffrey Snover as part of the Microsoft Management Console initiative, aiming to address the limitations of Command Prompt and Windows Script Host. It integrates deeply with the Component Object Model and Windows Management Instrumentation, providing unprecedented access to system internals. Its introduction marked a significant shift in Microsoft's strategy for System administration, promoting a more consistent and powerful automation environment. The framework's architecture allows it to manage entities across diverse systems, from the Active Directory to Microsoft Exchange Server.

Features

A core feature is its consistent handling of objects rather than text, with output from one command, known as a cmdlet, easily piped as input to another. It supports robust scripting capabilities, including functions, classes, and modules, enabling the creation of complex automation workflows. The framework includes an Integrated Scripting Environment for debugging and writing scripts, and it features extensive Remoting capabilities, allowing administrators to run commands on remote systems like Windows Server 2016. Other significant features include background jobs, transaction support, and a provider model that exposes data stores, such as the Windows Registry and Certificate Store, as navigable drives.

Language

The scripting language is built on the .NET Common Language Runtime, allowing direct consumption of .NET Framework classes and enabling the creation of powerful scripts and cmdlets. Its syntax supports familiar programming constructs like loops, conditions, and error handling, making it accessible to those with experience in languages like C# or Visual Basic .NET. The language is designed for discoverability, with a verb-noun naming convention and the `Get-Command` cmdlet for exploring functionality. It can interact with various Microsoft technologies, including SQL Server and Internet Information Services.

Cmdlets

Cmdlets are lightweight commands that perform an action and return a .NET Framework object, with names following a strict `Verb-Noun` pattern, such as `Get-Process` or `Set-Service`. Thousands of cmdlets are available out-of-the-box for managing components like network configuration, services, and Event Logs, with additional cmdlets provided by roles and features like Active Directory Domain Services. Third-party products, including those from VMware and Amazon Web Services, also extend its functionality with their own cmdlet modules. The `Get-Help` cmdlet provides comprehensive, accessible documentation for all available commands.

Versions

Version 1.0 was released in 2006 for Windows XP, Windows Server 2003, and Windows Vista. Version 2.0, integrated into Windows 7 and Windows Server 2008 R2, introduced major features like remoting, modules, and background jobs. Version 3.0, shipped with Windows 8 and Windows Server 2012, added enhanced workflows, scheduled jobs, and improved session connectivity. Version 4.0, included in Windows 8.1 and Windows Server 2012 R2, brought Desired State Configuration for declarative management. Version 5.0 and 5.1, the final versions under this name, were released with Windows 10 and Windows Server 2016, introducing advanced features like class definitions and the PowerShell Gallery.

Security

Execution policy settings, configurable via Group Policy, restrict script execution to prevent malicious code from running, with levels ranging from `Restricted` to `Bypass`. It supports script signing using X.509 certificates to ensure integrity and origin, a critical feature in environments managed by Active Directory Certificate Services. The remoting protocol, based on Web Services for Management, uses Windows Remote Management and can be secured with SSL and constrained endpoints to limit exposed functionality. These security measures are essential for compliance in regulated industries and for protecting infrastructure like Microsoft Azure virtual machines.

Category:Microsoft development tools Category:Scripting languages Category:Windows administration