Azure Stack deployment tweaking #azurestack #azure #deployment

After posting my former blog I got some questions on how to deploy the Stack and where to tweak this.

Well it is easy if you know the PDT kit.

Basically if you extracted the files you will have this folder

image

 

in the MicrosoftAzureStackPOC.vhdx are all the scripts during the deployment this disk will be mounted as source So changing files you will need to mount this disk and edit the files before you do the deployment.

 image

First let us edit the Disk types. To make sure in this example the script will work I do only a find / replace no code added. ( you can )

After mounting the disk we edit the Invoke-AzureStackDeploymentPrecheck.ps1 file

image

in this case I added the “ file backed Virtual” for using local VHD files.

image

Or change the Memory check set this to 32 GB if you want or to 8 <> Remember this is only to pass the validation changing this could fail the installation.

image

Or if one Nic is no option in your config.

image

That’s All

now in the E:\AzureStackInstaller\PoCFabricInstaller folder there is the PoCFabricSettings.xml

 

image

In this PoCFabricSettings.xml are all the settings CPU / Memory / Naming you can all change this here but remember it could fail you installation handle with care.

image

I must say the scripts are great but not a lot of flexibility it takes some testing just to make sure it all worked. I played on a HP blade G9 with SSD’s so running the setup doesn’t take that long but still playing with this kills the day. there is no 10 minute fix troubleshooting takes time.

checkout this forum link to support others.

https://social.msdn.microsoft.com/Forums/azure/en-US/home?forum=AzureStack

 

Happy Stacking

Robert Smit

Twitter: @clustermvp

Cloud and Datacenter MVP ( Expertise:  High Available )

First Errors in Azure Stack Deployment #MAS #AzureStack #Azure #MASCUG Microsoft Azure Stack POC is ready to deploy

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 )

image

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 …

 

image

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.

image

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

image

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 )