Merge pull request #220718 from Sharmistha-Rai/main

Linux root user callout

Author: prmerger-automator[bot]

articles/site-recovery/physical-azure-disaster-recovery.md

@@ -76,13 +76,13 @@ Set up an [Azure storage account](../storage/common/storage-account-create.md).
 
 ### Prepare an account for Mobility service installation
 
-The Mobility service must be installed on each server you want to replicate. Site Recovery installs this service automatically when you enable replication for the server. To install automatically, you need to prepare an account that Site Recovery will use to access the server.
+The Mobility service must be installed on each server you want to replicate. Site Recovery installs this service automatically when you enable replication for the server. To install automatically, you need to use the **root**/**admin** account that Site Recovery will utilize to access the server.
 
-- You can use a domain or local account
+- You can use a domain or local account for Windows VMs
 - For Windows VMs, if you're not using a domain account, disable Remote User Access control on the local machine. To do this, in the register under **HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System**, add the DWORD entry **LocalAccountTokenFilterPolicy**, with a value of 1.
 - To add the registry entry to disable the setting from a CLI, type:
   `REG ADD HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v LocalAccountTokenFilterPolicy /t REG_DWORD /d 1.`
-- For Linux, the account should be root on the source Linux server.
+- For Linux, the account should be **root** on the source Linux server.
 
 
 ## Create a vault

articles/site-recovery/vmware-azure-install-mobility-service.md

@@ -3,7 +3,6 @@ title: Prepare source machines to install the Mobility Service through push inst
 description: Learn how to prepare your server to install Mobility agent through push installation for disaster recovery of VMware VMs and physical servers to Azure using the  Azure Site Recovery service.
 services: site-recovery
 author: ankitaduttaMSFT
-manager: gaggupta
 ms.service: site-recovery
 ms.topic: conceptual
 ms.author: ankitadutta
@@ -43,7 +42,7 @@ On each Windows machine you want to protect, do the following:
 On each Linux machine that you want to protect, do the following:
 
 1. Ensure that there's network connectivity between the Linux machine and the process server.
-2. Create an account that the process server can use to access the computer. The account should be a **root** user on the source Linux server. Use this account only for the push installation and for updates.
+2. Use the built-in **root** user account which the process server will use to access the computer. This account should be a **root** user on the source Linux server. Use this account only for the push installation and for updates.
 3. Check that the /etc/hosts file on the source Linux server has entries that map the local hostname to IP addresses associated with all network adapters.
 4. Install the latest openssh, openssh-server, and openssl packages on the computer that you want to replicate.
 5. Ensure that Secure Shell (SSH) is enabled and running on port 22.
@@ -55,7 +54,7 @@ On each Linux machine that you want to protect, do the following:
       ![Linux](./media/vmware-azure-install-mobility-service/mobility2.png)
 
 8. Restart the **sshd** service.
-9. Add the account that you created in CSPSConfigtool. To do this, sign in to your configuration server.
+9. Add the root user account in CSPSConfigtool. To do this, sign in to your configuration server.
 10. Open **cspsconfigtool.exe**. It's available as a shortcut on the desktop and in the %ProgramData%\home\svsystems\bin folder.
 11. On the **Manage Accounts** tab, select **Add Account**.
 12. Add the account you created.