You administer of a set of virtual machine (VM) guests hosted in Hyper-V on Windows
Server 2012 R2.
The virtual machines run the following operating systems:
Windows Server 2008 Windows Server 2008 R2 Linux (openSUSE 13.1)
All guests currently are provisioned with one or more network interfaces with static bindings
and VHDX disks. You need to move the VMs to Azure Virtual Machines hosted in an Azure
subscription.
Which three actions should you perform? Each correct answer presents part of the solution.
A.
Install the WALinuxAgent on Linux servers.
B.
Ensure that all servers can acquire an IP by means of Dynamic Host Configuration
Protocol (DHCP).
C.
Upgrade all Windows VMs to Windows Server 2008 R2 or higher.
D.
Sysprep all Windows servers.
E.
Convert the existing virtual disks to the virtual hard disk (VHD) format.
No sysprep?
0
0
no, as the machines will be used again as-is
1
0
is it correct?
1
0
in my opinion should be “A C D”
* A: Azure Linux Agent
This agent is installed on the Linux VM and is responsible to communicate with the Azure Frabric Controller.
* UPLOADING A VIRTUAL MACHINE TO WINDOWS AZURE
Assumption: A Windows Server (2008 R2 or 2012) is created and running as a virtual machine in Hyper-V. (C)
Log onto the Windows Server hosted in Hyper-V you’d like to upload to Windows Azure and open and command prompt (I’m using Windows Server 2012 R2).
Navigate to c:\Windows\System32\Sysprep
Type in sysprep.exe and select enter: (D)
0
0
You only need to do a sysprep if you are planning to use it for an image. Because Server 2012 is using .vhdx and Azure doesn’t yet support .vhdx you need to convert it to vhd. Answer A C E is correct.
1
0
agreed
0
0
Mark is correct, as described: ‘ I you want to use the VHD for creating multiple machines in Azure you need to create an image in Azure. For Azure to be able to start a machine created from an image, you will want to run sysprep on it before you upload it.
If you just want to copy a machine to Azure for use as one Azure VM, you don’t need to sysprep it.’
So i think it must be: A C E.
A: http://azure.microsoft.com/en-us/documentation/articles/virtual-machines-linux-create-upload-vhd-suse/
0
0
Agree, Azure don’t use VHDX, only VHD. we require to convert VHDX to VHD
0
0
The correct answer is B, C and E.
The WA Agent is optional. Sysprep is only needed when creating a new VM image. Static IP addresses are not supported on Azure. Do not confuse static IP addresses with reserved IP addresses. All NICs need to be configured for DHCP before uploading a VHD. VHDX files are not supported. Last correct answer is the minimum requirement of Windows Server 2008 R2.
0
0
Although I agree with you, but I do not find evidence stating that WA Agent is optional. Can anyone second this?
0
0
I could not find an official article that quickly, but the following page mentions it as well: http://windowsitpro.com/azure/windows-azure-iaas-vm-agent
0
0
read this article.
It clearly says that the AzureLinuxAgent is required to properly provision the VM in Azure
https://azure.microsoft.com/en-us/documentation/articles/virtual-machines-linux-create-upload-vhd-generic/
0
0
Arie, DHCP is not required because Hyper-v installs an additional network card. When you are entering the same static ip values as in the on premises enviroment Azure wil pop-up with the message that the IP already is used by another networkcard. Therefore the answer is A,C,E. Otherwise when you swap between Azure and your on premise enviroment you always need to set it to DHCP instead of static.
0
0
You should never set static IP addresses in VMs on Azure. Instead, always use PowerShell to assign a reserved IP address to a VM. Before uploading a VHD file, you should therefore always set the NIC to DHCP.
An example of how this could go wrong is when you have a VM with the static IP address 10.0.0.1, of which you upload the VHD to Azure, where the address space of the virtual network is 192.168.0.0/24 for example.
0
0
No
CDE
http://azure.microsoft.com/en-us/documentation/articles/virtual-machines-create-upload-vhd-windows-server/
0
0
BCE
http://blogs.msdn.com/b/narahari/archive/2013/01/15/windows-azure-virtual-machines-gotcha-s.aspx
A VM must NOT be generalized to use as a disk to only use as a single VM (and not base other VMs from it). Provisioning will fail if you upload a VHD as a disk that has generalized. (Because of this we need to set DHCP)
The VM must be configured for DHCP and not assigned a static IP address. Windows Azure Virtual Machines do not support static IP addresses.
Upload only fixed VHDs (not dynamic, and not VHDX). Windows Azure Virtual Machines do not support dynamic disks or the VHDX format.
Windows Server 2008 is not Supported… Upgrade to Windows Server 2008 R2
0
0
it’s A C E
For C, E, we know there are correct.
For A, we have this reference link.
http://azure.microsoft.com/en-us/documentation/articles/virtual-machines-linux-create-upload-vhd-suse/
Prepare SUSE Linux Enterprise Server 11 SP3
5.Install the Azure Linux Agent from the SLES repository:
# sudo zypper install WALinuxAgent
0
0
A, C, E +1
0
0
A, C, E
0
0
ACE is the answer
From the sample… Azure Linux Agent is required……
So A is correct
5.Install the Azure Linux Agent from the SLES repository:
# sudo zypper install WALinuxAgent
0
0
* For linux the agent is mandatory, so A
* it is not asked to generalize a VM but deploy it, so NOT D
* Windows 2008 is not supported, at least it is not in the list
Get-AzureVMImage | where {$_.OS -eq ‘Windows’ } | select -ExpandProperty “Label”
and I found this:
https://azure.microsoft.com/fr-fr/documentation/articles/virtual-machines-create-upload-vhd-windows-server/
So C is an answer
* VHDX is not supported, so E
I have no idea why we should eliminate B
My answer is A,C,E
0
0
There can be more than one answer, confusing. However the question specifically specifies there are static bindings and VHDX disks. So the best answer is A,D,E. Azure doesn’t work with running servers with fixed IP addresses, and running sysprep /generalize will wipe the network clean, plus sysprep is a required step in Microsoft’s eyes, see https://azure.microsoft.com/en-us/documentation/articles/virtual-machines-create-upload-vhd-windows-server/
Also, there is no need to upgrade the Windows OS, I have successfully uploaded and run a Windows Server 2003 R2 machine in Azure without sysprepping.
0
0
A,B,E: Because if you do a sysprep to a VHD you wipe especific app info and it couldn’t run anymore. The link you provide is to prepare images: “This article shows you how to upload your own generalized VM image as a virtual hard disk (VHD) so you can use it to create virtual machines.” I uploaded and use 2003 at Azure without problem too and without sysprep, but DHCP is needed.
0
0
The mere fact the question makes a nod to VHDX makes E correct in my book.
0
0
A, C & E – D is not there in the new question
0
0
Get-AzureVM -ServiceName “” -Name “” | Set-AzureAvailabilitySet -AvailabilitySetName “” | Update-AzureVM
0
0
mmm the questions says that servers are windows server 2008 R2 – so u dont need to choose the option to upgrade? I make it A,B,E
0
0
“The virtual machines run the following operating systems:
Windows Server 2008 Windows Server 2008 R2 Linux (openSUSE 13.1)” Using happy fun pretty print….
The virtual machines run the following operating systems:
Windows Server 2008<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Windows Server 2008 R2
Linux (openSUSE 13.1)
0
0
It says on https://support.microsoft.com/nl-nl/kb/2721672.
Windows Server 2003 and later versions are supported for deployment in Microsoft Azure. For versions that are earlier than Windows Server 2008 R2, there is no Azure Marketplace support, and customers must provide their own images.
So C cannot be the answer
0
0
going by elimination here, Sysprep and upgrading VM is not required.
you do know that VMs must be DHCP clients in Azure, disk must be VHD and Linux VMs require WALinux agent.
ABE as the answer!
0
0
HI, ABE it’s correct. Because its possible upload custom vhd for legacy OS and its prerequisite that VM’s can receive ip addresses from DHCP. I found this link’s
http://www.ntweekly.com/?p=12921
https://morgansimonsen.com/2014/03/05/will-it-run-how-to-run-your-favorite-legacy-os-in-a-windows-azure-vm/
http://fabriccontroller.net/migrating-your-windows-server-2003-workloads-to-microsoft-azure/
https://blogs.infosupport.com/creating-a-vm-in-azure-based-on-an-uploaded-vhd/
0
0
Can you share a link that says DHCP is a must for VMs in Azure?
0
0
http://documentation.commvault.com/commvault/v11/article?p=products/vs_ms/t_vhypv_azure_convert.htm
0
0
https://docs.microsoft.com/en-us/azure/virtual-machines/windows/prepare-for-upload-vhd-image?toc=%2fazure%2fvirtual-machines%2fwindows%2ftoc.json
0
0
Answes by http://www.taxcup.com it is A: For Linux the WALinuxAgent agent is mandatory.
C: Need to upgrade to Windows Server 2008 R2 or higher.
E: VHDX is not supported, so VHD is needed.
References: https://azure.microsoft.com/fr-fr/documentation/articles/virtual-machinescreate-
upload-vhd-windows-server/
https://azure.microsoft.com/fr-fr/documentation/articles/virtual-machines-create-upload-vhdwindows-
server/
Question No : 76
86
1
0
A,B,E
A – MS best practice.
B – VMWare & MS best practice
C – Windows 2008 32bit is supported!
D – only used to create a new image
E – VHDX is not supported in Azure as yet.
0
0