Share on Facebook0Share on Google+0Share on LinkedIn0Share on Reddit17Tweet about this on Twitter0

PowerShell introduction

PowerShell is a command line (CLI) scripting language developed by Microsoft to simplify automation and configuration management, consisting of a command-line shell and associated scripting language.

It’s a (huge) evolution (or better a revolution) from the original DOS batch language (still supported in latest Windows OS with the cmd.exe command), and it’s really better compared to the different previous attempts to replace the batch language (like Windows Script Host).

Windows PowerShell (actually at version 5.1) is the edition of PowerShell built on top of .NET Framework (sometimes referred to as “FullCLR”). Because of its dependency on the .NET Framework, Windows PowerShell is only available on Windows (hence the name). The released versions of Windows PowerShell include 1.0, 2.0, 3.0, 4.0, 5.0, and 5.1. Windows PowerShell is launched as powershell.exe.

PowerShell initially was a Windows component only, known as Windows PowerShell, but recently it was made open-source and cross-platform on 18 August 2016 with the introduction of PowerShell Core.

PowerShell Core uses .NET Core 2.0 as its runtime (sometimes simplified to “CoreCLR”), that enables PowerShell Core to work on multiple platforms, thanks to the cross-platform nature of .NET Core.

PowerShell Core also exposes the API set offered by .NET Core 2.0 to be used in PowerShell cmdlets and scripts. Windows PowerShell used the .NET Framework runtime to host the PowerShell engine.

PowerShell it’s cross-platform and this means that now you can run it, of course, on Windows, but also on several different Linux distributions, on MacOSX 10.12 and also on ARM platform!

The list of supported Linux distributions is quite good: Ubuntu 14.04, Ubuntu 16.04, Ubuntu 17.04, Debian 8, Debian 9, CentOS 7 (and also Oracle Linux 7), Red Hat Enterprise Linux (RHEL), OpenSUSE 42.2, Fedora 25, Fedora 26, Arch Linux.

All packages are available on Microsoft’s GitHub releases page.

All those distributions have a simple package repository that you can add (this task depends on the distribution) and then you can simply add the powershell package.

For example, for CentOS 7, Oracle Linux 7 or RHEL7:

Latest stable release is version 6.0.2:

But there is already also the first preview of the new v6.1:

For Linux, PowerShell builds portable binaries for all Linux distributions. But .NET Core runtime requires different dependencies on different distributions, and hence PowerShell does the same.

The following table shows the .NET Core 2.0 dependencies on different Linux distributions that are officially supported.



Ubuntu 14.04 libc6, libgcc1, libgssapi-krb5-2, liblttng-ust0, libstdc++6,
libcurl3, libunwind8, libuuid1, zlib1g, libssl1.0.0, libicu52
Ubuntu 16.04 libc6, libgcc1, libgssapi-krb5-2, liblttng-ust0, libstdc++6,
libcurl3, libunwind8, libuuid1, zlib1g, libssl1.0.0, libicu55
Ubuntu 17.04 libc6, libgcc1, libgssapi-krb5-2, liblttng-ust0, libstdc++6,
libcurl3, libunwind8, libuuid1, zlib1g, libssl1.0.0, libicu57
Debian 8 (Jessie) libc6, libgcc1, libgssapi-krb5-2, liblttng-ust0, libstdc++6,
libcurl3, libunwind8, libuuid1, zlib1g, libssl1.0.0, libicu52
Debian 9 (Stretch) libc6, libgcc1, libgssapi-krb5-2, liblttng-ust0, libstdc++6,
libcurl3, libunwind8, libuuid1, zlib1g, libssl1.0.2, libicu57
CentOS 7 
Oracle Linux 7 
OpenSUSE 42.2 
Fedora 25
libunwind, libcurl, openssl-libs, libicu
Fedora 26 libunwind, libcurl, openssl-libs, libicu, compat-openssl10

In order to deploy PowerShell binaries on Linux distributions that are not officially supported, you would need to install the necessary dependencies for the target OS in separate steps. Unfortunately, the real dependencies are not easy to guess and could be quite difficult.

For Linux distributions that are not officially supported, you can try using the PowerShell AppImage. Using a recent Linux distribution, download the AppImage from the releases page into the Linux machine. This is a binary version that will help you in the dependencies, if possible.

Note that actually the latest version of AppImage it’s only the version 6.0.1:

Another option is just to grab the binaries files, that are more recently:



But in both cases, you will expect several issues, for example in libraries dependencies.

For example, on a CentOS 6.9 system (64 bit version):

Libraries dependencies is totally a mess, maybe was better provide those binaries with the option of static link to the required libraries, instead of relay on external shared libraries.

And it’s not so easy fix the requirements, for example on a CentOS 6.9 the installed libstdc++ library is quite old:

Trying to install a more recent lib from the repositories does not work, because it’s still too old:

Also PowerShell AppImage does not help at all:

You can fix the first requirement easily by installing the fuse-libs package (fuse-libs-2.8.3-5.el6.x86_64)

But then you will again have the issues with the shared libraries:

There is a dirty trick that potentially can help, and it’s use the libraries packages from the CentOS 7 distribution or another distribution from, then unpack them.

For example for libstdc++:

But it’s not enough, because there are a lot of other libraries that are needed.

Is too much easy using a latest distribution and install just a package. For CentOS7:

That’s it, isn’t simple? And just stating from a minimal installation using the minimal ISO of CentOS.

StarWind Virtual SAN eliminates any need for physical shared storage just by mirroring internal flash and storage resources between hypervisor servers. Furthermore, the solution can be run on the off-the-shelf hardware. Such design allows StarWind Virtual SAN to not only achieve high performance and efficient hardware utilization but also reduce operational and capital expenses.
Learn more about ➡ StarWind Virtual SAN

Using PowerShell Core

Once you installed PowerShell, to start the PowerShell console/session you can run the pwsh from a local terminal or a remote SSH session.

Note that actually, PowerShell Core provides only a subset of all the available PowerShell commands!

Just compare the available modules in Linux and Windows and the difference is huge:

1 - Using PowerShell Core - Comands

But it’s just a first step.

To view the version of the PowerShell, enter:

Then you can start using PowerShell command, but note that the output could be different if you run on Linux or on a Windows system. For example, compare the result of the command:

Note that on Linux, also if the OS is case sensitive, you can run the commands in the PowerShell sessions in lower case and the command will be converted with the right capital letters. And like it happen on Windows, you can still use all the other command from the standard CLI (like ls, for example).

Also, like in the bash, you can have some command aliases. To view the list of available aliases, run:


Remote PowerShell

The beauty of PowerShell on Windows is the ability to launch remote sessions, in this way you can use your client and manage different servers.

A PowerShell remote session communicates using Windows Remote Management (WinRM), that is an implementation of the Web Services for Management (WS-Man) specification.

The network channel requires a HTTP (TCP port 5985) or HTTPS (TCP port 5986) connection, usually utilized on “traditional” XML/SOAP web services.

Linux supports WS-Man through a combination of PowerShell Remoting Protocol (MS-PSRP) and an Open Management Infrastructure (OMI) provider. OMI is a standard interface for exposing Common Information Model (CIM) data on non-Windows systems. OMI can be downloaded from The Open Group: Open Management Infrastructure (OMI).

To configure the Linux machine for WSMAN, you’ll need to open the right port in the personal firewall:

Now you can run a PowerShell session from another system.

For example, from a Windows 10 client:


Nice, isn’t it?

But why using PowerShell?

For Windows system is quite clear that it’s the main command line but also the primary way to configure a Window system (from CLI you can do more compared from the CLI, as discussed in a previous post).

But why using PowerShell instead of other (cross-platform) languages? And why on Linux?

One reason is the beauty of the language and the powerful capability of the object-piping.

For example, let’s consider that you need the PID of the crond service. Using the ps command provide this information on a fixed formatting, but you need to filter it with grep to find the right line (and maybe you can found more lines).

The you need other tools (like cut command) to select the right part. Not easy and this is an easy case, because the columns are fixed!

Let’s see the same with PowerShell:

Another reason, very interesting for VMware vSphere admin (but there is something similar also for other VMware’s products), it’s using PowerCLI from Linux machine! I will discuss this option on a future post.

Another reason is using the DSC (Desired State Configuration). Windows PowerShell Desired State Configuration (DSC) is a configuration management platform to function reliably and consistently in each stage of the deployment lifecycle (development, test, pre-production, production), as well as during scale-out. To learn more, there is a nice article ( that describe the difference between declarative and imperative models.

The following Linux operating system versions are supported for DSC for Linux.

  • CentOS 5, 6, and 7 (x86/x64)
  • Debian GNU/Linux 6, 7 and 8 (x86/x64)
  • Oracle Linux 5, 6 and 7 (x86/x64)
  • Red Hat Enterprise Linux Server 5, 6 and 7 (x86/x64)
  • SUSE Linux Enterprise Server 10, 11 and 12 (x86/x64)
  • Ubuntu Server 12.04 LTS, 14.04 LTS and 16.04 LTS (x86/x64)

Desired State Configuration for Linux requires the Open Management Infrastructure (OMI) CIM server, version or later.

If you already have installed OMI (needed also for WS-Man) you just need DSC:

For more information on DSC on Linux and how can be used see also:

What’s the future of PowerShell?

PowerShell Core will be provided with new feature updates and fixes while the older PowerShell will just be provided bug fixes and security updates.

This is an official statement from Microsoft about the future of PowerShell:

However, there are currently no plans to introduce new functionality to Windows PowerShell. This means that the risk of regression will be very low for Windows PowerShell, so you can count on it as a stable platform for your existing workloads.

But actually, PowerShell Core is not as powerful as the full PowerShell, so it will some time to have both aligned. For now, PowerShell Core isn’t a drop-in replacement for Windows PowerShell because Core has a different audience and intent.

PowerShell PowerShell Core
Versions 1.0 to 5.1 6
Platforms Supported Only Windows client and Server) Windows, Linux, and MacOS
Dependency .NET Framework .NET Core
Usage Depends on .NET Framework Runtime Depends on .NET Core Runtime
Launched as powershell.exe pwsh.exe on Windows and pwsh on MacOS and Linux
Future Updates for Bug fixes and Security Updates only Feature Update, Bug Fixes as well as Security Updates


Views All Time
Views Today
Appreciate how useful this article was to you?
No Ratings Yet
The following two tabs change content below.
Andrea Mauro
Andrea Mauro
Virtualization expert and architect, System Administrator on Linux and Windows OS, network and storage specialist. Holding multiple technical certifications from VMware: (VCDX3, VCDX4, VCDX5-DCV, VCAP4-DCA, VCAP4-DCD, VCAP5-DCA, VCAP5-DCD, VCAP6-DCD, VCAP5-DTD, VCAP5-DTA, VCAP5-CIA, VCAP5-CID, VCIX-NV, VCIX6-DCV,VCP3, VCP4, VCP5-DCV, VCA4-DT, VCP4-DT, VCP5-DT, VCP6-NV, VCP5-Cloud), Microsoft (MCP, MCSA, MCSE, MCTS, MCITP), Citrix (CCA, CCSP). VMware vExpert from 2010 to 2016, Microsoft MVP 2014-16 (on Hyper-V), Veeam Vanguard 2015-2016.