Security enhancements including enforcement of catalog-signed modules coming from the Pull Server and when using PowerShellGet cmdlets;

Responses to a number of user requests and issues;

WMF Compatibility

WMF 2.0

WMF 3.0

WMF 4.0

WMF 5.0

WMF 5.1

Windows XP

Yes

No

No

No

No

Windows Server 2003

Yes

No

No

No

No

Windows Vista

Yes

No

No

No

No

Windows 7 SP1

Yes

Yes

Yes

Yes

Yes

Windows Server 2008 SP2

Yes

Yes

(Expect IA64)

No

No

No

Windows Server 2008 R2 SP1

Yes

Yes

(Expect IA64)

Yes

Yes

Yes

Windows 8

Yes

Yes

Yes

Yes

Yes

Windows 8.1

Yes

Yes

Yes

Yes

Yes

Windows Server 2012 SP1

Yes

Yes

Yes

Yes

Yes

Windows Server 2012 R2

Yes

Yes

Yes

Yes

Yes

Windows 10

Yes

Yes

Yes

Yes

Yes

Windows Server 2016

Yes

Yes

Yes

Yes

Yes

As of August 18, 2016 Windows PowerShell became Open-Source which means you can run on MacOS and some Linux distributions. The PowerShell team is using GitHub so anyone can contribute with the project at https://github.com/powershell .

PowerShell Gallery

The PowerShell Gallery is the central repository for PowerShell content. New PowerShell or Desired State Configuration (DSC) commands are present.

By accessing your account you can verify that you have an API key and it is this key that is used for submission.

Script Creation

Before starting the script you need to create the block that includes the script information with the cmdlet 'New-ScriptFileInfo'. The block will contain the version, GUID that is automatically generated, author, required information and script dependencies.

If you already have a script created add the PSScriptInfo body at the beginning of the script.

Testing the script

The cmdlet 'Test-ScriptFileInfo' checks the comment block if it has an error it will tell you where it is located or how to fix it.

As you can see in the image, no error was displayed and can be sent. The following image has a purposeful error in which a variable is not defined and can not be sent until the error is corrected.

Script publishing

With the tested script you can now publish it to publish you need the API key that you can query in your account. To publish, use the Publish-Script cmnlet.

Publish-Script -Path <localização do script> -NuGetApiKey <chave API>

An important rule is that the name of the script must be unique if you try to publish a script with the same ID will return an error and is required to rename the script.

Manage the script in the gallery

In your Manage My Items account you can manage all submitted modules or scripts.

You can edit the contents of the script.

The gallery also has the chance to delete the script but is not yet supported by the gallery what it can do is remove the script from the searches.

With successful publishing the script is visible and searchable in the Web Gallery comes as in PowerShell. The gallery hypothesis to save the script without installing with the 'Save-Script' cmldet. If someone wants to install you can use the cmdlet 'Install-Script'.

There is no restriction for publication but you have to be careful that the script or module you want to publish does not contain any sensitive information such as logins, passwords, keys for database links.

Even if the script has passed the tests it is always important to review and test the script before publishing. If it is possible to do it on another machine.