#pscore6 v.s. #powershell 5.x Modules (Part III)

You must have already noticed discrepancies in modules and corresponding commands[1] between PowerShell versions and releases. How can I keep abreast with constant changes in today’s ever fast-pace cloud technologies now that PowerShell is cross-platform commencing with version 6.x?

One way to find out yourself is illustrated here, paying attention to compare apples to apples i.e. Windows Desktop v.s. Windows Desktop. Otherwise, a big difference is to be expected between Windows Server 2016 and Windows 10 Desktop platforms running PowerShell 5.1.x for instance. Read more “#pscore6 v.s. #powershell 5.x Modules (Part III)”

#pscore6 v.s. #powershell 5.x Modules (Part II)

In the default installation of PowerShell Core 6.0 and Windows PowerShell 5.10 (PS5) with 13 and 89 modules discovered respectively, both PS versions have overlapping module names as illustrated:


An output with similar module names does not always mean that the number and type of commands in each of these modules correspond (see Part I of this blog series). Read more “#pscore6 v.s. #powershell 5.x Modules (Part II)”

#pscore6 v.s. #powershell 5.x Modules

Because of the cross-platform heterogeneous support design goal in #PsCore6, many platform specific #powershell functionality on the Windows operating system simply cannot, may not or have not yet been migrated over. Since Microsoft does not always fully document details of changes across product versions, this series of blog posts will attempt to identify any similarities and differences between these two PowerShell editions from the command perspective in a typical deployment, namely that of Windows PowerShell 5.x and the newly Release to Manufacturing/Web (RTM/RTW) GA version of PowerShell Core 6.0.0.

Let us kick start with the topic of Modules where the key functionality of PowerShell resides. Out of the box, executing powershell.exe (<= PS5.1) and pwsh.exe (PSCore6) will load a basic set of commands from core modules with exactly the same names:

ModuleType Version Name
———- ——- —-
Manifest Microsoft.PowerShell.Utility
Script 1.2 PSReadline

Even though module names and versions carry the same information, Read more “#pscore6 v.s. #powershell 5.x Modules”

#powershell v6.0 RTM GA Generally Available and Supported

PowerShell Core 6.0.0

  • a new edition of PowerShell #PsCore6
  • built on top of .NET Core “CoreCLR”
  • cross-platform support from Windows, macOS to Linux (direct download)
  • community driven (GitHub) and open-source
  • built for heterogeneous environments and the hybrid cloud
  • works side-by-side with Windows PowerShell[1] (3.0 and later)
  • $PSVersionTable.PSEdition is set to Core
  • process runs as pwsh(.exe) c.f. Windows Powershell = powershell(.exe)
  • default installation path %programfiles%\PowerShell\
  • starts as Administrator in %programfiles%\PowerShell\6.0.0
  • new user profile path $profile = %userprofile%\Documents\PowerShell
  • different $env:PSModulePath
  • not available features – workflow, WMI[2],  Windows Presentation Foundation/Windows Forms, PowerShell ISE[3]
  • Update-Help -force -UICulture “en-us” (help system independent of Windows Powershell)
  • Windows PowerShell 5.10
    = “maintenance” mode
    =  last Windows client/server version i.e.  no new version planned

[1] built on top of .NET Framework 4.x “FullCLR”
[2] use the equivalent *-CIM* cmdlets
[3] use Visual Studio Code + PowerShell plugin


  1. PowerShell Core 6.0: Generally Available (GA) and Supported!
  2. PowerShell 6.0 Roadmap: CoreCLR, Backwards Compatibility, and More!
  3. Angel Calvo (Twitter): Announcing the GA & Enterprise supported version of #PowerShell Core 6!
  4. Announcing PowerShell for Visual Studio Code 1.0!
  5. What’s New in PowerShell Core 6.0
  6. PowerShell Core Support Lifecycle
  7. PowerShell documentation (en-us)

Zurich Kurs/Course: Windows PowerShell 5.x Basics – Definitiv Start (ab Di. 16. Jan 2018)

Windows PowerShellThe next Windows Powershell 5.x Basics (covers PowerShell Core 6.0) private course IS35.18.12 for a regional bank in Zurich will run in the evenings starting next Tuesday 16 Jan 2018*. If you are interested or have previously registered for the public course IS35.18.11 PowerShell V5.x Einführung (originally start schedule for Tue 9 Jan 2018), you are invited to join and participate in this now open-to-public course instead.

Contact a EB-Zürich staff member or check online for more information today!

Dienstag 16.01.2018 18:00-21:30
Dienstag 23.01.2018 18:00-21:30
Dienstag 30.01.2018 18:00-21:30
Dienstag 06.02.2018 18:00-21:30
Dienstag 13.02.2018 Sportsferien
Dienstag 20.02.2018 Sportsferien

Dienstag 27.02.2018 18:00-21:30
Dienstag 06.03.2018 18:00-21:30
Dienstag 13.03.2018 18:00-21:30
Dienstag 20.03.2018 18:00-21:30

Zurich Kurs/Course: Windows Server 2016 Basics – Definitiv Start (ab Do. 18. Jan 2018)

Der erste, beliebte Windows Server 2016 Basics Kurs (IS36.18.11) dieses Jahres wird am Do. 18. Jan 2018 für insgesamt 6 Abende* in Zürich West, Technopark planmässig beginnen.

Sichern Sie Ihre Plätze zu diesem praxisnahen Microsoft Training für effizientes Betrieb Ihrer On-premise, Hybrid oder Cloud Datacentrelösungen heute noch!

Mehr Information und Anmeldung finden Sie hier.

Donnerstag 18.01.2018 18:00-21:30
Donnerstag 25.01.2018 18:00-21:30
Donnerstag 01.02.2018 18:00-21:30
Donnerstag 08.02.2018 18:00-21:30
Donnerstag 15.02.2018 Sportsferien
Donnerstag 22.02.2018 Sportsferien
Donnerstag 01.03.2018 18:00-21:30
Donnerstag 08.03.2018 18:00-21:30

#skype4b #powershell Get Registrar Pool Names from Cluster Id (msRTCSIP-PrimaryHomeServer)

Instead of legible plain text is a long string describing the distinguished name of the Skype for Business Front-End Server pool in the msRTCSIP-PrimaryHomeServer Active Directory user attribute. This can become difficult to identify and manage if several registrar pools exist in your environment whether they are located in the same or different sites.

To decipher the DN (pool cluster Id) into the fully qualified distinguished name of the corresponding #skype4b pools, Read more “#skype4b #powershell Get Registrar Pool Names from Cluster Id (msRTCSIP-PrimaryHomeServer)”

#powershell Get-Date v.s. [datetime] Format and System Locale III

On a non-US system locale Windows machine[1], running this statement in a #powershell script will fail:

[datetime]$dt1 = (Get-Date).DateTime
Cannont convert value “Dienstag, 12. Dezember 2017 22:20:20” to type “System.DateTime”. Error: “The string was not recognized as a valid DateTime. There is an unknown word starting at index 0.”
At line:1 char:1
+[datetime]$dt1 = (Get-Date).DateTime
+ CategoryInfo : MetadataError: (:) [], ArgumentTransformationMetadataException
+ FullyQualifiedErrorId : RuntimeException

To resolve this, Read more “#powershell Get-Date v.s. [datetime] Format and System Locale III”

#powershell Get a List of Windows Update Hotfixes & Patches

To retrieve a comprehensive list of installed quick fix engineering hotfixes and patches[1] in Windows Update, you export into a format such as CSV with the help of the perennial $env:windir\Windows\System32\Wbem\WMIC.exe tool:

$file = “qfe.csv”
wmic qfe list full /format:csv > $file
#optionally run in MS-DOS
#wmic qfe list full /format:”%windir%\system32\wbem\en-us\csv.xsl” > “qfe.csv”

Subsequently, you can import the Comma Separated Variable file and… Read more “#powershell Get a List of Windows Update Hotfixes & Patches”

#powershell Get-EventLog <-> Get-WinEvent

Inspecting the Event Log (eventvwr.exe) can provide clues to the startup (Event ID 6005*) and shutdown (Event ID 6006) date/time of a Windows machine. To do this, one common approach is with Get-EventLog:

#requires -version 3.0
Get-EventLog -LogName system -ComputerName FS01 | ? EventId -eq 6006

Instead, a more efficient way without the #powershell pipeline can be achieved using Get-WinEvent:

Get-WinEvent -ComputerName FS01 -FilterHashtable @{ LogName=’system’; Id=6006 }

Look out for Event ID 6008 which records the date/time of unexpected system shutdown.

* Event ID: 12 Provider (Source): Kernel-General contains actual operating system start time.