Merge pull request MicrosoftDocs#935 from MicrosoftDocs/master

Master to live to remove geocode broken link in skype.

Author: kenwith

sharepoint/sharepoint-ps/sharepoint-server/Add-SPProfileSyncConnection.md

@@ -38,7 +38,7 @@ For permissions and the most current information about Windows PowerShell for Sh
 
 ### ----------EXAMPLE----------- 
 ```
-C:\PS>Add-SPProfileSyncConnection -ProfileServiceApplication 888ds256-9ad9-53a9-f135-99eecd245670b -ConnectionForestName "fabrikam.com"-ConnectionDomain "Fabrikam" -ConnectionUserName "Testupa" -ConnectionPassword convertto-securestring "Password1" -asplaintext -force -ConnectionSynchronizationOU "OU=SharePoint Users,DC=fabrikam,DC=com"
+PS C:\>Add-SPProfileSyncConnection -ProfileServiceApplication 888ds256-9ad9-53a9-f135-99eecd245670b -ConnectionForestName "fabrikam.com"-ConnectionDomain "Fabrikam" -ConnectionUserName "Testupa" -ConnectionPassword convertto-securestring "Password1" -asplaintext -force -ConnectionSynchronizationOU "OU=SharePoint Users,DC=fabrikam,DC=com"
 ```
 
 This example adds a user from the fabrikam ___domain using a specific user profile service application.
@@ -316,7 +316,7 @@ Accept wildcard characters: False
 ```
 
 ### -ConnectionFilterOutUnlicensed
-{{Fill ConnectionFilterOutUnlicensed Description}}
+Do not use.
 
 ```yaml
 Type: Boolean
@@ -332,13 +332,16 @@ Accept wildcard characters: False
 ```
 
 ### -ConnectionUseDisabledFilter
-{{Fill ConnectionUseDisabledFilter Description}}
+Filters out disabled accounts.
+
+>[!NOTE] 
+This will only filter out accounts which are in a disabled state prior to being imported. It will not filter out accounts which have been disabled after importing.
 
 ```yaml
 Type: Boolean
 Parameter Sets: (All)
 Aliases: 
-Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016
+Applicable: SharePoint Server 2013, SharePoint Server 2016
 
 Required: False
 Position: Named

sharepoint/sharepoint-ps/sharepoint-server/Get-SPAccessServicesApplication.md

@@ -8,7 +8,9 @@ schema: 2.0.0
 # Get-SPAccessServicesApplication
 
 ## SYNOPSIS
-Returns an Access Services application or a collection of Access Services applications.
+
+Gets an Access Services Service Application.
+
 
 ## SYNTAX
 
@@ -18,28 +20,34 @@ Get-SPAccessServicesApplication [[-Identity] <SPServiceApplicationPipeBind>]
 ```
 
 ## DESCRIPTION
-The `Get-SPAccessServicesApplication` cmdlet retrieves an Access Services Service Applications. If an identity is not specified, the cmdlet returns the collection of Access Services applications that are in the farm. The properties returned from this cmdlet are read-only.
+
+Returns Access Services service applications available in the farm.
+
 
 ## EXAMPLES
 
 ### Example 1 
 ```
-PS C:\>Get-SPAccessServicesApplication
+
+PS C:\>$sa = Get-SPServiceApplication| ?{$_.TypeName -eq 'Access Services Web Service Application'}
+PS C:\>Get-SPAccessServicesApplication -Identity $sa
+
 ```
-Gets all Access Services Service Applications in the farm
+Returns the Access Services application using a service application pipebind.
 
-### Example 2
+### Example 2 
 ```
-PS C:\>Get-SPAccessServicesApplication -Identity 'Access Services Application'
+PS C:\>Get-SPAccessServicesApplication -Identity 0d1da6e4-5cd6-4ccf-9ae1-ace2e964223a
 ```
 
-Gets the Access Services Service Application named 'Access Services Application'.
+Returns the Access Services application with the specified GUID.
+
 
 ## PARAMETERS
 
 ### -AssignmentCollection
-Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the
-objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used.
+
+Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used.
 
 When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur.
 
@@ -57,7 +65,9 @@ Accept wildcard characters: False
 ```
 
 ### -Identity
-The identity of the Access Services Service Application. This can be in the format of a string, GUID, or a pipe bind object.
+
+Must be in the form of a Service Application pipe bind or a GUID.
+
 
 ```yaml
 Type: SPServiceApplicationPipeBind

sharepoint/sharepoint-ps/sharepoint-server/Get-SPAccessServicesDatabase.md

@@ -8,7 +8,7 @@ schema: 2.0.0
 # Get-SPAccessServicesDatabase
 
 ## SYNOPSIS
-{{Fill in the Synopsis}}
+Returns an Access Services database.
 
 ## SYNTAX
 
@@ -19,21 +19,26 @@ Get-SPAccessServicesDatabase [[-Identity] <AccessServicesDatabasePipeBind>]
 ```
 
 ## DESCRIPTION
-{{Fill in the Description}}
+Returns an Access Services database.
 
 ## EXAMPLES
 
 ### Example 1 
 ```
-PS C:\> {{ Add example code here }}
+PS C:\>Get-SPAccessServicesDatabase -Identity https://apps-eec88dc5f597c6.contoso-apps.com/sites/team/accessApp
 ```
+Using the App Web, this example returns the Access database named 'accessApp'.
 
-{{ Add example description here }}
+### Example 2 
+```
+PS C:\>Get-SPAccessServicesDatabase -ContentDb WSS_Content
+```
+This example returns all Access databases associated with sites in the content database, WSS_Content.
 
 ## PARAMETERS
 
 ### -AccessAppsOnly
-{{Fill AccessAppsOnly Description}}
+Returns only Access Apps.
 
 ```yaml
 Type: Boolean
@@ -49,7 +54,9 @@ Accept wildcard characters: False
 ```
 
 ### -AssignmentCollection
-{{Fill AssignmentCollection Description}}
+Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used.
+
+When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur.
 
 ```yaml
 Type: SPAssignmentCollection
@@ -65,7 +72,7 @@ Accept wildcard characters: False
 ```
 
 ### -ContentDb
-{{Fill ContentDb Description}}
+The Content Database to return Access Apps from.
 
 ```yaml
 Type: SPContentDatabasePipeBind
@@ -81,7 +88,7 @@ Accept wildcard characters: False
 ```
 
 ### -Identity
-{{Fill Identity Description}}
+The URL to the Access App. Must be the App Web URL.
 
 ```yaml
 Type: AccessServicesDatabasePipeBind

sharepoint/sharepoint-ps/sharepoint-server/Get-SPAccessServicesDatabaseServer.md

@@ -8,7 +8,7 @@ schema: 2.0.0
 # Get-SPAccessServicesDatabaseServer
 
 ## SYNOPSIS
-{{Fill in the Synopsis}}
+Returns SQL Server instances associated with Access Services.
 
 ## SYNTAX
 
@@ -27,21 +27,32 @@ Get-SPAccessServicesDatabaseServer [-ServiceContext] <SPServiceContextPipeBind>
 ```
 
 ## DESCRIPTION
-{{Fill in the Description}}
+Returns the SQL Server instances that are available for use with Access Services.
 
 ## EXAMPLES
 
 ### Example 1 
 ```
-PS C:\> {{ Add example code here }}
+PS C:\>Get-SPAccessServicesDatabaseServer
 ```
 
-{{ Add example description here }}
+Returns all SQL Server instances available for use.
+
+
+### Example 2 
+```
+PS C:\>Get-SPAccessServicesDatabaseServer -DatabaseServer ACCSQL -ServiceContext http://siteUrl -DatabaseServergroup DEFAULT
+```
+
+Returns the database server ACCSQL from the DEFAULT database server group using the service context from http://siteUrl.
+
 
 ## PARAMETERS
 
 ### -AssignmentCollection
-{{Fill AssignmentCollection Description}}
+Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used.
+
+When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur.
 
 ```yaml
 Type: SPAssignmentCollection
@@ -57,7 +68,7 @@ Accept wildcard characters: False
 ```
 
 ### -DatabaseServer
-{{Fill DatabaseServer Description}}
+Specifies an existing Database Server associated with Access Services.
 
 ```yaml
 Type: AccessServicesDatabaseServerPipeBind
@@ -73,7 +84,7 @@ Accept wildcard characters: False
 ```
 
 ### -DatabaseServerGroup
-{{Fill DatabaseServerGroup Description}}
+The name of the database server group.
 
 ```yaml
 Type: AccessServicesDatabaseServerGroupPipeBind
@@ -102,7 +113,7 @@ Accept wildcard characters: False
 ```
 
 ### -ServiceContext
-{{Fill ServiceContext Description}}
+Specifies the service context to retrieve Access Services database server information from.
 
 ```yaml
 Type: SPServiceContextPipeBind

sharepoint/sharepoint-ps/sharepoint-server/Remove-FASTSearchMetadataCrawledPropertyMapping.md

@@ -31,11 +31,11 @@ For permissions and the most current information about FAST Search Server 2010 f
 
 ### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010)
 ```
-C:\PS>$title = Get-FASTSearchMetadataManagedProperty -name title
-$crawledproperties = $title.GetCrawledPropertyMappings()
-$crawledproperties # To List the output before the removal
-Remove-FASTSearchMetadataCrawledPropertyMapping -managedproperty $title -crawledproperty $crawledproperties[4]
-$crawledproperties # To list the output after the removal
+PS C:\>$title = Get-FASTSearchMetadataManagedProperty -name title
+PS C:\>$crawledproperties = $title.GetCrawledPropertyMappings()
+PS C:\>$crawledproperties # To List the output before the removal
+PS C:\>Remove-FASTSearchMetadataCrawledPropertyMapping -managedproperty $title -crawledproperty $crawledproperties[4]
+PS C:\>$crawledproperties # To list the output after the removal
 ```
 
 This example removes the mapping of the crawled property "sitemap.title" to the managed property "title".

sharepoint/sharepoint-ps/sharepoint-server/Remove-FASTSearchMetadataFullTextIndexMapping.md

@@ -28,10 +28,10 @@ For permissions and the most current information about FAST Search Server 2010 f
 
 ### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010)
 ```
-C:\PS>$fulltextindex = Get-FASTSearchMetadataFullTextIndex -Name content
-$managedproperty = Get-FASTSearchMetadataManagedProperty -Name CreatedBy
-$fulltextindexmapping = Get-FASTSearchMetadataFullTextIndexMapping -ManagedProperty $managedproperty -FullTextIndex $fulltextindex
-Remove-FASTSearchMetadataFullTextIndexMapping -mapping $fulltextindexmapping
+PS C:\>$fulltextindex = Get-FASTSearchMetadataFullTextIndex -Name content
+PS C:\>$managedproperty = Get-FASTSearchMetadataManagedProperty -Name CreatedBy
+PS C:\>$fulltextindexmapping = Get-FASTSearchMetadataFullTextIndexMapping -ManagedProperty $managedproperty -FullTextIndex $fulltextindex
+PS C:\>Remove-FASTSearchMetadataFullTextIndexMapping -mapping $fulltextindexmapping
 ```
 
 This example removes the mapping of the managed property "CreatedBy" from the full text index "content".

sharepoint/sharepoint-ps/sharepoint-server/Remove-FASTSearchMetadataManagedProperty.md

@@ -34,16 +34,16 @@ For permissions and the most current information about FAST Search Server 2010 f
 
 ### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010)
 ```
-C:\PS>Remove-FASTSearchMetadataManagedProperty -Name title
+PS C:\>Remove-FASTSearchMetadataManagedProperty -Name title
 ```
 
 This example removes the managed property named "title" from the system.
 It will ask for confirmation before going through with the removal unless Force is specified.
 
 ### ---------------EXAMPLE 2----------------- (FAST Server for SharePoint 2010)
 ```
-C:\PS>$createdby = Get-FASTSearchMetadataManagedProperty -name CreatedBy
-Remove-FASTSearchMetadataManagedProperty -ManagedProperty $createdby -Force
+PS C:\>$createdby = Get-FASTSearchMetadataManagedProperty -name CreatedBy
+PS C:\>Remove-FASTSearchMetadataManagedProperty -ManagedProperty $createdby -Force
 ```
 
 This example removes the managed property represented by the object $managedproperty.

sharepoint/sharepoint-ps/sharepoint-server/Remove-FASTSearchMetadataRankProfile.md

@@ -37,15 +37,15 @@ For permissions and the most current information about FAST Search Server 2010 f
 
 ### ---------------EXAMPLE 1----------------- (FAST Server for SharePoint 2010)
 ```
-C:\PS>Remove-FASTSearchMetadataRankProfile -Name webcontent
+PS C:\>Remove-FASTSearchMetadataRankProfile -Name webcontent
 ```
 
 This example removes the rank profile "webcontent".
 
 ### ---------------EXAMPLE 2----------------- (FAST Server for SharePoint 2010)
 ```
-C:\PS>$rankprofile = Get-FASTSearchMetadataRankProfile -Name newrankprofile
-Remove-FASTSearchMetadataRankProfile -Force -RankProfile $rankprofile
+PS C:\>$rankprofile = Get-FASTSearchMetadataRankProfile -Name newrankprofile
+PS C:\>Remove-FASTSearchMetadataRankProfile -Force -RankProfile $rankprofile
 ```
 
 This example deletes the rank profile object which represents the rank profile named "newrankprofile".

sharepoint/sharepoint-ps/sharepoint-server/Remove-FASTSearchSpelltuning.md

@@ -29,7 +29,7 @@ For permissions and the most current information about FAST Search Server 2010 f
 
 ###   (FAST Server for SharePoint 2010)
 ```
-C:\PS>
+PS C:\>Remove-FASTSearchSpelltuning
 ```
 
 ## PARAMETERS

sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchLinksDatabase.md

@@ -30,10 +30,9 @@ For permissions and the most current information about Windows PowerShell for Sh
 
 ### ------------------EXAMPLE------------------
 ```
-C:\PS>$ssa = Get-SPEnterpriseSearchServiceApplication
-$linksDatabase = $ssa | Get-SPEnterpriseSearchLinksDatabase Links2
-
-Remove-SPEnterpriseSearchLinksDatabase -Identity $linksDatabase
+PS C:\>$ssa = Get-SPEnterpriseSearchServiceApplication
+PS C:\>$linksDatabase = $ssa | Get-SPEnterpriseSearchLinksDatabase Links2
+PS C:\>Remove-SPEnterpriseSearchLinksDatabase -Identity $linksDatabase
 ```
 
 This example removes the links database referenced by $linksDatabase.
@@ -60,13 +59,9 @@ Accept wildcard characters: False
 ```
 
 ### -AssignmentCollection
-Manages objects for the purpose of proper disposal.
-Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management.
-Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory.
-When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used.
+Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used.
 
-When the Global parameter is used, all objects are contained in the global store.
-If objects are not immediately used, or disposed of by using the `Stop-SPAssignment` command, an out-of-memory scenario can occur.
+When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur.
 
 ```yaml
 Type: SPAssignmentCollection