You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/migrate/hydration-process.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -69,19 +69,20 @@ The preparation script executes the following changes based on the OS type of th
69
69
70
70
- On the on-premises server, open the command prompt with elevated privileges and enter **diskpart**.
71
71
72
-
:::image type="content" source="./media/concepts-prepare-vmware-agentless-migration/command-prompt-diskpart.png" alt-text="Image of command prompt diskpart." lightbox="./media/concepts-prepare-vmware-agentless-migration/command-prompt-diskpart.png":::
72
+
:::image type="content" source="./media/concepts-prepare-vmware-agentless-migration/command-prompt-diskpart.png" alt-text="Image of command prompt diskpart." lightbox="./media/concepts-prepare-vmware-agentless-migration/command-prompt-diskpart.png":::
73
73
74
74
- Enter SAN. If the drive letter of the guest operating system isn't maintained, Offline All or Offline Shared is returned.
75
75
76
76
- At the DISKPART prompt, enter SAN Policy=OnlineAll. This setting ensures that disks are brought online, and that you can read and write to both disks.
The preparation script will also set the DHCP service start type as Automatic. This will enable the migrated VM to obtain an IP address and establish connectivity post-migration. Make sure the DHCP service is configured, and the status is running.
:::image type="content" source="./media/concepts-prepare-vmware-agentless-migration/get-service-dhcp.png" alt-text="Screenshot shows set dhcp start type." lightbox="./media/concepts-prepare-vmware-agentless-migration/get-service-dhcp.png":::
85
+
85
86
86
87
To edit the DHCP startup settings manually, run the following example in Windows PowerShell:
87
88
@@ -106,7 +107,7 @@ The preparation script executes the following changes based on the OS type of th
106
107
107
108
To check if the Azure VM Agent was successfully installed, open Task Manager, select the **Details** tab, and look for the process name *WindowsAzureGuestAgent.exe*. The presence of this process indicates that the VM agent is installed. You can also use [PowerShell to detect the VM agent.](/azure/virtual-machines/extensions/agent-windows#powershell)
108
109
109
-

110
+
:::image type="content" source="./media/concepts-prepare-vmware-agentless-migration/installation-azure-vm-agent.png" alt-text="Screenshot shows successful installation of Azure VM agent." lightbox="./media/concepts-prepare-vmware-agentless-migration/installation-azure-vm-agent.png":::
110
111
111
112
After the aforementioned changes are performed, the system partition will be unloaded. The VM is now ready for migration.
112
113
[Learn more about the changes for Windows servers.](/azure/virtual-machines/windows/prepare-for-upload-vhd-image)
0 commit comments