Fix links

Author: David Curwin

articles/backup/back-up-hyper-v-virtual-machines-mabs.md

@@ -140,7 +140,7 @@ To set up protection for live migration:
 
 3. Assign the MABSMachineName$ account as a read-only administrator account on the VMM management server.
 
-4. Connect all Hyper-V host servers to all MABS servers with the `Set-DPMGlobalProperty` PowerShell cmdlet. The cmdlet accepts multiple MABS server names. Use the format: `Set-DPMGlobalProperty -dpmservername <MABSservername> -knownvmmservers <vmmservername>`. For more information, see [Set-DPMGlobalProperty](https://technet.microsoft.com/library/hh881752.aspx).
+4. Connect all Hyper-V host servers to all MABS servers with the `Set-DPMGlobalProperty` PowerShell cmdlet. The cmdlet accepts multiple MABS server names. Use the format: `Set-DPMGlobalProperty -dpmservername <MABSservername> -knownvmmservers <vmmservername>`. For more information, see [Set-DPMGlobalProperty](https://docs.microsoft.com/powershell/module/dataprotectionmanager/set-dpmglobalproperty?view=systemcenter-ps-2019).
 
 5. After all virtual machines running on the Hyper-V hosts in the VMM clouds are discovered in VMM, set up a protection group and add the virtual machines you want to protect. Automatic consistency checks should be enabled at the protection group level for protection under virtual machine mobility scenarios.
 

articles/backup/backup-azure-backup-exchange-server.md

@@ -32,8 +32,8 @@ Before you continue, make sure that all the [prerequisites](backup-azure-dpm-int
 
 To install the DPM protection agent on the Exchange server, follow these steps:
 
-1. Make sure that the firewalls are correctly configured. See [Configure firewall exceptions for the agent](https://technet.microsoft.com/library/Hh758204.aspx).
-2. Install the agent on the Exchange server by clicking **Management > Agents > Install** in DPM Administrator Console. See [Install the DPM protection agent](https://technet.microsoft.com/library/hh758186.aspx?f=255&MSPPError=-2147217396) for detailed steps.
+1. Make sure that the firewalls are correctly configured. See [Configure firewall exceptions for the agent](https://docs.microsoft.com/previous-versions/system-center/system-center-2012-R2/hh758204(v=sc.12)).
+2. Install the agent on the Exchange server by clicking **Management > Agents > Install** in DPM Administrator Console. See [Install the DPM protection agent](https://docs.microsoft.com/previous-versions/system-center/system-center-2012-R2/hh758186(v=sc.12)) for detailed steps.
 
 ## Create a protection group for the Exchange server
 
@@ -43,7 +43,7 @@ To install the DPM protection agent on the Exchange server, follow these steps:
 4. Select the Exchange server database that you want to protect and click **Next**.
 
    > [!NOTE]
-   > If you are protecting Exchange 2013, check the [Exchange 2013 prerequisites](https://technet.microsoft.com/library/dn751029.aspx).
+   > If you are protecting Exchange 2013, check the [Exchange 2013 prerequisites](https://docs.microsoft.com/previous-versions/system-center/system-center-2012-R2/dn751029(v=sc.12)).
    >
    >
 

articles/backup/backup-azure-backup-sharepoint.md

@@ -237,5 +237,5 @@ In the following example, the *Recovering SharePoint item* has been accidentally
 ## Next steps
 
 * Learn more about DPM Protection of SharePoint - see [Video Series - DPM Protection of SharePoint](https://channel9.msdn.com/Series/Azure-Backup/Microsoft-SCDPM-Protection-of-SharePoint-1-of-2-How-to-create-a-SharePoint-Protection-Group)
-* Review [Release Notes for System Center 2012 - Data Protection Manager](https://technet.microsoft.com/library/jj860415.aspx)
-* Review [Release Notes for Data Protection Manager in System Center 2012 SP1](https://technet.microsoft.com/library/jj860394.aspx)
+* Review [Release Notes for System Center 2012 - Data Protection Manager](https://docs.microsoft.com/previous-versions/system-center/system-center-2012-R2/jj860415(v=sc.12)?redirectedfrom=MSDN)
+* Review [Release Notes for Data Protection Manager in System Center 2012 SP1](https://docs.microsoft.com/previous-versions/system-center/system-center-2012-R2/jj860394(v=sc.12)?redirectedfrom=MSDN)

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

@@ -17,8 +17,8 @@ Before you continue, make sure that Azure Backup Server is [installed and prepar
 
 To install the MABS protection agent on the Exchange server, follow these steps:
 
-1. Make sure that the firewalls are correctly configured. See [Configure firewall exceptions for the agent](https://technet.microsoft.com/library/Hh758204.aspx).
-2. Install the agent on the Exchange server by clicking **Management > Agents > Install** in MABS Administrator Console. See [Install the MABS protection agent](https://technet.microsoft.com/library/hh758186.aspx?f=255&MSPPError=-2147217396) for detailed steps.
+1. Make sure that the firewalls are correctly configured. See [Configure firewall exceptions for the agent](https://docs.microsoft.com/previous-versions/system-center/system-center-2012-R2/hh758204(v=sc.12)).
+2. Install the agent on the Exchange server by clicking **Management > Agents > Install** in MABS Administrator Console. See [Install the MABS protection agent](https://docs.microsoft.com/previous-versions/system-center/system-center-2012-R2/hh758186(v=sc.12)) for detailed steps.
 
 ## Create a protection group for the Exchange server
 
@@ -28,7 +28,7 @@ To install the MABS protection agent on the Exchange server, follow these steps:
 4. Select the Exchange server database that you want to protect and click **Next**.
 
    > [!NOTE]
-   > If you are protecting Exchange 2013, check the [Exchange 2013 prerequisites](https://technet.microsoft.com/library/dn751029.aspx).
+   > If you are protecting Exchange 2013, check the [Exchange 2013 prerequisites](https://docs.microsoft.com/previous-versions/system-center/system-center-2012-R2/dn751029(v=sc.12)).
    >
    >
 

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

@@ -33,7 +33,7 @@ We recommend you perform the below validation, before you start troubleshooting
 
 | Operation | Error details | Workaround |
 | --- | --- | --- |
-| Backup | Replica is inconsistent | Verify that the automatic consistency check option in the Protection Group Wizard is turned on. For more information about the causes of replica inconsistency and relevant suggestions, see the article [Replica is inconsistent](https://technet.microsoft.com/library/cc161593.aspx).<br> <ol><li> In case of System State/BMR backup, verify that Windows Server Backup is installed on the protected server.</li><li> Check for space-related issues in the DPM storage pool on the DPM/Microsoft Azure Backup Server, and allocate storage as required.</li><li> Check the state of the Volume Shadow Copy Service on the protected server. If it is in a disabled state, set it to start manually. Start the service on the server. Then go back to the DPM/Microsoft Azure Backup Server console, and start the sync with the consistency check job.</li></ol>|
+| Backup | Replica is inconsistent | Verify that the automatic consistency check option in the Protection Group Wizard is turned on. For more information about the causes of replica inconsistency and relevant suggestions, see the article [Replica is inconsistent](https://docs.microsoft.com/previous-versions/system-center/data-protection-manager-2006/cc161593(v=technet.10)).<br> <ol><li> In case of System State/BMR backup, verify that Windows Server Backup is installed on the protected server.</li><li> Check for space-related issues in the DPM storage pool on the DPM/Microsoft Azure Backup Server, and allocate storage as required.</li><li> Check the state of the Volume Shadow Copy Service on the protected server. If it is in a disabled state, set it to start manually. Start the service on the server. Then go back to the DPM/Microsoft Azure Backup Server console, and start the sync with the consistency check job.</li></ol>|
 
 ## Online recovery point creation failed
 
@@ -57,7 +57,7 @@ We recommend you perform the below validation, before you start troubleshooting
 
 | Operation | Error details | Workaround |
 | --- | --- | --- |
-| Pushing agent(s) to protected servers | The agent operation failed because of a communication error with the DPM Agent Coordinator service on \<ServerName>. | **If the recommended action shown in the product doesn't work, then perform the following steps**: <ul><li> If you are attaching a computer from an untrusted domain, follow [these steps](https://technet.microsoft.com/library/hh757801(v=sc.12).aspx). <br> (OR) </li><li> If you are attaching a computer from a trusted domain, troubleshoot using the steps outlined in [this blog](https://blogs.technet.microsoft.com/dpm/2012/02/06/data-protection-manager-agent-network-troubleshooting/). <br>(OR)</li><li> Try disabling antivirus as a troubleshooting step. If it resolves the issue, modify the antivirus settings as suggested in [this article](https://technet.microsoft.com/library/hh757911.aspx).</li></ul> |
+| Pushing agent(s) to protected servers | The agent operation failed because of a communication error with the DPM Agent Coordinator service on \<ServerName>. | **If the recommended action shown in the product doesn't work, then perform the following steps**: <ul><li> If you are attaching a computer from an untrusted domain, follow [these steps](https://docs.microsoft.com/previous-versions/system-center/system-center-2012-R2/hh757801(v=sc.12)). <br> (OR) </li><li> If you are attaching a computer from a trusted domain, troubleshoot using the steps outlined in [this blog](https://techcommunity.microsoft.com/t5/system-center-blog/data-protection-manager-agent-network-troubleshooting/ba-p/344726). <br>(OR)</li><li> Try disabling antivirus as a troubleshooting step. If it resolves the issue, modify the antivirus settings as suggested in [this article](https://docs.microsoft.com/previous-versions/system-center/system-center-2012-R2/hh757911(v=sc.12)).</li></ul> |
 
 ## Setup could not update registry metadata
 
@@ -70,7 +70,7 @@ We recommend you perform the below validation, before you start troubleshooting
 
 | Operation | Error details | Workaround |
 | --- | --- | --- |
-| 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](https://technet.microsoft.com/library/hh758186(v=sc.12).aspx#BKMK_Manual).|
+| 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](https://docs.microsoft.com/previous-versions/system-center/system-center-2012-R2/hh758186(v=sc.12)).|
 | 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](backup-configure-vault.md#verify-internet-access) and [IP address](backup-configure-vault.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.
 
@@ -79,8 +79,8 @@ We recommend you perform the below validation, before you start troubleshooting
 | Operation | Error details | Workaround |
 | --- | --- | --- |
 | Configuring protection groups | DPM could not enumerate the application component on the protected computer (protected computer name). | Select **Refresh** on the configure protection group UI screen at the relevant datasource/component level. |
-| Configuring protection groups | Unable to configure protection | If the protected server is a SQL server, verify that the sysadmin role permissions have been provided to the system account (NTAuthority\System) on the protected computer as described in [this article](https://technet.microsoft.com/library/hh757977(v=sc.12).aspx).
-| Configuring protection groups | There is insufficient free space in the storage pool for this protection group. | The disks that are added to the storage pool [should not contain a partition](https://technet.microsoft.com/library/hh758075(v=sc.12).aspx). Delete any existing volumes on the disks. Then add them to the storage pool.|
+| Configuring protection groups | Unable to configure protection | If the protected server is a SQL server, verify that the sysadmin role permissions have been provided to the system account (NTAuthority\System) on the protected computer as described in [this article](https://docs.microsoft.com/previous-versions/system-center/system-center-2012-R2/hh757977(v=sc.12)).
+| Configuring protection groups | There is insufficient free space in the storage pool for this protection group. | The disks that are added to the storage pool [should not contain a partition](https://docs.microsoft.com/previous-versions/system-center/system-center-2012-R2/hh758075(v=sc.12)). Delete any existing volumes on the disks. Then add them to the storage pool.|
 | Policy change |The backup policy could not be modified. Error: The current operation failed due to an internal service error [0x29834]. Please retry the operation after some time has passed. If the issue persists, contact Microsoft support. | **Cause:**<br/>This error occurs under three conditions: when security settings are enabled, when you try to reduce retention range below the minimum values specified previously, and when you are on an unsupported  version. (Unsupported versions are those below Microsoft Azure Backup Server version 2.0.9052 and Azure Backup Server update 1.) <br/>**Recommended action:**<br/> To proceed with policy-related updates, set the retention period above the minimum retention period specified. (The minimum retention period is seven days for daily, four weeks for weekly, three weeks for monthly or one year for yearly.) <br><br>Optionally, another preferred approach is to update the backup agent and Azure Backup Server to leverage all the security updates. |
 
 ## Backup
@@ -91,7 +91,7 @@ We recommend you perform the below validation, before you start troubleshooting
 | Backup | If you are backing up only system state, verify that there is enough free space on the protected computer to store the system state backup. | <ol><li>Verify that Windows Server Backup is installed on the protected machine.</li><li>Verify that there is enough space on the protected computer for the system state. The easiest way to verify this is to go to the protected computer, open Windows Server Backup, click through the selections, and then select BMR. The UI then tells you how much space is required. Open **WSB** > **Local backup** > **Backup schedule** > **Select Backup Configuration** > **Full server** (size is displayed). Use this size for verification.</li></ol>
 | Backup | Back up failure for BMR | If the BMR size is large, move some application files to the OS drive and retry. |
 | Backup | The option to reprotect a VMware VM on a new Microsoft Azure Backup Server does not show as available to add. | VMware properties are pointed at an old, retired instance of Microsoft Azure Backup Server. To resolve this issue:<br><ol><li>In VCenter (SC-VMM equivalent), go to the **Summary** tab, and then to **Custom Attributes**.</li>  <li>Delete the old Microsoft Azure Backup Server name from the **DPMServer** value.</li>  <li>Go back to the new Microsoft Azure Backup Server and modify the PG.  After you select the **Refresh** button, the VM appears with a check box as available to add to protection.</li></ol> |
-| Backup | Error while accessing files/shared folders | Try modifying the antivirus settings as suggested in the TechNet article [Run antivirus software on the DPM server](https://technet.microsoft.com/library/hh757911.aspx).|
+| Backup | Error while accessing files/shared folders | Try modifying the antivirus settings as suggested in this article [Run antivirus software on the DPM server](https://docs.microsoft.com/previous-versions/system-center/system-center-2012-R2/hh757911(v=sc.12)).|
 
 ## Change passphrase
 
@@ -104,7 +104,7 @@ We recommend you perform the below validation, before you start troubleshooting
 
 | Operation | Error details | Workaround |
 | --- | --- | --- |
-| Setting up email notifications using an Office 365 account |Error ID: 2013| **Cause:**<br> Trying to use Office 365 account <br>**Recommended action:**<ol><li> The first thing to ensure is that “Allow Anonymous Relay on a Receive Connector” for your DPM server is set up on Exchange. For more information about how to configure this, see [Allow Anonymous Relay on a Receive Connector](https://technet.microsoft.com/library/bb232021.aspx) on TechNet.</li> <li> If you can't use an internal SMTP relay and need to set up by using your Office 365 server, you can set up IIS to be a relay. Configure the DPM server to [relay the SMTP to O365 using IIS](https://technet.microsoft.com/library/aa995718(v=exchg.65).aspx).<br><br> **IMPORTANT:** Be sure to use the user\@domain.com format and *not* domain\user.<br><br><li>Point DPM to use the local server name as SMTP server, port 587. Then point it to the user email that the emails should come from.<li> The username and password on the DPM SMTP setup page should be for a domain account in the domain that DPM is on. </li><br> **NOTE**: When you are changing the SMTP server address, make the change to the new settings, close the settings box, and then reopen it to be sure it reflects the new value.  Simply changing and testing might not always cause the new settings to take effect, so testing it this way is a best practice.<br><br>At any time during this process, you can clear these settings by closing the DPM console and editing the following registry keys: **HKLM\SOFTWARE\Microsoft\Microsoft Data Protection Manager\Notification\ <br/> Delete SMTPPassword and SMTPUserName keys**. You can add them back to the UI when you launch it again.
+| Setting up email notifications using an Office 365 account |Error ID: 2013| **Cause:**<br> Trying to use Office 365 account <br>**Recommended action:**<ol><li> The first thing to ensure is that “Allow Anonymous Relay on a Receive Connector” for your DPM server is set up on Exchange. For more information about how to configure this, see [Allow Anonymous Relay on a Receive Connector](https://docs.microsoft.com/previous-versions/office/exchange-server-2010/bb232021(v=exchg.141)).</li> <li> If you can't use an internal SMTP relay and need to set up by using your Office 365 server, you can set up IIS to be a relay. Configure the DPM server to [relay the SMTP to O365 using IIS](https://docs.microsoft.com/previous-versions/tn-archive/aa995718(v=exchg.65)).<br><br> **IMPORTANT:** Be sure to use the user\@domain.com format and *not* domain\user.<br><br><li>Point DPM to use the local server name as SMTP server, port 587. Then point it to the user email that the emails should come from.<li> The username and password on the DPM SMTP setup page should be for a domain account in the domain that DPM is on. </li><br> **NOTE**: When you are changing the SMTP server address, make the change to the new settings, close the settings box, and then reopen it to be sure it reflects the new value.  Simply changing and testing might not always cause the new settings to take effect, so testing it this way is a best practice.<br><br>At any time during this process, you can clear these settings by closing the DPM console and editing the following registry keys: **HKLM\SOFTWARE\Microsoft\Microsoft Data Protection Manager\Notification\ <br/> Delete SMTPPassword and SMTPUserName keys**. You can add them back to the UI when you launch it again.
 
 ## Common issues