Powershell Crescendo general availability release

Powershell Crescendo general availability release

Powershell Crescendo general availability release



On March 10th Microsoft announced the General Availability (GA) release of PowerShell Crescendo, a platform-independent framework to rapidly develop PowerShell cmdlets for common command line tools. The release is available for download in PowerShell Gallery.



PowerShell Crescendo overview



The Crescendo framework allows developers to build PowerShell cmdlets which make use of existing command-line tools. Crescendo upgrades the overall functionality offered by the target command-line tool, by allowing the developer to include object output for the PowerShell pipeline, privilege elevation and integrated help information. A Crescendo module replaces cumbersome command-line tools with PowerShell cmdlets which are superior in terms of automation features and packaging.



The Crescendo framework has two main components:



- A JSON configuration file that describes the cmdlets you want

- Output handler functions that parse the output from the command-line tool and return objects

The Crescendo module provides cmdlets to help you create the JSON configurations and build a module containing the the cmdlets you defined. You must write your own output handler functions that return PowerShell objects.



The GA release includes the following features and benefits:



- Ability to define cmdlets from simple key/value statements in a JSON file

- Support for modular design – cmdlet definitions can be in a one or more JSON files

- A JSON schema that helps you create your Crescendo configuration using IntelliSense and tooltips

- Three styles of output handling code allowing you to separate your code from the cmdlet definitions for easier debugging and development

- Privilege elevation mechanisms in Windows, Linux, and macOS

- Crescendo generates a PowerShell script module ready for deployment

- While Crescendo requires PowerShell 7 or higher for authoring configurations, the generated module can run on Windows PowerShell 5.1 and higher

- Example configurations for you to copy and reuse

- Experimental Help parsers that provide proof-of-concept examples for auto-generating cmdlet configurations

Sources



https://docs.microsoft.com/en-us/powershell/utility-modules/crescendo/overview?view=ps-modules



https://devblogs.microsoft.com/powershell/announcing-powershell-crescendo-general-availability-ga/
https://stefanos.cloud/blog/powershell-crescendo-general-availability-release/

Comments

Post a Comment

Popular posts from this blog

How to perform hardware health checks in Windows

Image
Case You need to perform an overall hardware health check in a Windows machine, running either a Windows client or a Windows Server operating system. This article provides guidance on the steps to carry out to perform hardware health checks in Windows. Solution Carry out the steps below. - Thoroughly check all Windows event logs (Application, System, Security) for any warnings or errors which may be related to issues you are experiencing with your Windows machine. - Check the device management mmc console by running devmgmt.msc. Ensure that you choose to show all hidden devices from the View menu. If you notice any exclamation marks next to any device, you will need to re-install its driver from the respective manufacturer to ensure that there afterwards no warnings in the device management console. - Check the health of all your disks , either HDD or SSD. Follow instructions in the following KB article for steps to follow to check your disk health: https://stefanos.cloud/kb/how-to-ch...
Read more

How to resolve Group Policy error codes 8007071a and 800706ba

Image
Case You are running "Group Policy Update" on an OU inside the Group Policy Management Console in Active Directory but you are receiving RPC errors from your servers or domain-joined workstations, as shown in the example below. After a Group Policy Update, you come across Group Policy error codes 8007071a and 800706ba. This means that the local Windows Firewall is not configured properly to allow Group Policy (GPO) traffic. GPO traffic an be either remote GPO update or remote GP Resultant Set of Policy (RSOP) operations. Solution Option 1 Run gpedit.msc and create a new local group policy object which implements the following policies under Local Computer Policy --> Computer Configuration --> Windows Settings --> Security Settings --> Windows Defender Firewall --> Inbound Rules : The full configuration is shown below. After the above local group policies are configured on each domain server and workstation, you can start applying group policy objects to the dom...
Read more

FsLogix 2201 Public Preview release

Image
The FsLogix 2201 Public Preview release is now available for download from Microsoft. The change log is as follows: - Fixed issue where the FSLogix Profile Service would crash if it was unable to communicate with the FSLogix Cloud Cache Service. - The OfficeFileCache folder located at %LOCALAPPDATA%MicrosoftOffice16.0OfficeFileCache is now machine specific and encrypted so we now exclude it from FSLogix containers. Office files located outside this folder are not impacted by this update. - Windows Server 2019 version 1809, and newer versions of Windows Server, natively support per-user search indexes and we recommend you leverage that native search index capability. FSLogix Search Indexing is no longer available on those versions of Windows Server. - Windows 10 Enterprise Multi-session and Windows 11 Enterprise Multi-session natively support per-user search indexes and FSLogix Search Indexing is no longer available on those operating systems. - FSLogix now correctly handles cases where...
Read more