Playing with the AzureStack deployment is no picknick there is a Pre-check but you must have the perfect machine to deploy the Azure Stack Bits. So I tweaked the scripts a bit. this is the logical architecture of the Azure Stack POC and its components. all running on a single Hyper-v host.
But even then something can go wrong. As shown below some errors are highlighted.
Check disks failed. At least 3 disks of the same bus type (RAID/SAS/SATA) and with CanPool attribute equals true are
required. ( I added some other Storage also )
Cannot bind argument to parameter ‘PackagePath’ because it is an empty string ( used a variable setting before running the script )
Welcome to the Microsoft Azure Stack POC Deployment!
There are several prerequisites checks to verify that your machine meets all the minimum requirements for deploying Microsoft A
zure Stack POC.
All of the prerequisite checks passed.
Please enter the password for the built-in administrator. The password must meet the Azure Active Directory password complexity
requirements.
Password: **********
Confirm password: **********
Setup system admin account
Please sign in to your Azure account in the Microsoft Azure sign in window.
Press any key to continue …
But after Concurring All the Pre-Requirements you are ready to go Or not ?
During the Deployment I had this error : Method "NewTriggerByStartup" not found
This seams an updated Powershell module is in place and I have a bug in my build. After some digging in the Powershell modules I managed to fix this.
Microsoft Azure Stack POC is ready to deploy. Continue?
[Y] Yes [N] No [S] Suspend [?] Help (default is "Y"): y
New-ScheduledTaskTrigger : Method "NewTriggerByStartup" not found
At F:\AzureStackInstaller\PoCDeployment\AzureStackDeploymentScheduledTask.psm1:27 char:16
+ $trigger = New-ScheduledTaskTrigger -AtStartup
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (PS_ScheduledTask:Root/Microsoft/…S_ScheduledTask) [New-ScheduledTaskTrigger]
, CimException
+ FullyQualifiedErrorId : HRESULT 0x80041002,New-ScheduledTaskTrigger
The real fix is this mofcomp C:\Windows\System32\wbem\SchedProv.mof
and after Some digging I find already a uservoice post on this issue. So vote for this
I must say the scripts are awesome lots of handy stuff in there. I did the Next Next Finish setup to see what I could expect and how to Build this in a not default environment. SO no single server.
That’s All For now.
Greetings,
Robert Smit
Twitter: @clustermvp
Cloud and Datacenter MVP ( Expertise: High Available )
Share this:
Robert Smit MVP Blog 
This is interesting but you didn’t provide any information on host to address the first problem (canpool=false). I am seeing that problem now and the CannotPoolReason is “Insufficient Capacity”. But the disks (all SATA, 2 being 3T and one 4T) have lots of space available. According to the docs I have seen, the drives need to have a minimum of 5G available ans these drives all have a couple of terabyte available. So, what is the work around?
Thanks
Bert
Hi Bert,
the canpool options is only there is you can share the disk like ISCSI or in storage spaces direct and true you need at least 5Gb per disk but in case of Azure Stack the volume needs to be 200 GB this will be a Storage pool disk. So you need sharable disk In this case I used ISCSI disk and for the local disks I used the Storage spaces direct but this option needs more servers than one 😉
For more info about canpool:
https://robertsmit.wordpress.com/2014/01/14/virtual-hard-disk-sharing-shared-vhdx-storage-pool-usage-in-failover-clustering-windows-server-2012-r2/
hello Robert Can you send me the steps to resolve this error
Check disk failed. at leasst 3 disks of the same bus type (RAID /SAS/SATA) and with canpool attribute equals true are required
I really did not got how to resolve and i am stuck on this from last 2 weeks.
Please help.
Sure I’ll write a blog post on this next week