AzureStack-QuickStart-Templ.../ScaleInOutExistingVmss-managed
Thomas Roettinger 2ba4c65b14 Add Azure Backup Server (#424)
* Preview Release for Office Workloads

* Fix Typos

* Typos

* default PW

* Add SFB Front End Server

* Bug Fixes for AD, SQL, Exchange, Deploy Script

* Addded Skype Edge Servers, Optimized deployment Script

* Major Update to all Templates including addition of ADFS and WAO Templates

* Azure Backup Server
2019-03-15 14:27:10 -07:00
..
.DS_Store Add Azure Backup Server (#424) 2019-03-15 14:27:10 -07:00
README.md Resubmit:Add metadata to existing managed disk templates. (#408) 2019-01-09 11:42:11 -08:00
azuredeploy.json Resubmit:Add metadata to existing managed disk templates. (#408) 2019-01-09 11:42:11 -08:00
azuredeploy.parameters.json Resubmit:Add metadata to existing managed disk templates. (#408) 2019-01-09 11:42:11 -08:00
metadata.json Resubmit:Add metadata to existing managed disk templates. (#408) 2019-01-09 11:42:11 -08:00

README.md

Manually change the number of VMs in an existing VM Scale Set

This template allows you to manually scale in or out the number of VMs in an existing Scale Set. The capacity specified will be the new capacity of the scale set.

The VM size in this template is set to Standard_D1. If you are doing a scale operation on a VM Scale Set with different sized VMs, you will need to change this parameter. I.e. make sure the "sku" property in this template matches the "sku" you originally deployed your Scale Set with. Otherwise, either this deployment will fail (when the VM size belongs to a different family), or VMs will be created with a different size to the existing VMs.

PARAMETER RESTRICTIONS

existingVMSSName must be the name of an EXISTING VM Scale Set

vmSku must be the same size as the VM size of your EXISTING VM Scale Set