Azure Stack TP3 is out! My quick review and update

By Mark Scholman17 commentsAzure Resource Manager, Compute, Microsoft Azure Stack, Networking, Powershell, StorageAzure Resource Manager, Azure Stack, Compute, Mark Scholman, Microsoft Azure Stack, Networking, Powershell, Storage, TP3

So TP3 is here and i quickly downloaded the bits and installed some systems. Here a quick wrapup of my experience so far.

First, some parameters are changed as well the folder to start the install from. Find here an example to start the deployment once you have the VHDX installed on the server:

#Using Azure AAD
cd C:\CloudDeployment\Setup  
$adminpass = ConvertTo-SecureString "<PASSWORD>" -AsPlainText -Force 
$aadpass = ConvertTo-SecureString "<PASSWORD>" -AsPlainText -Force 
$aadcred = New-Object System.Management.Automation.PSCredential ("serviceadmin@<AADTENANT>.onmicrosoft.com", $aadpass)  
.\InstallAzureStackPOC.ps1 -AdminPassword $adminpass -InfraAzureDirectoryTenantAdminCredential $aadcred -InfraAzureDirectoryTenantName <AADTENANT>.onmicrosoft.com

#Using ADFS
cd C:\CloudDeployment\Setup  
$adminpass = ConvertTo-SecureString "<PASSWORD>" -AsPlainText -Force 
.\InstallAzureStackPOC.ps1 -AdminPassword $adminpass -UseADFS

#Using Azure AAD

cd C:\CloudDeployment\Setup

$adminpass = ConvertTo-SecureString "<PASSWORD>" -AsPlainText -Force

$aadpass = ConvertTo-SecureString "<PASSWORD>" -AsPlainText -Force

$aadcred = New-Object System.Management.Automation.PSCredential ("serviceadmin@<AADTENANT>.onmicrosoft.com", $aadpass)

.\InstallAzureStackPOC.ps1 -AdminPassword $adminpass -InfraAzureDirectoryTenantAdminCredential $aadcred -InfraAzureDirectoryTenantName <AADTENANT>.onmicrosoft.com

#Using ADFS

cd C:\CloudDeployment\Setup

$adminpass = ConvertTo-SecureString "<PASSWORD>" -AsPlainText -Force

.\InstallAzureStackPOC.ps1 -AdminPassword $adminpass -UseADFS

Then after just 4 hours TP3 is installed. The password policy issue is still active, so update the password policy if you want to use your POC longer than 40 days! You might also be used to install AzureRm version 1.2.6, but in TP3 we can use 1.2.8. Be aware of that too.

I use this script to quickly connect to Azure Stack with PowerShell

Install-Module -Name AzureRM -RequiredVersion 1.2.8
Install-Module -Name AzureStack

set-location C:\Users\AzureStackAdmin\Desktop
Invoke-WebRequest -UseBasicParsing -Uri https://github.com/Azure/AzureStack-Tools/archive/master.zip -OutFile master.zip
Expand-Archive -Path .\master.zip -DestinationPath . -Force
$Folder = New-Item -ItemType Directory -Path ~\Documents\WindowsPowerShell\Modules -Force
Get-ChildItem -Path .\AzureStack-Tools-master -Directory | ForEach-Object -Process {
    if (Get-ChildItem -Path $_.FullName -Filter *.psm1) {
        $PSM1 = Get-ChildItem -Path $_.FullName -Filter *.psm1
        Copy-Item -Path $_.FullName -Destination "$($Folder.FullName)\$($PSM1.BaseName)" -Recurse
        New-ModuleManifest -Path "$($Folder.FullName)\$($PSM1.BaseName)\$($PSM1.BaseName).psd1" -RootModule $PSM1.BaseName
    }
} 
#endregion

$Password = ConvertTo-SecureString "<PASSWORD>" -AsPlainText -Force
$AadTenant = Get-AzureStackAadTenant -HostComputer 192.168.200.65 -Password $Password

# Use this command to access the administrative portal
Add-AzureStackAzureRmEnvironment -AadTenant $AadTenant -Name AzureStack
# Use this command to access the tenant portal
Add-AzureStackAzureRmEnvironment -AadTenant $AadTenant -ArmEndpoint https://publicapi.local.azurestack.external -Name AzureStack

Login-AzureRmAccount -EnvironmentName "AzureStack" -TenantId $AadTenant

Install-Module -Name AzureRM -RequiredVersion 1.2.8

Install-Module -Name AzureStack

set-location C:\Users\AzureStackAdmin\Desktop

Invoke-WebRequest -UseBasicParsing -Uri https://github.com/Azure/AzureStack-Tools/archive/master.zip -OutFile master.zip

Expand-Archive -Path .\master.zip -DestinationPath . -Force

$Folder = New-Item -ItemType Directory -Path ~\Documents\WindowsPowerShell\Modules -Force

Get-ChildItem -Path .\AzureStack-Tools-master -Directory | ForEach-Object -Process {

if (Get-ChildItem -Path $_.FullName -Filter *.psm1) {

$PSM1 = Get-ChildItem -Path $_.FullName -Filter *.psm1

Copy-Item -Path $_.FullName -Destination "$($Folder.FullName)\$($PSM1.BaseName)" -Recurse

New-ModuleManifest -Path "$($Folder.FullName)\$($PSM1.BaseName)\$($PSM1.BaseName).psd1" -RootModule $PSM1.BaseName

}

#endregion

$Password = ConvertTo-SecureString "<PASSWORD>" -AsPlainText -Force

$AadTenant = Get-AzureStackAadTenant -HostComputer 192.168.200.65 -Password $Password

# Use this command to access the administrative portal

Add-AzureStackAzureRmEnvironment -AadTenant $AadTenant -Name AzureStack

# Use this command to access the tenant portal

Add-AzureStackAzureRmEnvironment -AadTenant $AadTenant -ArmEndpoint https://publicapi.local.azurestack.external -Name AzureStack

When you try to configure Marketplace syndication be aware that you installed Azure Stack in online mode (not ADFS) and have a subscription enabled on your Azure account. When you have installed Azure Stack in a AAD that doesn’t has a subscription, don’t worry. If you have another account that has an Azure subscription enabled and active use that one.

Set-Location C:\Users\AzureStackAdmin\Desktop\AzureStack-Tools-master\Registration
.\RegisterWithAzure.ps1 -azureDirectory markscholman.com -azureSubscriptionId b0d81e1e-8d78-0000-0000-08de7933af4a -azureSubscriptionOwner <SUBADMIN>@markscholman.com

1 2	Set-Location C:\Users\AzureStackAdmin\Desktop\AzureStack-Tools-master\Registration .\RegisterWithAzure.ps1 -azureDirectory markscholman.com -azureSubscriptionId b0d81e1e-8d78-0000-0000-08de7933af4a -azureSubscriptionOwner <SUBADMIN>@markscholman.com

UPDATE: I came around a message on twitter from Marius Sandbu that CSP subscriptions dont have the microsoft.azurestack resource provider registered yet. So if you have a CSP subscription it might not work yet to use marketplace syndication:

@Darmour_MSFT @OrchestratorGuy actually the AzureRMresourceprovider microsoft.azurestack isn’t available in CSP subscription?!

— Marius Sandbu (@msandbu) March 2, 2017

Now the nasty part… It looks like there is a bug, but again, we are running preview guys… Whenever you update a VM (add/remove extension, add disk, etc.) the VM reboots. and sometimes the operation fails. This has to be fixed in a new build, so that’s a good reason to get the Azure Stack downloader running once in a while and opt-in for the development branch 🙂

Also note, that the PaaS (SQL , MySQL & AppService) installation we have from TP2 do not work on TP3. We have to wait for an updated PaaS installer to get it running on TP3

That’s my 2 cents for today, more blogs will follow with the experience of TP3 deployments!

Spread the word. Share this post!

About the author

Mark is consultant at inovativ. Last year he is awarded with the Microsoft Azure MVP award. In his day to day job he is building clouds with Azure Stack, System Center and Powershell.

LinkedIn: https://nl.linkedin.com/in/markscholman
Twitter: @markscholman
Github: https://github.com/markscholman

SamM

Made some changes to your setup script, sorry Im OCD like that:

#Using Azure AAD
cd C:CloudDeploymentSetup
$adminpass = ConvertTo-SecureString “” -AsPlainText -Force
$aadusername = “serviceadmin@.onmicrosoft.com”
$aadpass = ConvertTo-SecureString “” -AsPlainText -Force

$aadcred = New-Object System.Management.Automation.PSCredential ($aadusername, $aadpass)
.InstallAzureStackPOC.ps1 -AdminPassword $adminpass -InfraAzureDirectoryTenantAdminCredential $aadcred -InfraAzureDirectoryTenantName ($aadusername.Split(‘@’)[-1])
- Mark Scholman
  
  Nice! Thanks for sharing your code.
Dadi Gudmundsson

Thanks for sharing you knowledge. Can you enlighten me about the availability of Power BI on Azure Stack? Is it there? Will it be? If it is/will be included, then that would essentially be on-premise Power BI, which many are waiting for. And in that case it would compete with the partial Power BI offering on SQL Server (which was done to make some Power BI capability available on-premise). Any insights would be appreciated.
- Mark Scholman
  
  Sorry, I have no insights on what is coming when to Azure Stack or if it is coming at all to Azure Stack. Please follow the blog and twitter to stay updated on latest news.
James Bond

Mark, can you check your TP3 system and provide information on how much storage space and memory Azure Stack TP3 consumes on a single-node POC configuration? This will hopefully allow me to estimate the amount of remaining server memory and storage space that would be “leftover” for testing guest VMs.
- Mark Scholman
  
  Hi, I used 100-110GB mem and storage used is now around 350 – 400 GB.
  - James Bond
    
    Mark, just to confirm, are your stated numbers what Azure Stack utilized or total system memory and storage? I ask because particularly the 100-110GB of memory seems like a huge amount for Azure to have used up by itself (before guest VMs loaded).
    - Mark Scholman
      
      Hi, that’s correct. Its the amount of memory being consumed by the OS and the Azure Stack VM’s without any guest VM’s deployed. My host has 256GB RAM total so I have some spare 😉
Jonathan Gershater

to deploy TP3, the docs are not clear as to whether two physical servers required (deployment server and POC server) or physical one server? https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-run-powershell-script
Please clarify
- Mark Scholman
  
  Hi, You just need 1 server. You deploy the VHDX onto that server and from that server you start the installation. For more and detailed information please look at http://aka.ms/azurestackdocs
Jonathan Gershater

Deployment fails with storage error
Server is a Cisco UCS C240 with a raid controller
There are five
physical disks, one has Win2016 installed where I launch the install;
the other four are configured as “JBOD” – just a bunch of disks.
The pre-req script sees the disks (and cpu and RAM)
The pre-req script passed.
I started the deploy.
It rebooted
I logged in as the azurestackazurestack admin – then after about an hour the deployment failed with a storage error .

See two screenshots attached

https://uploads.disquscdn.com/images/2863376add9f7b7e2a78fccd4c8a34fe337cbb8bc096316b1bb948b23900ef0f.png https://uploads.disquscdn.com/images/efa029da55ec0165da6e672cdb64fdaa447fee350299eae5e808e3d5113c4819.png
Jonathan Gershater

I got a time-sync error during the deployment see screenshot here
http://bit.ly/2nwS9ej
- Mark Scholman
  
  Please try to rerun the installation. Go back to the C:CloudDeploymentSetup and run the command InstallAzureStackPOC.ps1 -rerun
  Then the installation will continue, looks like a known issue since last week.
  - Jonathan Gershater
    
    thanks that worked!
    https://uploads.disquscdn.com/images/8f84aa94a7f025fc790ac839d9ff7409e964ee3cc1144f85f7661fb7124cbea4.png
Jonathan Gershater

Successfully deployed, at minimal pain, nice job Microsoft!
Question: can I migrate VMs between AzureStack and Azure.com public cloud?
Was looking for a “drag and drop” in the AzureStack portal but don’t see it
Jonathan Gershater

Is there a hybrid capability? Example, can I move VMs seamlessly between azure.com and azurestack on-prem?
Rafael Nunes

Hello Folks,

I’m facing the issue with Azure Stack TP3 during the setup according to the error below. I’ve already try repeat the installation five times removing the VM ‘MAS-SUS01’ from the hyper-v console, failover cluster and from directory C:ClusterStorageVolume1SharesSU1_Infrastructure_11.0.170331.1 an then re-run the installation with following command ‘Invoke-EceAction -RolePath Cloud -ActionType Deployment -Start 40 -Verbose’. However the issue persist.

2017-06-04 08:10:15 Verbose Action: Running action plan ‘Deployment’.
2017-06-04 08:10:15 Verbose Skipping step ‘Phase 0 – Configure physical machine and external networking’ index ‘0’ because it is outside the specified bounds.
2017-06-04 08:10:15 Verbose Step: Skipping step 0 – Phase 0 – Configure physical machine and external networking
2017-06-04 08:10:15 Verbose Step: Running step 40 – Phase 1 – CreateVMs
2017-06-04 08:10:15 Verbose Task: Running action type ‘Deployment-Phase1-CreateVMs’ of role ‘Cloud’.
2017-06-04 08:10:15 Verbose Action: Running action Deployment-Phase1-CreateVMs.
2017-06-04 08:10:15 Verbose Action: Running action plan ‘Deployment-Phase1-CreateVMs’.
2017-06-04 08:10:15 Verbose Step: Running step 40.41 – (CPI) Create guest VMs
2017-06-04 08:10:15 Verbose Task: Running interface ‘Deployment’ of role ‘CloudFabricVirtualMachines’. Attempt #1.
2017-06-04 08:10:15 Verbose Interface: Path to module: C:CloudDeploymentClassesVirtualMachinesVirtualMachines.psm1
2017-06-04 08:10:15 Verbose Interface: Running interface Deployment (ClassesVirtualMachinesVirtualMachines.psm1, VirtualMachines:Deployment)
2017-06-04 08:10:19 Warning The names of some imported commands from the module ‘RoleHelpers’ include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb.
2017-06-04 08:10:20 Warning The names of some imported commands from the module ‘RoleHelpers’ include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb.
2017-06-04 08:10:20 Warning The names of some imported commands from the module ‘RoleHelpers’ include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb.
2017-06-04 08:10:21 Warning The names of some imported commands from the module ‘RoleHelpers’ include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb.
2017-06-04 08:10:21 Warning The names of some imported commands from the module ‘VirtualMachine’ include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb.
2017-06-04 08:10:21 Verbose VMs to create: MAS-DC01, MAS-NC01, MAS-SLB01, MAS-Gwy01, MAS-Con01, MAS-Sql01, MAS-SUS01, MAS-WAS01, MAS-WASP01, MAS-ACS01, MAS-Xrp01, MAS-ERCS01, MAS-ADFS01, MAS-CA01, MAS-BGPNAT01
2017-06-04 08:10:21 Verbose Updating management nodes for HyperConverged deployment.
2017-06-04 08:10:27 Verbose Skipping deployment of the VM named ‘MAS-DC01’. It is accessible via remote Powershell.
2017-06-04 08:10:27 Verbose Skipping deployment of the VM named ‘MAS-NC01’. It is accessible via remote Powershell.
2017-06-04 08:10:27 Verbose Skipping deployment of the VM named ‘MAS-SLB01’. It is accessible via remote Powershell.
2017-06-04 08:19:48 Verbose Skipping deployment of the VM named ‘MAS-Gwy01’. It is accessible via remote Powershell.
2017-06-04 08:23:28 Verbose Skipping deployment of the VM named ‘MAS-Con01’. It is accessible via remote Powershell.
2017-06-04 08:23:46 Verbose Skipping deployment of the VM named ‘MAS-Sql01’. It is accessible via remote Powershell.
2017-06-04 08:23:47 Verbose Skipping deployment of the VM named ‘MAS-SUS01’. It is accessible via remote Powershell.
2017-06-04 08:24:21 Verbose Skipping deployment of the VM named ‘MAS-WAS01’. It is accessible via remote Powershell.
2017-06-04 08:24:21 Verbose Skipping deployment of the VM named ‘MAS-WASP01’. It is accessible via remote Powershell.
2017-06-04 08:24:22 Verbose Skipping deployment of the VM named ‘MAS-ACS01’. It is accessible via remote Powershell.
2017-06-04 08:24:22 Verbose Skipping deployment of the VM named ‘MAS-Xrp01’. It is accessible via remote Powershell.
2017-06-04 08:24:22 Verbose Skipping deployment of the VM named ‘MAS-ERCS01’. It is accessible via remote Powershell.
2017-06-04 08:24:22 Verbose Skipping deployment of the VM named ‘MAS-ADFS01’. It is accessible via remote Powershell.
2017-06-04 08:24:52 Verbose Skipping deployment of the VM named ‘MAS-CA01’. It is accessible via remote Powershell.
2017-06-04 08:25:26 Verbose Skipping deployment of the VM named ‘MAS-BGPNAT01’. It is accessible via remote Powershell.
2017-06-04 08:25:26 Verbose Waiting for the following VMs to be remotely accessible: 192.168.200.224.
2017-06-04 08:25:27 Verbose The VM ‘192.168.200.224’ has successfully started.
2017-06-04 08:25:27 Verbose Waiting for the following VMs to be remotely accessible: MAS-NC01, MAS-SLB01, MAS-Gwy01, MAS-Con01, MAS-Sql01, MAS-SUS01, MAS-WAS01, MAS-WASP01, MAS-ACS01, MAS-Xrp01, MAS-ERCS01, MAS-ADFS01, MAS-CA01, MAS-BGPNAT01.
2017-06-04 08:25:29 Verbose The VM ‘MAS-NC01’ has successfully started.
2017-06-04 08:25:33 Verbose The VM ‘MAS-SLB01’ has successfully started.
2017-06-04 08:26:34 Verbose The VM ‘MAS-Gwy01’ has successfully started.
2017-06-04 08:26:41 Verbose The VM ‘MAS-Con01’ has successfully started.
2017-06-04 08:26:46 Verbose The VM ‘MAS-Sql01’ has successfully started.
2017-06-04 08:26:49 Verbose The VM ‘MAS-SUS01’ has successfully started.
2017-06-04 08:26:52 Verbose The VM ‘MAS-WAS01’ has successfully started.
2017-06-04 08:26:57 Verbose The VM ‘MAS-WASP01’ has successfully started.
2017-06-04 08:27:00 Verbose The VM ‘MAS-ACS01’ has successfully started.
2017-06-04 08:27:03 Verbose The VM ‘MAS-Xrp01’ has successfully started.
2017-06-04 08:27:06 Verbose The VM ‘MAS-ERCS01’ has successfully started.
2017-06-04 08:27:08 Verbose The VM ‘MAS-ADFS01’ has successfully started.
2017-06-04 08:27:40 Verbose The VM ‘MAS-CA01’ has successfully started.
2017-06-04 08:27:48 Verbose The VM ‘MAS-BGPNAT01’ has successfully started.
2017-06-04 08:27:48 Verbose Waiting for the following VMs to complete their DSC configuration: MAS-NC01, MAS-SLB01, MAS-Gwy01, MAS-Con01, MAS-Sql01, MAS-SUS01, MAS-WAS01, MAS-WASP01, MAS-ACS01, MAS-Xrp01, MAS-ERCS01, MAS-ADFS01, MAS-CA01, MAS-BGPNAT01.
2017-06-04 08:27:49 Verbose Operation ” complete.
2017-06-04 08:27:49 Verbose The VM ‘MAS-NC01’ has successfully completed DSC configuration.
2017-06-04 08:27:50 Verbose Operation ” complete.
2017-06-04 08:27:52 Verbose The VM ‘MAS-SLB01’ has successfully completed DSC configuration.
2017-06-04 08:27:53 Verbose Operation ” complete.
2017-06-04 08:28:08 Verbose Operation ” complete.
2017-06-04 08:29:40 Verbose Operation ” complete.
2017-06-04 08:29:51 Verbose Operation ” complete.
2017-06-04 08:29:51 Warning MAS-Gwy01: LCM state is changed by non-DSC operations. If you wish to change the state of LCM, please use Remove-DscConfigurationDocument cmdlet.
2017-06-04 08:30:01 Verbose Operation ” complete.
2017-06-04 08:31:13 Verbose Operation ” complete.
2017-06-04 08:31:13 Verbose The VM ‘MAS-Gwy01’ has successfully completed DSC configuration.
2017-06-04 08:31:14 Verbose Operation ” complete.
2017-06-04 08:31:18 Verbose The VM ‘MAS-Con01’ has successfully completed DSC configuration.
2017-06-04 08:31:19 Verbose Operation ” complete.
2017-06-04 08:31:21 Verbose The VM ‘MAS-Sql01’ has successfully completed DSC configuration.
2017-06-04 08:31:21 Verbose Operation ” complete.
2017-06-04 08:31:34 Verbose Operation ” complete.

2017-06-04 08:46:27 Warning Task: Invocation of interface ‘Deployment’ of role ‘CloudFabricVirtualMachines’ failed:

Function ‘VirtualMachines:Deployment’ in module ‘ClassesVirtualMachinesVirtualMachines.psm1’ raised an exception:

The VM ‘MAS-SUS01’ didn’t complete its DSC configuration in 900 seconds.
Command Arguments
——- ———
Wait-VMDSCComplete {VMNames=MAS-NC01 MAS-SLB01 MAS-Gwy01 MAS-Con01 MAS-Sql01 MAS-SUS01 MAS-WAS01 MAS-WASP01 MAS-ACS01…
Add-GuestVMs {Parameters=CloudEngine.Configurations.EceInterfaceParameters, ErrorAction=Stop, Verbose=True}
{}
{C:CloudDeploymentCloudDeployment.psd1, CloudEngine.Configurations.EceInterfaceParameters}

at Trace-Error, C:CloudDeploymentCommonTracer.psm1: line 44
at Wait-VMDSCComplete, C:CloudDeploymentRolesVirtualMachineVirtualMachine.psm1: line 2188
at Add-GuestVMs, C:CloudDeploymentRolesVirtualMachineVirtualMachine.psm1: line 470
at Deployment, C:CloudDeploymentClassesVirtualMachinesVirtualMachines.psm1: line 39
at , : line 9
2017-06-04 08:46:27 Error Task: Invocation of interface ‘Deployment’ of role ‘CloudFabricVirtualMachines’ failed:

Function ‘VirtualMachines:Deployment’ in module ‘ClassesVirtualMachinesVirtualMachines.psm1’ raised an exception:

The VM ‘MAS-SUS01’ didn’t complete its DSC configuration in 900 seconds.
Command Arguments
——- ———
Wait-VMDSCComplete {VMNames=MAS-NC01 MAS-SLB01 MAS-Gwy01 MAS-Con01 MAS-Sql01 MAS-SUS01 MAS-WAS01 MAS-WASP01 MAS-ACS01…
Add-GuestVMs {Parameters=CloudEngine.Configurations.EceInterfaceParameters, ErrorAction=Stop, Verbose=True}
{}
{C:CloudDeploymentCloudDeployment.psd1, CloudEngine.Configurations.EceInterfaceParameters}

at Trace-Error, C:CloudDeploymentCommonTracer.psm1: line 44
at Wait-VMDSCComplete, C:CloudDeploymentRolesVirtualMachineVirtualMachine.psm1: line 2188
at Add-GuestVMs, C:CloudDeploymentRolesVirtualMachineVirtualMachine.psm1: line 470
at Deployment, C:CloudDeploymentClassesVirtualMachinesVirtualMachines.psm1: line 39
at , : line 9
2017-06-04 08:46:27 Verbose Step: Status of step ‘40.41 – (CPI) Create guest VMs’ is ‘Error’.
2017-06-04 08:46:27 Error Action: Invocation of step 40.41 failed. Stopping invocation of action plan.
2017-06-04 08:46:27 Verbose Action: Status of ‘Deployment-Phase1-CreateVMs’ is ‘Error’.
2017-06-04 08:46:27 Verbose Task: Status of action ‘Deployment-Phase1-CreateVMs’ of role ‘Cloud’ is ‘Error’.
2017-06-04 08:46:27 Verbose Step: Status of step ’40 – Phase 1 – CreateVMs’ is ‘Error’.
2017-06-04 08:46:27 Error Action: Invocation of step 40 failed. Stopping invocation of action plan.

Does anyone has seen this issue ?

Tks,

Rafael Nunes