История

Shriram Natarajan f3721f6b3e Update azuredeploy.json		2017-10-24 15:24:00 -07:00
..
scripts	Changing name of templates to match the pattern 101/201/301-PrimaryResourceName-Linux/Windows-WhatTheTemplateDoes (#225 )	2017-05-09 11:05:08 -07:00
README.md	Changing name of templates to match the pattern 101/201/301-PrimaryResourceName-Linux/Windows-WhatTheTemplateDoes (#225 )	2017-05-09 11:05:08 -07:00
azuredeploy.json	Update azuredeploy.json	2017-10-24 15:24:00 -07:00
azuredeploy.parameters.json	Changing name of templates to match the pattern 101/201/301-PrimaryResourceName-Linux/Windows-WhatTheTemplateDoes (#225 )	2017-05-09 11:05:08 -07:00
metadata.json	Changing name of templates to match the pattern 101/201/301-PrimaryResourceName-Linux/Windows-WhatTheTemplateDoes (#225 )	2017-05-09 11:05:08 -07:00

README.md

Deploy a VM Scale Set of Windows VMs with a custom script extension

This template allows you to deploy a VM Scale Set of Windows VMs with a custom script run on each VM. It uses the latest patched version of several Windows versions. To connect from the load balancer to a VM in the scale set, you would go to the AzureStack Portal, find the load balancer of your scale set, examine the NAT rules, then connect using the NAT rule you want. For example, if there is a NAT rule on port 50000, you could RDP on port 50000 of the public IP to connect to that VM. Similarly if something is listening on port 80 we can connect to it using port 80:

PARAMETER RESTRICTIONS

vmssName must be 3-10 characters in length. It should also be globally unique across all of AzureStack. If it isn't globally unique, it is possible that this template will still deploy properly, but we don't recommend relying on this pseudo-probabilistic behavior. instanceCount must be 20 or less. VM Scale Set supports upto 100 VMs and one should add more storage accounts to support this number.