Merge pull request #92579 from Rajeswari-Mamilla/master

Support matrix updates

Author: ShannonLeavitt

articles/site-recovery/vmware-azure-configuration-server-requirements.md

@@ -26,57 +26,7 @@ For disaster recovery of VMware VMs to Azure, you deploy the configuration serve
 - We strongly recommend that you set up the configuration server using the OVA template. However, if you're setting up disaster recovery for VMware VMs and can't use the OVA template, you can deploy the configuration server using [these instructions provided](physical-azure-set-up-source.md).
 - If you're deploying the configuration server for disaster recovery of on-premises physical machines to Azure, follow the instructions in [this article](physical-azure-set-up-source.md). 
 
-
-## Hardware requirements
-
-**Component** | **Requirement** 
---- | ---
-CPU cores | 8 
-RAM | 16 GB
-Number of disks | 3, including the OS disk, process server cache disk, and retention drive for failback 
-Free disk space (process server cache) | 600 GB
-Free disk space (retention disk) | 600 GB
-
-## Software requirements
-
-**Component** | **Requirement** 
---- | ---
-Operating system | Windows Server 2012 R2 <br> Windows Server 2016
-Operating system locale | English (en-us)
-Windows Server roles | Don't enable these roles: <br> - Active Directory Domain Services <br>- Internet Information Services <br> - Hyper-V 
-Group policies | Don't enable these group policies: <br> - Prevent access to the command prompt. <br> - Prevent access to registry editing tools. <br> - Trust logic for file attachments. <br> - Turn on Script Execution. <br> [Learn more](https://technet.microsoft.com/library/gg176671(v=ws.10).aspx)
-IIS | - No preexisting default website <br> - No preexisting website/application listening on port 443 <br>- Enable  [anonymous authentication](https://technet.microsoft.com/library/cc731244(v=ws.10).aspx) <br> - Enable [FastCGI](https://technet.microsoft.com/library/cc753077(v=ws.10).aspx) setting 
-
-## Network requirements
-
-**Component** | **Requirement** 
---- | --- 
-IP address type | Static 
-Internet access | The server needs access to these URLs (directly or via proxy): <br> - \*.accesscontrol.windows.net<br> - \*.backup.windowsazure.com <br>- \*.store.core.windows.net<br> - \*.blob.core.windows.net<br> - \*.hypervrecoverymanager.windowsazure.com  <br> - https:\//management.azure.com <br> - *.services.visualstudio.com <br> - time.nist.gov <br> - time.windows.com <br> OVF also needs access to the following URLs: <br> - https:\//login.microsoftonline.com <br> - https:\//secure.aadcdn.microsoftonline-p.com <br> - https:\//login.live.com  <br> - https:\//auth.gfx.ms <br> - https:\//graph.windows.net <br> - https:\//login.windows.net <br> - https:\//www.live.com <br> - https:\//www.microsoft.com <br> - https:\//dev.mysql.com/get/Downloads/MySQLInstaller/mysql-installer-community-5.7.20.0.msi 
-Ports | 443 (Control channel orchestration)<br>9443 (Data transport) 
-NIC type | VMXNET3 (if the Configuration Server is a VMware VM)
-
-## Required software
-
-**Component** | **Requirement** 
---- | ---
-VMware vSphere PowerCLI | [PowerCLI version 6.0](https://my.vmware.com/web/vmware/details?productId=491&downloadGroup=PCLI600R1) should be installed if the Configuration Server is running on a VMware VM.
-MYSQL | MySQL should be installed. You can install manually, or Site Recovery can install it.
-
-## Sizing and capacity requirements
-
-The following table summarizes capacity requirements for the configuration server. If you're replicating multiple VMware VMs, you should review the [capacity planning considerations](site-recovery-plan-capacity-vmware.md), and run the [Azure Site Recovery Deployment Planner](site-recovery-deployment-planner.md) tool for VMWare replication.read 
-
-**Component** | **Requirement** 
---- | ---
-
-| **CPU** | **Memory** | **Cache disk** | **Data change rate** | **Replicated machines** |
-| --- | --- | --- | --- | --- |
-| 8 vCPUs<br/><br/> 2 sockets * 4 cores \@ 2.5 GHz | 16 GB | 300 GB | 500 GB or less | Les than 100 machines |
-| 12 vCPUs<br/><br/> 2 socks  * 6 cores \@ 2.5 GHz | 18 GB | 600 GB | 500 GB-1 TB | 100 to 150 machines |
-| 16 vCPUs<br/><br/> 2 socks  * 8 cores \@ 2.5 GHz | 32 GB | 1 TB | 1-2 TB | 150-200 machines | 
-
-
+[!INCLUDE [site-recovery-configuration-server-requirements](../../includes/site-recovery-configuration-and-scaleout-process-server-requirements.md)]
 
 ## Next steps
 Set up disaster recovery of [VMware VMs](vmware-azure-tutorial.md) to Azure.

articles/site-recovery/vmware-azure-deploy-configuration-server.md

@@ -23,7 +23,7 @@ Configuration server must be set up as a highly available VMware VM with certain
 
 ## Prerequisites
 
-Minimum hardware requirements for a configuration server are summarized in the following table.
+Minimum hardware requirements for a configuration server are summarized in the following sections.
 
 [!INCLUDE [site-recovery-configuration-server-requirements](../../includes/site-recovery-configuration-and-scaleout-process-server-requirements.md)]
 
@@ -32,32 +32,20 @@ Minimum hardware requirements for a configuration server are summarized in the f
 You require a user with **one of the following** permissions set in AAD (Azure Active Directory) to register configuration server with Azure Site Recovery services.
 
 1. User should have “Application developer” role to create application.
-   1. To verify, Sign in to Azure portal</br>
-   1. Navigate to Azure Active Directory > Roles and administrators</br>
-   1. Verify if "Application developer" role is assigned to the user. If not, use a user with this permission or reach out to [administrator to enable the permission](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-users-assign-role-azure-portal#assign-roles).
+    - To verify, Sign in to Azure portal</br>
+    - Navigate to Azure Active Directory > Roles and administrators</br>
+    - Verify if "Application developer" role is assigned to the user. If not, use a user with this permission or reach out to [administrator to enable the permission](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-users-assign-role-azure-portal#assign-roles).
 
-1. If the "Application developer" role cannot be assigned, ensure that "User can register application” flag is set as true for user to create identity. To enable above permissions,
-   1. Sign in to Azure portal
-   1. Navigate to Azure Active Directory > User settings
-   1. Under **App registrations", "Users can register applications" should be chosen as "Yes".
+2. If the "Application developer" role cannot be assigned, ensure that "User can register application” flag is set as true for user to create identity. To enable above permissions,
+    - Sign in to Azure portal
+    - Navigate to Azure Active Directory > User settings
+    - Under **App registrations", "Users can register applications" should be chosen as "Yes".
 
       ![AAD_application_permission](media/vmware-azure-deploy-configuration-server/AAD_application_permission.png)
 
 > [!NOTE]
 > Active Directory Federation Services(ADFS) is **not supported**. Please use an account managed through [Azure Active Directory](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-whatis).
 
-## Capacity planning
-
-The sizing requirements for the configuration server depend on the potential data change rate. Use this table as a guide.
-
-| **CPU** | **Memory** | **Cache disk size** | **Data change rate** | **Protected machines** |
-| --- | --- | --- | --- | --- |
-| 8 vCPUs (2 sockets * 4 cores \@ 2.5 GHz) |16 GB |300 GB |500 GB or less |Replicate fewer than 100 machines. |
-| 12 vCPUs (2 sockets * 6 cores \@ 2.5 GHz) |18 GB |600 GB |500 GB to 1 TB |Replicate 100-150 machines. |
-| 16 vCPUs (2 sockets * 8 cores \@ 2.5 GHz) |32 GB |1 TB |1 TB to 2 TB |Replicate 150-200 machines. |
-
-If you're replicating more than one VMware VM, read [capacity planning considerations](site-recovery-plan-capacity-vmware.md). Run the [Deployment planner tool](site-recovery-deployment-planner.md) for VMWare replication.
-
 ## Download the template
 
 1. In the vault, go to **Prepare Infrastructure** > **Source**.
@@ -144,17 +132,17 @@ If you want to add an additional NIC to the configuration server, add it before
 
 ## Upgrade the configuration server
 
-To upgrade the configuration server to the latest version, follow these [steps](vmware-azure-manage-configuration-server.md#upgrade-the-configuration-server). For detailed instructions on how to upgrade all Site Recovery components, click [here](service-updates-how-to.md).
+To upgrade the configuration server to the latest version, follow these [steps](vmware-azure-manage-configuration-server.md#upgrade-the-configuration-server). For detailed instructions on how to upgrade all Site Recovery components, visit [service update management](service-updates-how-to.md).
 
 ## Manage the configuration server
 
 To avoid interruptions in ongoing replication, ensure that IP address of the configuration server does not change after the configuration server has been registered to a vault. You can learn more about common configuration server management tasks [here](vmware-azure-manage-configuration-server.md).
 
 ## FAQ
 
-1. How long is the Licence provided on configuration server deployed through OVF is valid? What happens if I do not reactivate the License?
+1. How long is the License provided on configuration server deployed through OVF is valid? What happens if I do not reactivate the License?
 
-    The license provided with OVA template is an evaluation license valid for 180 days. Before expiry, you need to activate the license. Else, this can result in frequent shutdown of configuration server and thus cause hinderance to replication activities.
+    The license provided with OVA template is an evaluation license valid for 180 days. Before expiry, you need to activate the license. Else, it can result in frequent shutdown of configuration server and thus cause hindrance to replication activities. For additional details, refer to article on [manage configuration server license](vmware-azure-manage-configuration-server.md#update-windows-license).
 
 2. Can I use the VM, where the configuration server is installed, for different purposes?
 

articles/site-recovery/vmware-azure-manage-configuration-server.md

@@ -16,12 +16,16 @@ You set up an on-premises configuration server when you use [Azure Site Recovery
 
 [!INCLUDE [updated-for-az](../../includes/updated-for-az.md)]
 
+## Update Windows license
+
+The license provided with the OVF template is an evaluation license valid for 180 days. For uninterrupted usage, you must activate Windows with a procured license. License update can be done either through a standalone key or KMS standard key. Guidance is available at [DISM Windows command line for running OS](https://docs.microsoft.com/windows-hardware/manufacture/desktop/dism-windows-edition-servicing-command-line-options). To obtain keys, refer to [KMS client set up](https://docs.microsoft.com/windows-server/get-started/kmsclientkeys).
+
 ## Access configuration server
 
 You can access the configuration server as follows:
 
 * Sign in to the VM on which it's deployed, and Start **Azure Site Recovery Configuration Manager** from the desktop shortcut.
-* Alternatively, you can access the configuration server remotely from https://*ConfigurationServerName*/:44315/ . Sign in with administrator credentials.
+* Alternatively, you can access the configuration server remotely from https://*ConfigurationServerName*/:44315/. Sign in with administrator credentials.
 
 ## Modify VMware server settings
 
@@ -53,7 +57,7 @@ Modify the credentials used to automatically install Mobility Service on the VMw
 
 You can also modify credentials through CSPSConfigtool.exe.
 
-1. Login to the configuration server and launch CSPSConfigtool.exe
+1. Log in to the configuration server and launch CSPSConfigtool.exe
 2. Choose the account you wish to modify and click **Edit**
 3. Enter the new credentials and click **Ok**.
 
@@ -68,7 +72,7 @@ If you missed adding credentials during OVF deployment of configuration server,
 
 You can also add credentials through CSPSConfigtool.exe.
 
-1. Login to the configuration server and launch CSPSConfigtool.exe
+1. Log in to the configuration server and launch CSPSConfigtool.exe
 2. Click **Add**, enter the new credentials and click **Ok**.
 
 ## Modify proxy settings
@@ -288,10 +292,6 @@ For configuration server deployments before May 2016, certificate expiry was set
 3. On the blade with details of chosen configuration server, click **More** > **Refresh Server**.
 4. Monitor the progress of the job under **Recovery Services Vault** > **Monitoring** > **Site Recovery jobs**.
 
-## Update Windows license
-
-The license provided with the OVF template is an evaluation license valid for 180 days. For uninterrupted usage, you must activate Windows with a procured license.
-
 ## Failback requirements
 
 During reprotect and failback, the on-premises configuration server must be running and in a connected state. For successful failback, the virtual machine being failed back must exist in the configuration server database.

articles/site-recovery/vmware-azure-set-up-source.md

@@ -13,7 +13,7 @@ ms.author: ramamill
 
 # Set up the source environment for VMware to Azure replication
 
-This article describes how to set up your source on-premises environment, to replicate VMware VMs to Azure. It includes steps for selecting your replication scenario, setting up an on-premises machine as the Site Recovery configuration server, and automatically discovering on-premises VMs. 
+This article describes how to set up your source on-premises environment, to replicate VMware VMs to Azure. Article includes steps for selecting your replication scenario, setting up an on-premises machine as the Site Recovery configuration server, and automatically discovering on-premises VMs. 
 
 ## Prerequisites
 
@@ -36,7 +36,7 @@ The article assumes that you have already:
 You can set up the configuration server as an on-premises VMware VM through an Open Virtualization Application (OVA) template. [Learn more](concepts-vmware-to-azure-architecture.md) about the components that will be installed on the VMware VM.
 
 1. Learn about the [prerequisites](vmware-azure-deploy-configuration-server.md#prerequisites) for configuration server deployment.
-2. [Check capacity numbers](vmware-azure-deploy-configuration-server.md#capacity-planning) for deployment.
+2. [Check capacity numbers](vmware-azure-deploy-configuration-server.md#sizing-and-capacity-requirements) for deployment.
 3. [Download](vmware-azure-deploy-configuration-server.md#download-the-template) and [import](vmware-azure-deploy-configuration-server.md#import-the-template-in-vmware) the OVA template to set up an on-premises VMware VM that runs the configuration server. The license provided with the template is an evaluation license and is valid for 180 days. Post this period, customer needs to activate the windows with a procured license.
 4. Turn on the VMware VM, and [register it](vmware-azure-deploy-configuration-server.md#register-the-configuration-server-with-azure-site-recovery-services) in the Recovery Services vault.
 
@@ -65,7 +65,7 @@ Exclude following folders from Antivirus software for smooth replication and to
   - C:\ProgramData\ASRSetupLogs
   - C:\ProgramData\LogUploadServiceLogs
   - C:\inetpub
-  - ASR server installation directory. For example: E:\Program Files (x86)\Microsoft Azure Site Recovery
+  - Site Recovery server installation directory. For example: E:\Program Files (x86)\Microsoft Azure Site Recovery
 
 ### If Antivirus Software is active on scale-out Process server/Master Target
 
@@ -77,7 +77,7 @@ Exclude following folders from Antivirus software
 4. C:\ProgramData\ASRSetupLogs
 5. C:\ProgramData\LogUploadServiceLogs
 6. C:\ProgramData\Microsoft Azure Site Recovery
-7. ASR load balanced process server installation directory, Example: C:\Program Files (x86)\Microsoft Azure Site Recovery
+7. Azure Site Recovery load balanced process server installation directory, Example: C:\Program Files (x86)\Microsoft Azure Site Recovery
 
 
 ## Next steps