I feel like ive brought this up before so i appologize if this is a duplicate (I did a quick look and didnt see it)
When onboarding a new client and setting up FSLogix file share it joins it to AD, for this it creates a VM. There is an error that can occur if the size that Nerdio automatically selects is unavailable that it just fails.
I assume this can happen at any of the automation points that nerdio spins up a temp VM.
Logs give you the error
/providers/Microsoft.Compute/virtualMachines/vm-c1eac6' is currently not available in location 'westus3' zones '' for subscription '<subscription>'. Please try another size or deploy to a different location or zones.
Can we get failover sizes for the automation or allow selection if it fails as it just halts automation and onboarding.
Feature Request / Bug fix - VM size selection during client creation / automated tasks
Hey, Tomas.
I believe Nerdio already has this feature (Azure Capacity Extender). We've found that the Intelligent Azure Capacity Extender feature works best for our customers.
The only "Negative" is if you have reserved instances, you could run into billing issues if a non-reserved SKU is in use.
However, I think Nerdio has (or is?) released a monitor to compare your current AVD state against the Auto-Scale settings.
I'm hoping we'll be able to use that same monitor for the SKU type.
DStephenson
This would make sense for an existing environment for AVD pools, But my understanding is that it does not effect some of the automation tasks such as joining fslogix to AD.
As well as the issue that im running into this error on creating a client which means i can not configure this setting at all...
DStephenson is correct, Azure Capacity Extender (ACE) is there for this purpose. If you look at the advanced settings for joining Azure Files to AD on the customer level, we've included Intelligent ACE to resolve capacity issues for temp VMs as well.
Tomas However, ACE is not enabled yet during the Add Account wizard which means this wouldn't apply to your flow. As a workaround for now, I would suggest to skip joining Azure Files to AD from the wizard in order to proceed for this region, you can do that by specifying a dummy UNC path. After finishing the wizard, go to the customer level to create AD joined Azure Files storage using the ACE.
We will make Intelligent ACE the default setting during the Add Account wizard to prevent this issue from happening. Expect this soon.
Gido Veekens
Perfect thank you.
I had ended up just creating and joining my own azure file share then proceeding with creation.
I will make note of the dummy unc path moving forward as that seems a lot easier.
Please sign in to leave a comment.
Comments (4 comments)