Azure Stack TP2 Deployment Issue step 0.20

Last week i finally got my first Azure Stack TP2 deployment completed after weeks of error’s as a blogged before.  After that i needed to redeploy several times and ran into different issue’s every time.

This time it stopped at step 0.20. After retrying the deployment with:


Invoke-EceAction -RolePath Cloud -ActionType Deployment -Start 0.20 -Verbose

It stopped at the same error. See below for te error message.

2016-11-08 20:45:06 Verbose  VMs to create: MAS-BGPNAT01
2016-11-08 20:45:06 Verbose  Updating management nodes for HyperConverged deployment.
2016-11-08 20:45:12 Verbose  Skipping deployment of the VM named 'MAS-BGPNAT01'. It is accessible via remote Powershell.
2016-11-08 20:45:12 Verbose  Waiting for the following VMs to be remotely accessible: MAS-BGPNAT01.
2016-11-08 20:45:13 Verbose  The VM 'MAS-BGPNAT01' has successfully started.
2016-11-08 20:45:15 Error    Task: Invocation of interface 'Deployment' of role 'Cloud\Fabric\VirtualMachines' failed:
Function 'Add-GuestVMs' in module 'Roles\VirtualMachine\VirtualMachine.psd1' raised an exception:
The WS-Management service cannot process the request because the XML is invalid.
at Wait-VMPSConnection, C:\CloudDeployment\Roles\VirtualMachine\VirtualMachine.psm1: line 1683
at Add-GuestVMs, C:\CloudDeployment\Roles\VirtualMachine\VirtualMachine.psm1: line 265
at <ScriptBlock>, <No file>: line 18
2016-11-08 20:45:15 Verbose  Step: Status of step '(NET) Deploy BGP VM' is 'Error'.
2016-11-08 20:45:15 Error    Action: Invocation of step 0.20 failed. Stopping invocation of action plan.
2016-11-08 20:45:15 Verbose  Action: Status of 'Deployment-Phase0-DeployBareMetalAndBGPAndNAT' is 'Error'.

The MAS-BGPNAT01 VM was accessible and i didn’t notice any errors in relation to the error above in the eventlogs. After a reboot of the MAS-BGPNAT01 VM I started the deployment from step 1, without the -start parameter:

Read more


Azure Stack TP2 Deployment Issue with Timezone

Oke, let me first start of a special thanks to my colleague’s Hans Vredevoort, Darryl van der Pijl and Mark Scholman for leading me to the solution!

Since the release of Azure Stack TP2 i did not found the time to start a deployment and play around with Azure Stack TP2. Tp1 was unstable and had a lot of strange issue’s were TP2 was much more stable I was told.. But for the past view weeks I have ben struggling with the deployment!

I’ve deployed it over and over and it keept failing on error in step 60.140.145 were the VM’s were registered at the Compute Controller.

2016-10-24 04:38:18 Error 1> 2> Task: Invocation of interface 'Migrate' of role 'Cloud\Fabric\VirtualMachines' failed: 
Function 'Add-CpiObjects' in module 'Roles\VirtualMachine\VirtualMachine.psd1' raised an exception:
Failed to register virtual machine 'MAS-NC01' with compute controller. Operation failed with: 
Exception calling "GetResult" with "0" argument(s): "MakeReservation VM:36fae812-1703-4198-b0ae-39075e77e2ef Cluster:S-Cluster"
At C:\CloudDeployment\Roles\VirtualMachine\VirtualMachine.psm1:2118.
+ $eceVm.Name
at Trace-Error, C:\CloudDeployment\Common\Tracer.psm1: line 52
at Add-CpiObjects, C:\CloudDeployment\Roles\VirtualMachine\VirtualMachine.psm1: line 2118
at <ScriptBlock>, <No file>: line 18

Since I was on a VLAN tagged network and had no DHCP I was suspecting that one of these parameters –PublicVLan -NatIPv4Subnet -NatIPv4Address -NatIPv4DefaultGateway were giving me a hard time deploying TP2. But after adding a DHCP and change my VLAN to native/untagged so I wouldn’t need the parameters I still ended up at the same error!

Read more


Go Hyper-converged with S2D

Windows Server 2016 is getting to it’s final RTM state within several months now. After that time we can start using Windows Server 2016 Storage Spaces Direct (S2D) for production environments and start using Hyper-converged stacks.

I’m not going to explain how Storage Spaces Direct works, this is just a blog about the setup. If you want some more info about S2D check out this link for an overview and for te more tech guys or girls look here.

I have spend some lab time setting up en using Storage Spaces Direct (S2D) and use Hyper-converged hosts and started this blog to share some info.

Beware that the info below is Lab stuf. I’ve taken some shortcuts to be able to setup S2D on VM’s with Virtual disks. So do not use this commands for you’re own setup, unless you are also running tests in VMs.

General Info

I have 2 VM’s running on a Windows Server 2016 TP5 physical box. The VM’s are enabled for nested virtualization to make sure a can start VM’s on the VM’s. Both VM’s have 10 disks attached to them. So no shared VHD, just 10 .vhdx files to both VM’s which makes a total of 20 .vhdx files. The VM’s are also running Windows Server 2016 TP5.

Create and attach disks

To create and attach the disks I used some powershell commands. I have 2 “Hosts” HV-01 and HV-02.

Read more


Azure Stack TP 1.1 Multi-Compartment Network Proxy Service

Since Azure Stack TP 1.1 i have an issue deploying Azure Stack. After a while it fails with the error below:
MultiCompartmentNetworkProxyServiceError
Service 'Multi-Compartment Network Proxy Service (MultiCompartmentNetworkProxyS
ervice)' cannot be stopped due to the following error: Cannot stop MultiCompart
mentNetworkProxyService service on computer '.'.
    + CategoryInfo          : CloseError: (System.ServiceProcess.ServiceContro 
   ller:ServiceController) [Restart-Service], ServiceCommandException
    + FullyQualifiedErrorId : CouldNotStopService,Microsoft.PowerShell.Command 
   s.RestartServiceCommand
    + PSComputerName        : xRPVM.AzureStack.local

I want to point out that i am not running all official requirement for the Azure Stack Deployment, since i am not booting from the included .vhdx file because i am a bit short on disk space. So this issue might not occur if you follow all the rules… 🙄

But since this issue took me a while to overcome and it’s the second time this happens I though I write a quick blog about it.

Read more


Windows 10 Mobile Continuum with Azure Remote App

“Continuum turns your phone into a big-screen projector and a big-time productivity tool”. That’s what the marketing department of Microsoft says. A lot of media is also shouting out “Turn you phone into a PC”.  But is it true? I have been working with Windows 10 and Windows 10 Mobile for almost a year now and I am a huge fan! I have had my frustrating moments in the insider preview program with mostly Windows 10 mobile but  at the end it’s really a good OS with lost of features and capabilities.

For a project I was able to work with a Lumia 950XL with Windows 10 Mobile and a Microsoft Display Dock to use and work with Continuum and Azure Remote App. In this blog I share some of my findings and thoughts.

How does it work

With Continuum and the Display Dock you can connect your phone to a big screen, keyboard and mouse like on a full desktop/laptop. I say ‘like’ on purpose because of course it’s not the same. More on that later on.

WP_20160322_09_42_45_Pro_LI (2)

When you connect the display dock or connect to a device with a Display Dock you have a separate screen. Everything you do there is not displayed on the phone, so it’s not duplicating a screen but more a separate desktop. Duplicating is an option to do but then you’re not using Continuum

Read more


Remove Azure Stack TP1 to install TP1.1

If you tried out Azure Stack Preview 1 and want to play arround with TP 1.1 release you have to remove the current Azure Stack deployment. I was unable to find a documented uninstall (if somebody does please leave a comment 🙂 ) so i just deleted everything.

I have a one node setup so here is what I did:

  • Turn of all VM’s
  • Deleted all cluster roles;
  • Removed the VM’s;
  • Destroyed the cluster;
  • Removed the storage pool and its volumes;
  • Removed my node from the azurestack.local domain and rebooted;
  • Removed the virtual switch;
  • Uninstalled the Microsoft Azure Service Fabric from my host.

Read more