azure-vm-scale-set

问题 I'm trying to change my VMSS from: "imageReference": { "publisher": "MicrosoftWindowsServer", "offer": "WindowsServer", "sku": "2016-Datacenter-with-Containers", "version": "latest" } To: "imageReference": { "publisher": "MicrosoftWindowsServer", "offer": "WindowsServerSemiAnnual", "sku": "Datacenter-Core-1803-with-Containers-smalldisk", "version": "latest" } The first thing I tried was: Update-AzureRmVmss -ResourceGroupName "DevServiceFabric" -VMScaleSetName "HTTP" -ImageReferenceSku

问题 I'm trying to change my VMSS from: "imageReference": { "publisher": "MicrosoftWindowsServer", "offer": "WindowsServer", "sku": "2016-Datacenter-with-Containers", "version": "latest" } To: "imageReference": { "publisher": "MicrosoftWindowsServer", "offer": "WindowsServerSemiAnnual", "sku": "Datacenter-Core-1803-with-Containers-smalldisk", "version": "latest" } The first thing I tried was: Update-AzureRmVmss -ResourceGroupName "DevServiceFabric" -VMScaleSetName "HTTP" -ImageReferenceSku

问题 Today, I found I cannot remote into my Azure VM scale set instances (win 2016 Nano Server). I then tried restart the VM scale set instance using powershell but got following like error: Restart-AzureRmVmss : Long running operation failed with status 'Failed'. Additional Info:'VM 'master-vmss_0' has not reported status for VM agent or extensions. Please verify the VM has a running VM agent, and can establish outbound connections to Azure storage.' ErrorCode: VMAgentStatusCommunicationError

问题 As I understand, Virtual Machine Scale Sets are a collection of Virtual Machines. Each one can be destroyed and reconstituted at the whim of the configuration. The VM's are recreated from a certain image. Is this understanding is correct ? If this is correct, how do you patch a scaleset ? Consider a scaleset created using a Windows 2016. 50 patches are made available via the update service since the base image was created. During a heavy load, 3 new VMs are created by the scaleset. The new

问题 For networking I'm using new Standard SKU (Load balancer, Public IP addresses, etc.). By default everything is disabled for Public IP Address Standard SKU. I added the following and got TCP outbound connectivity: 1. NSG - enabled all outbound traffic 2. Load balancer rule - rule for Tcp & disabled SNAT 3. Outbound rule - for Tcp Now when I remote to VMSS VM instance, I can open "google.com". But "ping google.com" keeps timing out. I wonder what I should configure to enable ping/tracert to

问题 I'm receiving the following error when trying to manually increase the number of instances above 10 on an Azure Scale set. Failed to update autoscale configuration for 'XXXX'.{ "error": { "details": [], "code": "InboundNatPoolFrontendPortRangeSmallerThanRequestedPorts", "message": "The frontend port range for the inboundNATpool /subscriptions/xxxx/resourceGroups/xxxx/providers/Microsoft.Network/loadBalancers/LB-xxx/inboundNatPools/DebuggerListenerNatPool-4vhwwa8stp is smaller than the

问题 I've deployed a virtual machine scale set (VMSS) to Azure as part of a Service Fabric cluster. When I try to redeploy the template, slightly enhanced to update the VMSS with an additional secret, I get the following error. I've verified that the parameters I'm using are all correct. "type": "Microsoft.Compute/virtualMachineScaleSets", // ... "osProfile": { // ... "secrets": [ { "sourceVault": { "id": "[parameters('sourceVaultValue')]" }, "vaultCertificates": [ { "certificateStore": "

问题 Using PS to create a extension that needs to do the following for right now. 1: Get zip 2: Unzip and copy into directory in C:\Scripts Here is the PS to install the extension (this does infact create the extension in extensions under the scale set) $dscConfig = @{ "wmfVersion" = "latest"; "configuration" = @{ "url" = "https://foo.blob.core.windows.net/dsc.zip"; "script" = "configure.ps1"; "function" = "AzureDscDemo"; }; } $vmss = Get-AzVmss ` -ResourceGroupName "FooVmssResource" `

问题 I am trying to deploy Virtual Machine Scale Set to Azure using ARM Template and Desired State Configuration (DSC). I have created DSC configuraiton and validated it on a separate VM that it is working. In ARM template I have following definition of DSC extension: { "name": "Microsoft.Powershell.DSC", "properties": { "publisher": "Microsoft.Powershell", "type": "DSC", "typeHandlerVersion": "2.9", "autoUpgradeMinorVersion": true, "settings": { "configuration": { "url": "publicstoragebloburi/DSC