Merge pull request #215429 from v-amallick/Oct-21-2022-OnPremTS

MABS - TLS 1.2 support updates

Author: prmerger-automator[bot]

articles/backup/backup-azure-mabs-troubleshoot.md

@@ -3,7 +3,7 @@ title: Troubleshoot Azure Backup Server
 description: Troubleshoot installation, registration of Azure Backup Server, and backup and restore of application workloads.
 ms.reviewer: srinathv
 ms.topic: troubleshooting
-ms.date: 08/26/2022
+ms.date: 10/21/2022
 author: v-amallick
 ms.service: backup
 ms.author: v-amallick
@@ -22,7 +22,8 @@ We recommend you perform the following validation, before you start troubleshoot
 - Ensure Microsoft Azure Recovery Services is running (in Service console). If necessary, restart and retry the operation
 - [Ensure 5-10% free volume space is available on scratch folder location](./backup-azure-file-folder-backup-faq.yml#what-s-the-minimum-size-requirement-for-the-cache-folder-)
 - If registration is failing, then ensure the server on which you're trying to install Azure Backup Server isn't already registered with another vault
-- If Push install fails, check if DPM agent is already present. If yes, then uninstall the agent and retry the installation
+- If Push install fails, check if DPM agent is already present. If yes, then uninstall the agent and retry the installation.
+- [Ensure your server is running on TLS 1.2](transport-layer-security.md).
 - [Ensure no other process or antivirus software is interfering with Azure Backup](./backup-azure-troubleshoot-slow-backup-performance-issue.md#cause-another-process-or-antivirus-software-interfering-with-azure-backup)<br>
 - Ensure that the SQL Agent service is running and set to automatic in the MABS server<br>
 
@@ -109,6 +110,7 @@ Reg query "HKLM\SOFTWARE\Microsoft\Microsoft Data Protection Manager\Setup"
 | Pushing agent(s) to protected servers | The credentials that are specified for the server are invalid. | **If the recommended action that's shown in the product doesn't work, take the following steps**: <br> Try to install the protection agent manually on the production server as specified in [this article](/system-center/dpm/deploy-dpm-protection-agent).|
 | Azure Backup Agent was unable to connect to the Azure Backup service (ID: 100050) | The Azure Backup Agent was unable to connect to the Azure Backup service. | **If the recommended action that's shown in the product doesn't work, take the following steps**: <br>1. Run the following command from an elevated prompt: **psexec -i -s "c:\Program Files\Internet Explorer\iexplore.exe**. This opens the Internet Explorer window. <br/> 2. Go to **Tools** > **Internet Options** > **Connections** > **LAN settings**. <br/> 3. Change the settings to use a proxy server. Then provide the proxy server details.<br/> 4. If your machine has limited internet access, ensure that firewall settings on the machine or proxy allow these [URLs](install-mars-agent.md#verify-internet-access) and [IP address](install-mars-agent.md#verify-internet-access).|
 | Azure Backup Agent installation failed | The Microsoft Azure Recovery Services installation failed. All changes that were made to the system by the Microsoft Azure Recovery Services installation were rolled back. (ID: 4024) | Manually install Azure Agent.
+| Server registration status verification with Microsoft Azure Backup failed. | The server registration status could not be verified with Microsoft Azure Backup. Verify that you are connected to the internet and that the proxy settings are configured correctly. | You'll encounter this issue when the MARS agent can't contact Azure services. To resolve this issue: <br><br> - Ensure network connectivity and proxy settings. <br><br> - Ensure that you are running the latest MARS agent. <br><br> - [Ensure your server is running on TLS 1.2](transport-layer-security.md). |
 
 ## Configuring protection group