Remove references to technet wiki

Author: MikeRayMSFT

docs/database-engine/availability-groups/windows/data-synchronization-state-of-availability-database-is-not-healthy.md

@@ -31,9 +31,6 @@ manager: erikre
 ## Description  
  This policy rolls up the data synchronization state of all availability databases (also known as "database replicas") in the availability replica. The policy is in an unhealthy sate when any database replica is not in the expected data synchronization state. The policy is otherwise in a healthy state.  
 
-> [!NOTE]  
->  For this release of [!INCLUDE[ssnoversion](../../../includes/ssnoversion-md.md)], information about possible causes and solutions is located at [Data synchronization state of some availability database is not healthy](https://go.microsoft.com/fwlink/p/?LinkId=220858) on the TechNet Wiki.  
-  
 ## Possible Causes  
  The data synchronization state of this availability database is unhealthy. On an asynchronous-commit availability replica, every availability database should be in the SYNCHRONIZING state. On a synchronous-commit replica, every availability database must be in the SYNCHRONIZED state.  
 

docs/database-engine/availability-groups/windows/secondary-database-is-not-joined.md

@@ -29,10 +29,7 @@ ms.author: chadam
 
 ## Description  
  This policy checks the join state of the secondary database (also known as a "secondary database replica"). The policy is in an unhealthy state when the dataset replica is not joined. The policy is otherwise in a healthy state.  
-  
-> [!NOTE]  
->  For this release of [!INCLUDE[ssnoversion](../../../includes/ssnoversion-md.md)], information about possible causes and solutions is located at [Secondary database is not joined](https://go.microsoft.com/fwlink/p/?LinkId=220862) on the TechNet Wiki.  
-  
+
 ## Possible Causes  
  This secondary database is not joined to the availability group. The configuration of this secondary database is incomplete.  
 

docs/database-engine/availability-groups/windows/some-availability-replicas-are-disconnected.md

@@ -29,10 +29,7 @@ ms.author: chadam
 
 ## Description  
  This policy rolls up the connection state of all availability replicas and checks for any availability replicas that are DISCONENCTED. The policy is in an unhealthy state when any availability replica is DISCONNECTED. The policy is otherwise in a healthy state.  
-  
-> [!NOTE]  
->  For this release of [!INCLUDE[ssnoversion](../../../includes/ssnoversion-md.md)], information about possible causes and solutions is located at [Some availability replicas are disconnected](https://go.microsoft.com/fwlink/p/?LinkId=220855) on the TechNet Wiki.  
-  
+ 
 ## Possible Causes  
  In this availability group, at least one secondary replica is not connected to the primary replica. The connected state is DISCONNECTED.  
 

docs/database-engine/availability-groups/windows/some-availability-replicas-are-not-synchronizing-data.md

@@ -31,10 +31,7 @@ ms.author: chadam
  This policy rolls up the data synchronization state of all availability replicas in the availability group and checks if the synchronization of any availability replica is not operational. The policy is in an unhealthy state if any of the data synchronization states of the availability replica is NOT SYNCRONIZING.  
 
  This policy is in a healthy state if none of the data synchronization states of the availability replica is NOT SYNCHRONIZING.  
-  
-> [!NOTE]  
->  For this release of [!INCLUDE[ssnoversion](../../../includes/ssnoversion-md.md)], information about possible causes and solutions is located at [Some availability replicas are not synchronizing data](https://go.microsoft.com/fwlink/p/?LinkId=220852) on the TechNet Wiki.  
-  
+ 
 ## Possible Causes  
  In this availability group, at least one secondary replica has a NOT SYNCHRONIZING synchronization state and is not receiving data from the primary replica.  
 

docs/database-engine/availability-groups/windows/some-synchronous-replicas-are-not-synchronized.md

@@ -29,10 +29,7 @@ ms.author: chadam
 
 ## Description  
  This policy rolls up the data synchronization state of all availability replicas and checks for any availability replicas that are not in the expected synchronization state. The policy is in an unhealthy state when any asynchronous replica is not in a SYNCHRONIZING state and any synchronous replica is not in a SYNCHRONIZED state. The policy state is otherwise healthy.  
-  
-> [!NOTE]  
->  For this release of [!INCLUDE[ssnoversion](../../../includes/ssnoversion-md.md)], information about possible causes and solutions is located at [Some synchronous replicas are not synchronized](https://go.microsoft.com/fwlink/p/?LinkId=220853) on the TechNet Wiki.  
-  
+
 ## Possible Causes  
  In this availability group, at least one synchronous replica is not currently synchronized. The replica synchronization state could be either SYNCHRONIZING or NOT SYNCHRONIZING.  
 

docs/database-engine/availability-groups/windows/wsfc-cluster-service-is-offline.md

@@ -32,11 +32,8 @@ monikerRange: ">=sql-server-2016"
 ## Description  
  This policy checks the state of the Windows Server Failover Cluster (WSFC). The policy is in an unhealthy state and an alert is raised when the WSFC cluster is offline or in the forced quorum state. All availability groups hosted within this cluster are offline or a disaster recovery action is required.  
 
- The policy state is healthy when the cluster state is in the normal quorum.  
-  
-> [!NOTE]  
->  For this release of [!INCLUDE[ssnoversion](../../../includes/ssnoversion-md.md)], information about possible causes and solutions is located at [WSFC cluster service is offline](https://go.microsoft.com/fwlink/p/?LinkId=220849) on the TechNet Wiki.  
-  
+ The policy state is healthy when the cluster state is in the normal quorum.
+
 ## Possible Causes  
  This issue can be caused by a cluster service issue or by the loss of the quorum in the cluster.  
 

docs/master-data-services/install-windows/install-master-data-services.md

@@ -51,9 +51,7 @@ ms.author: lle
 |Enable Data Quality Services (DQS) integration|For users of the [!INCLUDE[ssMDSshort](../../includes/ssmdsshort-md.md)][!INCLUDE[ssMDSXLS](../../includes/ssmdsxls-md.md)], enable integration with the DQS feature, which can be used to match similar data.|[Enable Data Quality Services Integration with Master Data Services](../../master-data-services/install-windows/enable-data-quality-services-integration-with-master-data-services.md)|  
 |Deploy a sample model|Sample model packages are installed with Master Data Services, and can be deployed using MDSModelDeploy.exe.|[Deploying MDS Samples in SQL Server](~/master-data-services/sql-server-samples-model-deployment-packages-mds.md)|
 
- If you encounter issues during the installation process or initial configuration, see [Troubleshooting Installation and Configuration Issues](https://social.technet.microsoft.com/wiki/contents/articles/troubleshooting-installation-and-configuration-issues-master-data-services.aspx) on TechNet Wiki.  
-  
- If you no longer need [!INCLUDE[ssMDSshort](../../includes/ssmdsshort-md.md)] on a computer, you can uninstall [!INCLUDE[ssMDSshort](../../includes/ssmdsshort-md.md)] and determine whether to remove items that are not affected by the uninstall process. For more information, see [Uninstall and Remove Master Data Services](../../sql-server/install/uninstall-and-remove-master-data-services.md).  
+If you no longer need [!INCLUDE[ssMDSshort](../../includes/ssmdsshort-md.md)] on a computer, you can uninstall [!INCLUDE[ssMDSshort](../../includes/ssmdsshort-md.md)] and determine whether to remove items that are not affected by the uninstall process. For more information, see [Uninstall and Remove Master Data Services](../../sql-server/install/uninstall-and-remove-master-data-services.md).  
 
 ## See Also  
  [Install SQL Server 2016](../../database-engine/install-windows/install-sql-server.md)  

docs/reporting-services/report-server-sharepoint/reporting-services-report-server-sharepoint-mode.md

@@ -128,7 +128,6 @@ monikerRange: ">=sql-server-2016 <=sql-server-2016"
 |Scale-out your Reporting Services SharePoint deployment by adding additional report servers.|[Add an additional Report Server to a Farm](../../reporting-services/install-windows/add-an-additional-report-server-to-a-farm-ssrs-scale-out.md) and [Deployment topologies for SQL Server BI features in SharePoint](/previous-versions/sql/sql-server-2016/hh231674(v=sql.130)).|  
 |Add additional SharePoint web front-ends that have the Reporting Services components installed for viewing and report items.|[Add an additional Reporting Services web front-end to a farm](../../reporting-services/install-windows/add-an-additional-reporting-services-web-front-end-to-a-farm.md)|  
 |Configure e-mail for your report server within SharePoint.|[Configure e-mail for a Reporting Services service application](../install-windows/configure-e-mail-for-a-reporting-services-service-application.md)|
-|Recent information for this release, found on the TechNet Wiki.|[SQL Server 2012 Reporting Services tips, tricks, and troubleshooting](https://go.microsoft.com/fwlink/?LinkId=221297).|  
 
 ## Next steps