Windows Server 2016 is now available on Azure

So the day has come when Windows Server have arrived at Microsoft Azure and you can start deploying your new workloads.

You either find the different flavours from the portal or from PowerShell


And the command for finding them with PowerShell AzureRM module is

and running it looks like this:


Good luck in deploying!


AzureStack TP2 – deploy experience

During Ignite 2016 in Atlanta, Microsoft announced the technical preview 2 of AzureStack and finally now this friday I got my hardware available (the dang server was not responding on the ILO port and I had to go to the datacenter to give it a kung-fu-devops-kick) so I could deploy the new bits.

First things first! Read the documentation about how to proceed and you will more likely succeed in your deployment!

The download for AzureStack is 20 GB so if you have a slow internet connection it will take some time!

Before getting started i suggest you to run the pre-check script that can tell you if there is some immediate issues,


And then you can unpack and follow the instructions to prepare to vhd-boot into the cloudbuilder disk with the next script:


Once rebooted you want to make sure that you only have one nic enabled and then kick of the deployment which will take about 2-3 hours if you have a decent hardware like me 😛


As you can see the install process uses both desired state and powershell direct (which is a lovely feature in Hyper-V 2016)


And if you are patient and then log in as a azurestack\AzureStackAdmin on the physical machine you will see the status of the deployment. Do not log in as a local user on the server and try to start the deployment again!

Hopefully you will end up with the same result as me:


And then you can log in to the VM MAS-CON01 to connect to the portal,


Maybe I was lucky but I believe that the Stack-Team has done some serious work since TP1 and the deployment process have been thoroughly developed, tested and works really good now.

Good luck in your deployment of Azurestack TP2!


Best sessions of Ignite 2016

So last week I was at Microsoft Ignite in Atlanta and had a great time with all attendees and speakers and the wonderful staff that guided all of us 23 000+ there!


Of course the Swedish Chef tagged along and was hanging with some cool people! And as you can see in low right corner, my friend Fredrik could not be at Ignite in person but had the brilliant possibility to join with a remote controlled robot that he explored the different areas with…

There was some good stuff presented there also and here is a list of the best sessions and there are probably a hundred more that I have not seen yet so there might be a revised list later 😉 :


If you as I want a big library of ppt´s and videos of this event you can go to your friend PowerShell and download all available presentations with a great script from Mattias and Michel. So start exploring and please add your favorites in the comments below!

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.


Download SysCtr 2016 VHD eval with PowerShell

Hi and hello,

As you maybe know by now the System Center 2016 suite and Windows Server 2016 was released this week during the Ignite conference in Atlanta

I have updated my script that you can use to download the Evaluation VHD´s with all System Center 2016 roles in an easy format ready to import into Hyper-V

Enjoy and start playing!


PowerShell disappeared or…..

Utilizing the mighty Irwin´s Operation testing in the environment I am building and administrering right now is great success. I have set up a scheduled task that runs every morning and giving me a nice report about the status of the environment and if someone have done reconfigurations or just services being down for any reason.

This week though the scheduled task started to failing.

Apparently someone had done some mistreatment to my environment path so the powershell.exe could not be found any more from CMD thus the scheduled task failing..

Screen Shot 2016-09-02 at 11.11.39

First off I could see that a %path% had snuck into, in CMD ECHO %path% shows all paths so some failure during a PS-script as in powershell %path% does not give love in the same way as the cmd console.

There could be other ways but one easy way is to find another server having the path untouched and removing the %path% from this server and adding the right way to system32 and powershell….

Screen Shot 2016-09-04 at 17.15.47

And then to correctly set the path (if you just use $env:path = $real It will only set it for the current session and not being persistent and in this case it is not enough :

Screen Shot 2016-09-04 at 17.16.32

And once that have been done I could verify that powershell was once again found within the CMD

Screen Shot 2016-09-02 at 11.17.31

PowerShell opensourced woop woop

You might have noticed on twitter and other media that now PowerShell has been released as open source and also available not only for your windows environment but also now for Linux and OS X 🙂

The release is available on Github and go there to get your preferred package for your OS! Read the instructions and be aware that this is the first step and the packages for the non-windows is in alpha!

I have a Mac with OS X and have of course installed it

Screen Shot 2016-08-18 at 16.08.36
Screen Shot 2016-08-18 at 16.09.34

Read some more on Snovers blog post here if you want some more insight in why and how and also some cool demos !

Happy powershelling!!

AWS Cloudwatch – watch out for outdated EC2config

I configured a Windows instance on AWS to start reporting logs and performance counters into their AWS Cloudwatch for centralised overview.

The day after I had started monitoring I found that it was consuming loads of CPU and memory and thus not normal,

Screen Shot 2016-07-14 at 12.01.01

Going into the instance, which took a while as it was so sluggish, I found that the EC2Config service was going berserk and I had to kill it.

Screen Shot 2016-07-14 at 10.53.59

Looking at the properties of the EC2 you can see that it was and far from the version available today.

Screen Shot 2016-07-14 at 11.12.56

So if you want to enable Cloudwatch make sure that you first update the EC2config to be sure that your server will survive the burden of monitoring  ?

Firmware update of NIC makes team go degraded

I have been doing some maintenance on a Hyper-V environment and patching with Windows updates and also firmware for the hardware.

The hosts was Dell R730 with former Broadcom and now Qlogic 10 Gbit NIC´s. There are 4 10 Gbit NIC´s on every host and they are set up with one team for management and one team for VM´s.

I have done firmware update before but now there was a new version that I wanted to apply.

It tock a while before I realised that the NIC`s had changed name and thus that was why the teams was degraded, we had some discussions and the Networking guy checked his configuration more than once and we also verified the cabling on the server and then after a while I realised that the NIC actually had changed name and once adding the correct NIC´s to the teams the status changed to normal!

Screen Shot 2016-06-23 at 10.33.14

So when doing maintenece please check the status after updating firmware or the battle with the networking guys can end in misery on your side 😉