PowerShell 7 GA

The moment for the largest happening since PowerShell v1 has now happened and that is the general availability of PowerShell 7!

Install on a Mac with OS X

So I had PowerShell Core installed on my mac and also the 7 preview but now I wanted to update with the latest version. Running the pwsh on a terminal I got the 6.2.3.

Of course using Brew I easily can update this to version 7

The brew cask package powershell was already installed as version 6 so what I had to do was force a reinstall using brew cask reinstall powershell and thus get the right version. If you did not have it since before you can use brew cask install powershell and if you do not have brew installed you can check here how to get it.

If I want a short cut to the pwsh on my OS X terminal I add a profile with the settings and then get a nice Windowsy-feeling ?

And voila I can easily start a terminal with PowerShell 7

I will do a followup post on the features and new stuff in PS7 later but this gets you started!

Happy PowerShelling!

Azure App Service vnet integration with Express route

Yesterday we had the opportunity to configure a Azure environment with a ER and building this with a hub-spoke where the spoke had a App Service.

I had help from my colleagues to do the ER and Hub. Then I created a vnet for the subscription for the app service.

I created a /28 vnet and subnet as I wanted to keep the amount of IP´s at a fairly limited level and set up the peering and everything looked great. I provisioned a test-VM and tested to reach the onprem resources and that also worked as expected.

The supplier that we worked with complained though that it did not work to integrate this subnet into the App Service as he got an error when trying.

What I learned after looking a bit more carefully was though that the App Service integration required a /27 subnet that was dedicated for the web service. There are some requirements and limits that you can read on the link below:

https://docs.microsoft.com/en-us/azure/app-service/web-sites-integrate-with-vnet#regional-vnet-integration

I had to remove the VM and also the peering as it is not possible to change the vnet properties ,such as address space, otherwise

With no dependencies I could change the address space to a /26. I wanted a dedicated subnet for the App Service and also a subnet for a VM to test some networking. After creating the subnets and recreated the peering everything worked great, including the integration to the App Service, and just as a coincident it was released as GA to do regional vnet integration.

Learning from this is among other things, to read the documentation first and also not accept the networking departments restricted allocation of network ranges because it will probably end in frustration!

Microsoft Ignite on Tour Stockholm May 5-6

It is time again for Microsoft Ignite on tour in Stockholm and this time it is in May and it will be the last one on the On Tour serie 2019-2020. It will be two packed days with awesome content and learnings! I will of course be there and network and watch sessions..

To register, go to the event site and do it right now, as I have been informed already about 2900 have already done it and the seats may run out!

The different learning paths are :
  • Managing Cloud Operations
  • Azure Fundamentals
  • Journey to Microsoft Teams
  • Securing your organisation
  • Migrating Server Infrastructure
  • Content collaboration, communication, and engagement in the intelligent workplace Learning Path
  • Deploying, managing, and servicing windows, office and all your devices Learning Path
  • Meeting organizational compliance requirements Learning Path
  • Power Platform
  • Microsoft Dynamics 365
  • Modernizing web applications and data Learning Path
  • IT administrator’s guide to managing productivity in the cloud Learning Path
  • Improving reliability through modern operations practices Learning Path
  • Developing cloud native applications Learning Path
  • Develop integrations and workflows for your productivity applications Learning Path

See you there!

MVP Azure 2019-2020

I am thrilled to tell you all that I was once again awarded the Microsoft Most Valuable Professional for 2019-2020.

This time I have moved to the Azure category but still do lot of stuff with the cloud and datacenter management of course, although the main part now is within the Azure/Azure Stack space!

Azure Stack HCI

Today Microsoft announced the Azure Stack HCI and the family of Azure, Azure Stack, Azure Stack HCI is complete to take care of your company all different needs.

So Azure Stack HCI is the new name for the Hyper Converged solution that before was called WSSD and hardware companies certify their solutions to be in the list for Azs HCI.

Azure Stack HCI solutions

There is a hybrid event on the 28th that you can sign up and learn more on that online show.

Or listen on the recording from Jeff and Vijay where they describe more about Azure Stack HCI

Upgrading my homelab to Server 2019

My homelab environment consists of two Intel NUC and I have been playing around with the insiders previews of Server 2019 on one of them and the other one was running Server 2016.

As you might know there is a bit of a hustle of the nic drivers with the server versions of Windows and the Intel NUC´s so there are some steps to get it working. I had some issues where the nic failed during in-place upgrade between preview versions of 2019 and as I do not have a KVM I had to move the NUC to a monitor and fix it. To get the drivers in I had to set the server into test mode:

After I did this and rebooted the server I could update the nic drivers that I already had modified as per this blog post.

I wanted to test and update my 2016 server with an in-place upgrade without moving it from the closet and as a precaution I changed to test mode first and then started the update…

After the upgrade went through successfully I changed back to non-test-mode:

I had a small issue with the Windows Update after the upgrade and it would not finish installing the CU of 2018-12… As a mitigation if this I went for the command line tool of System File Checker, SFC and the parameter /Scannow I also did a Dism repair and after these two successfully ran I could continue with the Windows Update!


Happy NUC-playing with 2019 🙂

Global Update Manager in Win Failover Clusters

Yesterday we experienced some issues in a large hyper-v cluster that had nodes evicting and restarting the cluster service resulting in VM´s beeing restarted on other nodes and that is not great when trying to have a High Available service for the end users.

Reading about the Global Update Manager and how it works and also getting help from the Microsoft CSS helped us getting out of the issue. In default async mode in 2012 R2 the cluster update is commited when a majority of the nodes have processed it, when reading the cluster state the nodes need to check with a majority of the nodes once again to get a valid state so this means more traffic. 

The problem is when you have a large Hyper-V  2012 R2 cluster with lots of cluster resource updates and VMM, SCOM agents hammering the cluster database function gets lots of traffic and that can be cumbersome and at last it might start going bananas and evicting hosts that does not respond in time. Your logs will start filling up with event 5377 and 1135.

GUM cluster synchronous mode

There have been some work under the covers and now the cluster database read write mode has changed to a default of synchronous mode in a Hyper-V 2016 cluster. When doing it synchron it means all nodes in the cluster will process the state and that also means that all nodes have the latest info and thus can read it locally and that means less net traffic!

Default Behaviours in Clusters

Windows Server 2012 R2

Get-Cluster | fl DatabaseReadWriteMode

DatabaseReadWriteMode : 1

Windows Server 2016

Get-Cluster | fl DatabaseReadWriteMode

DatabaseReadWriteMode : 0

ref: https://windowsprivatecloud.wordpress.com/about/configure-the-global-update-manager-gum-mode-in-wfc/

Once we changed to the DatabaseReadWriteMode 0 the cluster became stable. 

My Microsoft Ignite Schedule

I have during the latest weeks been refining my Schedule and now I am getting somewhere about to an gigantic board of valuable sessions that I want to see.

My schedule as of today Friday the 21th of september

And now you start to panic and thing this is caos, and yes in some sense it is but there is a plan with it, and that is if I realize after 5 minutes into a session that either the speaker is a bad preformer or if the session does not seem to fit my interest I can then divert to another one that I added also. There is another reason and that is after Ignite I might want to go back and see what sessions I might want to find the recordings for. 

Regarding the part of your obligations as a business traveler and informing your co-workers at home there is a neat feature that you can use within the scheduler and that is the Trip report

When you press that link you get an word document where you can add your own notes and findings during the sessions and have that handy when getting back into the normal work-mode!

word doc from trip report

I will update with some more great stuff during the week! 

Microsoft Hyper-V 2016 Features list

Quite an impressive list of new stuff in the Hyper-V are with 2016 release, and then you of course also have the new stuff in Clustering and storage to add to this but that will be another blog post 🙂

  • Compatible with Connected Standby (new)
  • Discrete device assignment (new)
  • Host resource protection (new)
  • Hot add and remove for network adapters and memory (new)
  • Hyper-V Manager improvements (updated)
  • Integration services delivered through Windows Update (updated).
  • Linux Secure Boot (new)
  • More memory and processors for generation 2 virtual machines and Hyper-V hosts (updated)
  • Nested virtualization (new)
  • Networking features (new)
  • Production checkpoints (new)
  • Rolling Hyper-V Cluster upgrade (new)
  • Shared virtual hard disks (updated)
  • Shielded virtual machines (new)
  • Start order priority for clustered virtual machines (new)
  • Storage quality of service (QoS) (updated)
  • Virtual machine configuration file format (updated)
  • Virtual machine configuration version (updated).
  • Windows Containers (new)
  • Windows PowerShell Direct (new)

Read more at the technet site here.