I had created a virtual machine scaleset agent pool. After testing I have deleted the agent pool and the virtual machine scaleset. Again I have created a new virtual machine scale set with the same name created before and when adding it to the agent pool I am getting the error "This virtual machine scale set is already in use by pool"
To fix this issue delete manually the tag from the scaleset. You can do this via the Azure Portal. In the scaleset, click the Tags link on the left and delete the tags labeled
Related
I have an existing virtual network in my subscription. Three virtual machines are already assigned to that virtual network since last 2-3 months. But something has got changed in the portal. I am trying to create another virtual machine in the same existing virtual network through the new portal. But I am not getting the available virtual network in my subscription & region while trying to choose the virtual network for the new virtual machine. Unable to add the new virtual machine to the existing virtual network though both are in same subscription & region.
Can I add existing virtual machine to virtual network?
I have seen this link
http://blogs.msdn.com/b/walterm/archive/2013/05/29/moving-a-virtual-machine-from-one-virtual-network-to-another.aspx
and it asks to unattach disk and delete and then create new virtual machine.
Which is impossible in production environment vm.
Any other way to do it?
No, no other option for time being (2014-09-05).
As already suggested, you may try with opening a support ticket, but I doubt that would also help. Before all, Virtual Networks are associated with Affinity Groups. An absolute requirement is that the VHD for the VM uses storage account in the same Affinity Group as the Virtual Network, as well as the Cloud Service that hosts the VM should be also in the same Affinity Group.
To conclude, you have slight chance to solve the issue with support ticket if your new VM and its VHDs are in the same Affinity Group as the Virtual Network. If they are not (either the VM or the VHDs), then your only option is delete and recreate.
In the azure managment portal, I created a Virtual Network, but when i go to create the virtual machines, It didn't give me the screen that let me assign that vm to the virtual network. Why?
How long did you wait between the time the Virtual Network was created and the time when trying to create the VM? I've seen sometimes where it takes a little bit (less than 30 sec.), or refresh the management portal. Also, the VM must be provisioned into a VNET. You can't currently assign an existing VM to a VNET.
First I've captured image of my Azure windows virtual machine see, then I created two new virtual machines(VM1, VM2) from this captured image. Now I want to do load balancing with these 2 virtual machines see. But the "LOAD-BALANCE TRAFFIC ON AN EXISTING ENDPOINT" option is disabled (I added the endpoint in VM1) also my availability set is not showing under "AVAILABILITY SET" option in VM2.
If I do the same process by creating virtual machine from the Gallery, and follow the steps from here, it worked for me.
Is there any power shell command or other way to load balance?
Please help me.
Thanks
Kapil
You need both the virtual machines to be under the same cloud service. Only then you get the option to load balance them. There is no way add existing VMs to the same network. there are operations in the Service management API (usable through powershell) to create a new VM. You can use that to create a fresh VM from your existing image and connect it to the same service as your first VM. Then you'llhave the necessary options enabled for load balancing.
Is it possible to move an already created VM in Azure (different affinity group) to an existing VNET?
Are there commands under the hood to do this (powershell, cmdlets)?
Cheers
Currently you can't join VMs to a virtula network after they are created, you must do this during VM creation time as described here
What you could do is delete your Virtual Machine which will delete the VM configuration but your OS disk will still be saved at Azure Storage. After that you can create a new Virtual Machine using the saved OS disk and during the VM configuration time, you can add it to your virtual network.