Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit 898cc58

Browse files
committedMar 31, 2020
Fixing few issues
1 parent ea03ca5 commit 898cc58

File tree

5 files changed

+13
-9
lines changed

5 files changed

+13
-9
lines changed
 

‎articles/migrate/common-questions-appliance.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -90,6 +90,9 @@ No. There's a one-to-one mapping between an [Azure Migrate appliance](migrate-ap
9090
## Can an Azure Migrate project have multiple appliances?
9191
A project can have multiple appliances attached to it. However, an appliance can only be associated with one project.
9292

93+
## Can the Azure Migrate appliance/Replication appliance connect to the same vCenter?
94+
Yes. You can add both the Azure Migrate appliance (used for assessment and agentless VMware migration), and the replication appliance (used for agent-based migration of VMware VMs) to the same vCenter server.
95+
9396

9497
## How many VMs or servers can I discover with an appliance?
9598

Loading

‎articles/migrate/migrate-appliance.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -75,14 +75,14 @@ The following table summarizes the Azure Migrate appliance requirements for VMwa
7575
The Azure Migrate appliance needs connectivity to the internet.
7676

7777
- When you deploy the appliance, Azure Migrate does a connectivity check to the URLs summarized in the table below.
78-
- If you're using a URL-based proxy to connect to the internet, allow access to these URLs, making sure that the proxy resolves any CNAME records received while looking up the URLs.
78+
- If you're using a URL-based proxy to connect to the internet, you need to alllow access to these URLs, making sure that the proxy resolves any CNAME records received while looking up the URLs.
7979

8080
**URL** | **Details**
8181
--- | --- |
8282
*.portal.azure.com | Navigate to the Azure portal.
8383
*.windows.net <br/> *.msftauth.net <br/> *.msauth.net <br/> *.microsoft.com <br/> *.live.com | Sign in to your Azure subscription.
84-
*.microsoftonline.com <br/> *.microsoftonline-p.com | Create Active Directory apps for the appliance to communicate with Azure Migrate.
85-
management.azure.com | Create Active Directory apps for the appliance to communicate with the Azure Migrate service.
84+
*.microsoftonline.com <br/> *.microsoftonline-p.com | Create Azure Active Directory (AD) apps for the appliance to communicate with Azure Migrate.
85+
management.azure.com | Create Azure AD apps for the appliance to communicate with the Azure Migrate service.
8686
dc.services.visualstudio.com | Upload app logs used for internal monitoring.
8787
*.vault.azure.net | Manage secrets in the Azure Key Vault.
8888
aka.ms/* | Allow access to aka links. Used for Azure Migrate appliance updates.

‎articles/migrate/tutorial-prepare-hyper-v.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Prepare Hyper-V VMs for assessment/migration with Azure Migrate
33
description: Learn how to prepare for assessment/migration of Hyper-V VMs with Azure Migrate.
44
ms.topic: tutorial
5-
ms.date: 03/23/2020
5+
ms.date: 03/31/2020
66
ms.custom: mvc
77
---
88

@@ -90,8 +90,9 @@ You can prepare Hyper-V for VM assessment manually, or using a configuration scr
9090
- Set up PowerShell remoting on each host, so that the Azure Migrate appliance can run PowerShell commands on the host, over a WinRM connection.
9191
- Delegate credentials if VM disks are located on remote SMB shares.
9292
- Set up an account that the appliance will use to discover VMs on Hyper-V hosts.
93-
- Set up Hyper-V Integration Services on each VM you want to discover and assess.
93+
- Set up Hyper-V Integration Services on each VM you want to discover and assess. The default settings when you enable Integration Services are sufficient for Azure Migrate.
9494

95+
![Enable Integration Services](./media/tutorial-prepare-hyper-v/integrated-services.png)
9596

9697

9798
## Prepare with a script
@@ -107,7 +108,7 @@ The script does the following:
107108
- Checks that the host is running a supported version of Hyper-V, and the Hyper-V role.
108109
- Enables the WinRM service, and opens ports 5985 (HTTP) and 5986 (HTTPS) on the host (needed for metadata collection).
109110
- Enables PowerShell remoting on the host.
110-
- Checks that the Hyper-V integration service is enabled on all VMs managed by the host.
111+
- Checks that the Hyper-V Integration Services is enabled on all VMs managed by the host.
111112
- Enables CredSSP on the host if needed.
112113

113114
Run the script as follows:

‎articles/site-recovery/hyper-v-vmm-disaster-recovery.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,10 +4,10 @@ description: Learn how to set up disaster recovery for Hyper-V VMs between your
44
author: rayne-wiselman
55
manager: carmonm
66
ms.service: site-recovery
7-
ms.topic: tutorial
7+
ms.topic: how-to
88
ms.date: 11/14/2019
99
ms.author: raynew
10-
ms.custom: MVC
10+
1111
---
1212
# Set up disaster recovery for Hyper-V VMs to a secondary on-premises site
1313

@@ -39,7 +39,7 @@ To complete this scenario:
3939

4040
- Connects VMs to appropriate target VM networks after failover.
4141
- Optimally places replica VMs on target Hyper-V host servers.
42-
- If you dont configure network mapping, replica VMs wont be connected to a VM network after failover.
42+
- If you don't configure network mapping, replica VMs won't be connected to a VM network after failover.
4343

4444
Prepare VMM as follows:
4545

0 commit comments

Comments
 (0)
Please sign in to comment.