My experience on AzureStack part 3: Changing owner of a AzureStack user subscription

We have some users on-boarded on the AzureStack multi-node system and they do testing and when they forget to remove stuff and we need to make some changes we might need to remove their resources and as Stanislav mentioned there is a way to actually take over a subscription. There is though a small thing that needs to be added to the PowerShell cmds that can change a Azure Stack user subscription owner when you have a multitennant setup of your Stack, your users will have their own tenant ID´s on the subscriptions.

So to be able to access and remove resources from an user that left his subscription and resources burning you will have to do a update on both Owner and TenantId

So set up your enviroment with the AzureStack tools and PowerShell environment, connect as a cloud operator to the default subscription and then run the following::

Happy Stack Operating 🙂

 

Add 2016 shared vhds to VMs fail with backend SOFS running Windows 2012 R2

We are doing some work in adding functionality and found an issue today! We have quite a few workloads running on a converged setup with Hyper-V nodes accessing storage from Scale-Out File Servers.

In our lab environment we have Hyper-V running on Server 2016 and these get their storage from SOFS and they currently run 2012 R2. For ordinary VM´s that has not been a problem. Now we wanted to get the VHD Scale sets (enhanced shared VHDX) set up for guest clusters running guest OS win 2016.

The documentation says not so much more than you need storage residing on a SMB or CSV volume, but when trying to add a VHDs file we get an error stating that the SOFS server does not recognize the file format of the vhd set and think it is a reserved file for windows!

 

Using a SMB share from a bunch of 2016 Scale Out File Servers gives no errors

So upgrade those SOFS servers first and you will not run into problem 🙂

My experience with AzureStack in a multinode setup part 2

Here is my second post on experience with our lovely AzureStack multinode that we now have running.

First of all, there is now a good doc on the AzureStack site for Datacenter Integration and it is really important to read and understand the text. It is also vital to also have the networking guys on the wagon!

For a success in the deployment you will need to have a NAT functionality within your router/fw or have a transparent proxy. The doc says it is needed for the Infra Network that is called public, it is not public reachable but do need internet access. Some routers have advanced functionality with Policy based routing that can send infra traffic to a fw and public VIP traffic directly to and from internet!

Also during deployment the BMC network will need access to internet because the deployment VM running on the HLH will need to do a AAD login and registration if the stack is not being deployed as a disconnected version.

Certificates

Before you can get a deployment up and running you will need to make sure that the certificates that you ordered are rock solid! Follow the documentation and do not take any short cuts in wild card certs etc…

There is a sample cert INF template file that you can use:

Next..

Next post I will go through a bit about the update process, support and marketplace syndication.

 

 

System Center 1801 released, updated vhd eval download script

This week the System Center 1801 was released and I have updated the script to have the new links to the downloadable VHD´s that you can use to evaluate the release.

Happy evaluating and getting started with the latest System Center release 🙂

Running Honolulu on Windows Server 17079

I had Honolulu in an earlier release installed on a Windows Server Insider 17035 build and wanted to try the new feature that came in 17079 with inplace upgrade, that did not however work out as wanted and I had to run a clean VM instead! I have not looked more into why the upgrade failed, probably because the documentation said that it was supported from 1709…

Thanks to the insider system it is already a VHDx there that I could download and use and add it to my domain.

Once that was done I could add the honolulu msi into the VM with the magnificent Copy-VMFile cmdlet

And after a simple install I could connect to it from a Chrome browser! (IE is not supported)

Have fun with your testing of Honolulu!