Skip to content

Commit d15d41a

Browse files
author
Cynthia Nottingham
committed
Updates
1 parent 6f54882 commit d15d41a

File tree

2 files changed

+2
-58
lines changed

2 files changed

+2
-58
lines changed

articles/virtual-machines/linux/capture-image.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -28,8 +28,6 @@ To create a copy of your existing Linux VM for backup or debugging, or to upload
2828

2929
You can use the **Azure VM Image Builder (Public Preview)** service to build your custom image, no need to learn any tools, or setup build pipelines, simply providing an image configuration, and the Image Builder will create the Image. For more information, see [Getting Started with Azure VM Image Builder](https://docs.microsoft.com/azure/virtual-machines/linux/image-builder-overview).
3030

31-
Additonally, use **Packer** to create your custom configuration. For more information, see [How to use Packer to create Linux virtual machine images in Azure](build-image-with-packer.md).
32-
3331
You'll need the following items before creating an image:
3432

3533
* An Azure VM created in the Resource Manager deployment model that uses managed disks. If you haven't yet created a Linux VM, you can use the [portal](quick-create-portal.md), the [Azure CLI](quick-create-cli.md), or [Resource Manager templates](create-ssh-secured-vm-from-template.md). Configure the VM as needed. For example, [add data disks](add-disk.md), apply updates, and install applications.

articles/virtual-machines/windows/upload-generalized-managed.md

Lines changed: 2 additions & 56 deletions
Original file line numberDiff line numberDiff line change
@@ -53,68 +53,14 @@ Make sure the server roles running on the machine are supported by Sysprep. For
5353
6. When Sysprep finishes, it shuts down the virtual machine. Do not restart the VM.
5454

5555

56-
## Get a storage account
57-
58-
You'll need a storage account in Azure to store the uploaded VM image. You can either use an existing storage account or create a new one.
59-
60-
If you'll be using the VHD to create a managed disk for a VM, the storage account location must be the same location where you'll be creating the VM.
61-
62-
To show the available storage accounts, enter:
63-
64-
```azurepowershell
65-
Get-AzStorageAccount | Format-Table
66-
```
67-
6856
## Upload the VHD to your storage account
6957

70-
Use the [Add-AzVhd](https://docs.microsoft.com/powershell/module/az.compute/add-azvhd) cmdlet to upload the VHD to a container in your storage account. This example uploads the file *myVHD.vhd* from *C:\Users\Public\Documents\Virtual hard disks\\* to a storage account named *mystorageaccount* in the *myResourceGroup* resource group. The file will be placed into the container named *mycontainer* and the new file name will be *myUploadedVHD.vhd*.
71-
72-
```powershell
73-
$rgName = "myResourceGroup"
74-
$urlOfUploadedImageVhd = "https://mystorageaccount.blob.core.windows.net/mycontainer/myUploadedVHD.vhd"
75-
Add-AzVhd -ResourceGroupName $rgName -Destination $urlOfUploadedImageVhd `
76-
-LocalFilePath "C:\Users\Public\Documents\Virtual hard disks\myVHD.vhd"
77-
```
78-
79-
80-
If successful, you get a response that looks similar to this:
81-
82-
```powershell
83-
MD5 hash is being calculated for the file C:\Users\Public\Documents\Virtual hard disks\myVHD.vhd.
84-
MD5 hash calculation is completed.
85-
Elapsed time for the operation: 00:03:35
86-
Creating new page blob of size 53687091712...
87-
Elapsed time for upload: 01:12:49
88-
89-
LocalFilePath DestinationUri
90-
------------- --------------
91-
C:\Users\Public\Doc... https://mystorageaccount.blob.core.windows.net/mycontainer/myUploadedVHD.vhd
92-
```
93-
94-
Depending on your network connection and the size of your VHD file, this command may take a while to complete.
95-
96-
### Other options for uploading a VHD
97-
98-
You can also upload a VHD to your storage account using one of the following:
99-
100-
- [AzCopy](https://aka.ms/downloadazcopy)
101-
- [Azure Storage Copy Blob API](https://msdn.microsoft.com/library/azure/dd894037.aspx)
102-
- [Azure Storage Explorer Uploading Blobs](https://azurestorageexplorer.codeplex.com/)
103-
- [Storage Import/Export Service REST API Reference](https://msdn.microsoft.com/library/dn529096.aspx)
104-
- We recommend using the Import/Export Service if estimated uploading time is longer than seven days. You can use [DataTransferSpeedCalculator](https://github.com/Azure-Samples/storage-dotnet-import-export-job-management/blob/master/DataTransferSpeedCalculator.html) to estimate the time from data size and transfer unit.
105-
Import/Export can be used to copy to a standard storage account. You'll need to copy from standard storage to premium storage account by using a tool like AzCopy.
106-
107-
> [!IMPORTANT]
108-
> If you are using AzCopy to upload your VHD to Azure, make sure you have set [**/BlobType:page**](https://docs.microsoft.com/azure/storage/common/storage-use-azcopy-blobs#upload-a-file) before running your upload script.
109-
> If the destination is a blob and this option is not specified, by default AzCopy creates a block blob.
110-
>
111-
>
112-
58+
You can now upload a VHD straight into a managed disk. For instructions, see [Upload a VHD to Azure using Azure PowerShell] (disks-upload-vhd-to-managed-disk-powershell.md).
11359

11460

11561
## Create a managed image from the uploaded VHD
11662

117-
Create a managed image from your generalized OS VHD. Replace the following values with your own information.
63+
Create a managed image from your generalized OS managed disk. Replace the following values with your own information.
11864

11965

12066
First, set some parameters:

0 commit comments

Comments
 (0)