All notes


Change VM to another Virtual Network

Microsoft Technet.

Identify the disk used by a Virtual Machine

In the Dashboard pane for the virtual machine you want to move, scroll down to the disk section and note the disk/disks that your VM has attached to itself. In my case the disk attached to the vm-test-01 virtual machine. is “VM-Test-01-VM-Test-01-0-201406140351230909”.

Delete the existing Virtual Machine.

While the virtual machine is still selected in the portal, select Delete in the action bar at the bottom of the screen. Ensure that you select “Keep the attached disks”.

Once Deleted, switch your focus in the portal to the Virtual Machines section and the Disk Pane and keep refreshing the screen until the field “Attached to” goes blank.

Create the new Virtual Machine.

Once the disk reports that it’s not attached to anything, it will also show up the “My Disks” portion of the gallery. Let’s create a new VM using that disk by selecting in the Action bar. New, Compute, Virtual Machine, From Gallery.

In the Gallery, select “My Disks” and select the disk that corresponds to the disk that was originally attached to the virtual machine we deleted. In my case “VM-Test-01-VM-Test-01-0-201406140351230909”.

Fill out the wizard with the name, tier, size … until you get to the Cloud Service. Once you get there you must create a new Cloud Service and select the new virtual Network and subnet you want has the new target for your new VM. You Need a new cloud service because the Cloud Service is a boundary for a variety of settings such as: Public IP Address space Public DNS Name Internet Firewall Load Balancing so switching the network will of course change the IP address space. Once you’ve selected the new Cloud Service, pick the Virtual Network and the subnet you want. And complete the wizard to create the new VM.

Connect two VMs

MSDN social. In general, Azure VMs can automatically communicate using a private network channel with other virtual machines in the same cloud service or virtual network. In addition, you can use a VNet to VNet connection to connect the two virtual networks.

If the two VMs are in the same cloud service, it is recommended to enable the File and Printer Sharing (Echo Request – ICMPv4-In) in the inbound rules in Windows firewall on your VMs, then to see if it is able to ping between them.

Upload files to your Azure VM

  1. Launch your RDP client (mstsc.exe in Windows) and expand the details button to reveal the remote computer access to local resources checkboxes.
  2. Ensure that the Clipboard option is checked and connect and log into your Azure VM.
  3. Copy the files, folders or ISO from on your local host.
  4. Paste into your Azure VM.

wcfNote: Drag and Drop doesn't work. You have to Ctrl-c and Ctrl-v.