Tag: update

Install or Update PowerShell 6 on Windows 10

How to Install and Update PowerShell 6

Today Windows 10 and Windows Server 2019 ship with Windows PowerShell 5.1 as the default version. PowerShell Core 6 is a new edition of PowerShell that is cross-platform (Windows, macOS, and Linux), open-source, and built for heterogeneous environments and the hybrid cloud. PowerShell 6 today is a side by side version next to Windows PowerShell 5.1. That means on Windows you cannot just upgrade to PowerShell 6, you will need to install it, same as on Linux and macOS. This blog post just shows you how simple you can install PowerShell 6 or update PowerShell 6, if you have already installed it, on Windows 10, Windows Server 2019 or Linux.

Of course you can find great documentation out there on Microsoft Docs. However, Steve Lee (Microsoft Principal Software Engineer Manager in the PowerShell Team) shared some one-liner, which help you easily install and update PowerShell 6.

Install PowerShell Core 6

Before showing you the one-liner option to install PowerShell 6, I want to share with you the documentation to install PowerShell Core 6 on different operating systems like Windows, macOS and Linux.

One-liner to install or update PowerShell 6 on Windows 10

Install or Update PowerShell 6 on Windows 10

You can use this single command in Windows PowerShell to install PowerShell 6.

There are additional parameters to for example install daily builds of the latest PowerShell previews.

The destination path to install PowerShell Core to.

Install PowerShell Core from the daily build.
Note that the ‘PackageManagement’ module is required to install a daily package.

Install latest preview.

Use MSI installer.

Quiet command for the MSI installer.

Do not overwrite the destination folder if it already exists.

On Windows, add the absolute destination path to the ‘User’ scope environment variable ‘Path’;
On Linux, make the symlink ‘/usr/bin/pwsh’ points to “$Destination/pwsh”;
On MacOS, make the symlink ‘/usr/local/bin/pwsh’ points to “$Destination/pwsh”.

For more about installing PowerShell 6 on Windows, check out the Microsoft Docs.

One-liner to install or update PowerShell 6 on Linux

Install or Update PowerShell 6 on Linux

You can use this as a single command to install PowerShell 6 on Linux

Depending on your distro you are using, this will register Microsoft’s pkg repos and install that package (deb or rpm).

For more about installing PowerShell 6 on Linux, or if you want to install PowerShell Core 6 on macOS, check out the Microsoft Docs.

After Installing

After you have installed PowerShell 6, also make sure to update PowerShellGet and the PackageManagement module.

By the way, PowerShell 6 is also used in the PowerShell version of Azure Cloud Shell. You can of course also install the Azure PowerShell module in PowerShell 6.

Updated PowerShellGet and PackageManagment

Update PowerShellGet and PackageManagement

Since I am just setting up a new work machine, I wanted to share some information how you can update PowerShellGet and PackageManagement to the latest version. This will give you the usual bug fixes and performance enhancements. Since you don’t get the latest version in Windows PowerShell nor PowerShell Core, you will need to update it manually.

PowerShellGet is a PowerShell module with commands for discovering, installing, updating and publishing the PowerShell artifacts like Modules, DSC Resources, Role Capabilities and Scripts. For example you use PowerShellGet to install the Azure PowerShell module, or other modules.

PowerShellGet module is also integrated with the PackageManagement module as a provider, users can also use the PowerShell PackageManagement cmdlets for discovering, installing and updating the PowerShell artifacts like Modules and Scripts.

(source: GitHub)

How to update PowerShellGet and PackageManagement

Updating to the latest version of PowerShellGet and the PackageManagement module is simple. Since both modules are part of the PowerShell Gallery, you can update them using a couple of simple commands.

You can find both modules in the PowerShell Gallery:

First lets check which versions of the modules you have available. If you use Update-Module, it will automatically load PowerShellGet and PackageManagement and list them as loaded PowerShell modules. Of course you can also use Get-Module -ListAvailable.

PowerShell Modules PowerShellGet and PackageManagement

As you can see, In my default installation, I got PowerShellGet version 1.6.7 and PackageManagement If you have a look at PSGallery, you will see that these are pretty old versions and that there are newer available.

To get the latest version from PowerShell Gallery, you should first install the latest Nuget provider. You will need to run PowerShell as an Administrator for all  the following commands.

If you run PowerShell 5.0 or newer, you can install the latest PowerShellGet using the following command. PowerShell 5.0 is included in Windows 10, Windows Server 2016, Windows Server 2019, any system with WMF 5.0 and 5.1 or a system running PowerShell 6.

Two quick tips, first of, you will need to set the execution policy to RemoteSigned to allow the new module to run. Secondly in some cases you will need to use the -AllowClobber parameter to install the updated version of the module.

You can then use Update-Module to get newer versions:

Updated PowerShellGet and PackageManagment

After that you will see the latest versions of PowerShellGet and PackageMangement available

If you run older versions of PowerShell you can check out the full documention on the PowerShell Docs. I hope this blog post helps you to update PowerShellGet and benefit from the latest versions. If you have any questions, please let me know in the comments.

Windows Server 2019 Upgrade

Windows Server 2019 In-place Upgrade

As another part of my series for Windows Server 2019, this blog post covers the in-place upgrade feature. In-place upgrade allows you to upgrade your existing LTSC versions of Windows Server 2012 R2 or Windows Server 2016 servers to Windows Server 2019. Windows Server 2019 In-place Upgrade allows businesses to quicker update to the latest version. Especially, if you have servers which you might needed to install some dependencies for the applications. I saw a lot of customers which not have documented their server installations and neither used infrastructure as code to deploy them. For these customers it can be hard to upgrade to newer versions of Windows Server. With the Windows Server 2019 In-Place Upgrade feature, this should get a lot easier. Especially since Windows Server 2019 bring a lot of improvements.

You can in place upgrade to Windows Server 2019 from

How to in place upgrade to Windows Server 2019

Windows Server 2016 upgrade to Windows Server 2019

To in place upgrade to Windows Server 2019, just insert the Windows Server 2019 media into the existing server, by attaching an ISO file, copying the sources, inserting a USB drive or even a DVD drive and start the setup.exe.

Installing Windows Server 2019

The setup will discover the existing installation and will let you perform an in place upgrade. The installation will run for a couple of minutes, it will take quiet some time depending of the speed of your server hardware and of the installed roles and features. Microsoft MVP Didier Van Hoye, did write a great blog post about Windows Server 2019 In-Place Upgrade testing. In that blog post he has a quick look on upgrading to Windows Server 2019.

You can also find a overview about what is coming new in Windows Server 2019, in my blog: Windows Server 2019 – What’s coming next.

Download Azure Stack Update

How to install and manage Azure Stack Updates

At itnetX, we help customers to implement as well as to operate  Azure Stack. One part of operating Azure Stack is keeping it up-to-date. This means installing Microsoft Azure Stack Updates, hotfixes as well as OEM update packages like drivers and firmware. In this blog post I will cover all the information you need to keep your Azure Stack up-to-date.

Why should you update your Azure Stack

Azure Stack Update

This may sound like a simple question, but a lot of people ask for it. First of all, Microsoft and the hardware vendors are obviously delivering quality fixes and security updates to keep Azure Stack stable and secure. But Microsoft also adds new functionality with their updates packages to keep up with the rapid cloud development on Azure. This is important if you want that your Azure Stack stays consistent with Azure in terms of functionality.

Another important reason to stay current is to stay supported. You are allowed to be behind two major versions of Azure Stack, which means 2-3 months. You basically should update monthly, to make sure that you are secure and stable, however there are reasons why you might have to defer an update. For example, this can happen for some companies, when they are in a freeze period where they are not allowed to do changes in their systems. If you are more than 3 major versions behind, your Azure Stack is considered out of support and will not be supported from Microsoft, until you have the at least required version installed.

You can read more about the Azure Stack servicing policy on the Azure Stack documentation site.

Updates for the Azure Stack Integrated System

Azure Stack Operations

As mentioned before, there are basically three types of updates to Azure Stack. The monthly Azure Stack Update Packages from Microsoft, Hotfixes and OEM updates.

  • Microsoft software updates – Microsoft is responsible for the end-to-end servicing lifecycle for the Microsoft software update packages. These packages can include the latest Windows Server security updates, non-security updates, and Azure Stack feature updates. These update packages are non-cumulative updates and need to be installed one after the other. These updates are fully automated and will update the complete Azure Stack infrastructure.
  • OEM hardware vendor-provided updates – Azure Stack hardware partners are responsible for the end-to-end servicing lifecycle (including guidance) for the hardware-related firmware and driver update packages. In addition, Azure Stack hardware partners own and maintain guidance for all software and hardware on the hardware lifecycle host.
  • Microsoft hotfixes – Microsoft provides hotfixes for Azure Stack that address a specific issue that is often preventative or time-sensitive. Each hotfix is released with a corresponding Microsoft Knowledge Base article that details the issue, cause, and resolution. Hotfixes are downloaded and installed just like the regular full update packages for Azure Stack. Other the the major updates, Azure Stack hotfixes are cumulative per iteration.
 ReleaseCumulativeWhere to find
Microsoft Software UpdatesMonthly (4th Tuesday of very month)NoRelease Notes
OEM Hardware Vendor UpdatesDepending on OEMDependsOEM Website
Microsoft HotfixesWhen neededYesKnowledge Base article

By the way, you can only update Azure Stack multi-node systems, the Azure Stack Development Kit needs to be redeployed.

System Center Logo

Summary: Update Rollup 7 for System Center 2012 R2 and Azure Pack now available

Last week Microsoft released Update Rollup 7 (UR7) for System Center 2012 R2 and Windows Azure Pack. And as always, Update Rollup 7 does not only include a bunch of fixes, it also includes some new features. This time especially Windows Azure Pack and System Center Virtual Machine Manager got some nice updates. Components that are fixed and updated in this update rollup

  • Data Protection Manager (3065246)
    • Support for Windows 10 Client operating system
    • Ability to use an alternative DPM server to recover from Azure Backup Vault
    • Improvements for backup on Hyper-V Replica VMs
    • Other improvements and fixes…
  • Orchestrator & SMA (3069115)
    • Orchestrator: some small fixes
    • SMA
      • SMA runbook execution fails if a PowerShell execution policy is set to Unrestricted through a Group Policy Object.
      • Fixed an error when you try to save or import a runbook in SMA
  • Operations Manager (will be released later)
    • The rollup is delayed by few weeks, as engineering team is working on recently reported issues.
  • Service Manager (3063263)
  • Service Provider Foundation (3069355)
    • This update includes general API changes to improve product quality.
  • Virtual Machine Manager (3066340)
    • Support for Windows 10 Client Operating System
    • Support for new Linux Operating Systems (Debian 8)
    • Support for VMWare vCenter 5.5 management scenarios (more infos VMWare vCenter 5.5 management scenarios)
    • Support for Multiple External IP Addresses per Virtual Network
    • Option to Reassociate Orphaned virtual machines to their Service or VM role
    • Support for VMM DHCP Extension PXE/TFP Forwarding
    • Some scale improvements if you have more than 50 Hyper-V Hosts
    • Some Hyper-V Network Virtualization (HNV) fixes and improvements
    • Other fixes…
  • Windows Azure Pack (3069121)
    • Tenants cannot delete the checkpoints of their virtual machines
    • Support for VM names of up to 15 characters
    • Displaying VHD items during virtual machine creation when there are no hardware profiles in the plan
    • Incompatible VHDs are offered to the tenant when attaching a VHD to a virtual machine
    • Support for tenant plan viewing and self-subscription permission based on security groups
    • Support for Shielded Virtual Machine Management when it’s run on Windows Server 2016 Preview
    • Virtual Machine performance data displayed in the tenant portal
    • Other fixes and improvements…
  • Windows Azure Pack Web Sites (3069358)
    • Adds support for IPv6 to IP SSL functionality
    • Changes Web Deploy publishing from publish.domain.com to site.scm.domain.com.
    • Other fixes and improvements…

One of the new features I want to highlight is the possibility to add multiple public (external) IP addresses to  Virtual Network (Using Hyper-V Network Virtualization HVN). This means a tenant can assign multiple public IP addresses on his NAT gateway and do port forwarding, for example if he runs multiple webservers in that VM Network. This is a feature a lot of customers especially service provider have missed for a long time.

Another improvement we can see is the support for the next release of Windows Server and also support for Windows 10.


Windows 10 Task View

The best Windows 10 Features – Why you will love Windows 10

Since the first release of the Windows 10 Preview in the Insider program, I was using the Technical previews on my Surface Pro 3, and it is great how Microsoft is improving Windows 10 over the last several months based on research and feedback from the Windows Insider program.

In some days, at July 29, Microsoft will release Windows 10 to the public, and here are some reasons why you will love Windows 10:

Microsoft Edge

Microsoft Edge Browser

With Windows 10 Microsoft released a new browser called Microsoft Edge (before Project Spartan) which is amazing fast and brings a lot of new features to the table such as Cortana Integration, Web notes which allow you basically draw your notes on websites and share them and Microsoft also promised to allow browser extensions. Secret: you can also switch from a Light Theme to a Dark Theme.

Task View & Virtual Desktop

Windows 10 Task View

Most of the IT Pros reading this blog already knew about Task view in previous version of Windows using WIN + TAB, but only a few other users did know about this features. Microsoft not only improved the Task view, Microsoft also promoted it much better  with an icon in the Taskbar.

In Windows 10 WIN + TAB does not only offer you Task View it also allows you to create and switch between Virtual Desktops. With Virtual Desktops you can now finally create multiple workspaces on your PC, which should bring you the productivity boost you need. Secret: You can switch between different Desktops using the Shortcut: CTRL + WIN + ARROW (LEFT and RIGHT).


Hyper-V vNext Runtime Memory Resize

Microsoft build Hyper-V directly into the Windows Client since Windows 8. This is great if you want to run Virtual Machines on your Windows Client. Windows 10 Client Hyper-V brings you the great performance and features Windows Server 2016 Hyper-V will bring you. Of course some features are only available in the server build of Hyper-V, but you get some great features such as Enhanced Session mode to copy & past between your PC and your Virtual Machine. Secret: Windows 10 will allow you to run Hyper-V and use Connected Standby at the same time.

Update Rollup 5 for System Center 2012 R2

Summary: Update Rollup 5 for System Center 2012 R2 and Azure Pack now available

Yesterday Microsoft released a new Update Rollup for System Center 2012 R2 and Azure Pack called Update Rollup 5. Update Rollup 5 has a lot of fixes and new features especially for Windows Azure Pack and System Center Virtual Machine Manager and Data Protection Manager.

Components that are fixed in this update rollup

  • Data Protection Manager (KB3021791)
    • Protect SharePoint with SQL Always on Configuration
    • Protect SharePoint Server, Exchange Server, and Windows Client workloads to Microsoft Azure by using Data Protection Manager
    • Support for multiple retention ranges for long-term backup on Microsoft Azure
    • Ability to transfer initial backup copy offline to Azure
    • Support for protecting Microsoft workloads that are hosted in VMware
    • Display missed SLA alerts on the Data Protection Manager console
    • Enhanced reporting with Data Protection Manager central console
  • Operations Manager (KB3023138)
  • Service Manager (KB3009517)
  • Virtual Machine Manager (KB3023195)
    • Differencing disk as an option in the Windows Azure Pack VMRole deployment
    • New operating system support
    • New ExplicitRevokeRequired parameter to control IP address management when Grant-SCIPAddress is used
    • Support for SQL Server 2014
    • Azure Site Recovery
  • Windows Azure Pack (KB3023209)
    • Adds support for SQL Governor in the SQL Server Resource Provider.
    • Adds administrator support for disabling native Network RP to allow for third-party network provider
    • Provides detail on Virtual Machine Memory type, Memory Startup and Maximum values in the Tenant Portal.
    • Fix to the Get-MgmtSvcRelyingPartySettings PowerShell cmdlet.
    • Fix to the issue of failing to establish Remote Desktop Connection to virtual machines put behind a Network Address Translation (NAT) device.
    • Fix to the Attached Network dialog box where the network entries in the list were disabled.

As you can see you get several new feature with Update Rollup 5. In Data Protection Manager you finally get support for SharePoint, Exchange and Windows Client workload protection to Microsoft Azure, and support for workloads running on VMware infrastructure. Virtual Machines Manager not only brings new features such as support for the Virtual Machine Manager Database to run on SQL Server 2014 it also includes a lot of fixes and a security update (3035898
MS15-017: Vulnerability in Virtual Machine Manager could allow elevation of privilege: February 10, 2015). Some of the most interesting fixes for me are:

  • DHCP extension: Currently, users have to manually update the DHCP extension after update rollup installation on all hosts. This is now automated. After the DHCP extension is replaced in the Virtual Machine Manager server’s installation folder to the latest version, Virtual Machine Manager automatically checks the DHCP extension against all hosts. If the host has an older version of DHCP extensions, the agent version status will be displayed as “DHCP extension needs to be updated in host properties on the Status page.” The user calls the update agent and updates the DHCP extension on the Hyper-V host in the same way that the user did this for the Virtual Machine Manager agent. Also, if the VSwitch is a logical switch, the status will be shown in “logical switch compliance.” The user can remediate the logical switch. This will also update the DHCP extension on the host.
  • Bare-Metal Deployment: If a physical computer profile is created by using vNic (and by using a virtual machine network) and if there are more than one hostgroup for a logical network that also has that virtual machine network when you add a host resource on the “Provisioning Options” page, the host profile will be displayed for only one host group. The profile won’t be displayed for the rest of the host groups.

For Windows Azure Pack also includes some important fixes and improvements on of the is in the Tenant Portal, users can now see details on Virtual Machine Memory type, Memory Startup and Maximum values.

Update Rollup 5 for System Center 2012 R2 brings a lot of new features and important fixes to the table, however before deploying the fixes in your production environment, I recommend to test the Update Rollup and maybe wait for some reports about issues from other users.