Merge pull request MicrosoftDocs#149 from nsshommo/nasim

Clean Up and Consolidate

Author: kenwith

exchange/exchange-ps/exchange/Enable-AddressListPaging.md

@@ -3,15 +3,9 @@ applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
 schema: 2.0.0
 ---
 
-# enable-AddressListPaging
+# Enable-AddressListPaging
 
 ## SYNOPSIS
-!!! Exchange Server 2010
-
-Use the Enable-AddressListPaging cmdlet to enable Active Directory virtual list view for address lists. Virtual list view allows you to display the address lists in your organization as pages instead of loading and viewing the entire directory.
-
-!!! Exchange Server 2013, Exchange Server 2016
-
 This cmdlet is available only in on-premises Exchange.
 
 Use the Enable-AddressListPaging cmdlet to enable Active Directory virtual list view for address lists. Virtual list view allows you to display the address lists in your organization as pages instead of loading and viewing the entire directory.
@@ -21,31 +15,10 @@ For information about the parameter sets in the Syntax section below, see Exchan
 ## SYNTAX
 
 ```
-enable-AddressListPaging [[-Identity] <OrganizationIdParameter>] [-Confirm] [-DomainController <Fqdn>]
- [-DoNotUpdateRecipients] [-ForceUpdateOfRecipients] [-WhatIf] [<CommonParameters>]
+Enable-AddressListPaging [-Confirm] [-DomainController <Fqdn>] [-WhatIf] [<CommonParameters>]
 ```
 
 ## DESCRIPTION
-!!! Exchange Server 2010
-
-The Enable-AddressListPaging cmdlet creates the Address List container in Active Directory. Exchange 2010 recipient cmdlets, such as Get-Recipient, use the information written to the container to quickly retrieve recipient data.
-
-Exchange 2007 can't read the Address List container and will clear its contents while managing address lists. As a result, the Exchange 2010 recipient cmdlets won't return any recipient data. If you're in a coexistence deployment with Exchange 2007, and you use Exchange 2007 servers to manage address lists, don't enable address list paging. If you've already enabled address list paging, you can disable it by running the Disable-AddressListPaging cmdlet.
-
-You need to be assigned permissions before you can run this cmdlet. Although all parameters for this cmdlet are listed in this topic, you may not have access to some parameters if they're not included in the permissions assigned to you. To see what permissions you need, see the "Address lists" entry in the Mailbox Permissions topic.
-
-!!! Exchange Server 2013
-
-The Enable-AddressListPaging cmdlet creates the Address List container in Active Directory. Recipient cmdlets, such as Get-Recipient, use the information written to the container to quickly retrieve recipient data.
-
-Microsoft Exchange Server 2007 can't read the Address List container and will clear its contents while managing address lists. As a result, the Exchange Server 2010 or later recipient cmdlets won't return any recipient data. If you're in a coexistence deployment with Exchange 2007, and you use Exchange 2007 servers to manage address lists, don't enable address list paging. If you've already enabled address list paging, you can disable it by running the Disable-AddressListPaging cmdlet.
-
-You need to be assigned permissions before you can run this cmdlet. Although all parameters for this cmdlet are listed in this topic, you may not have access to some parameters if they're not included in the permissions assigned to you. To see what permissions you need, see the "Address lists" entry in the Email address and address book permissions topic.
-
-By default in Exchange Online, the Address List role isn't assigned to any role groups. To use any cmdlets that require the Address List role, you need to add the role to a role group. For more information, see the "Add a role to a role group" section in the topic, Manage role groups.
-
-!!! Exchange Server 2016
-
 The Enable-AddressListPaging cmdlet creates the Address List container in Active Directory. Recipient cmdlets, such as Get-Recipient, use the information written to the container to quickly retrieve recipient data.
 
 You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://technet.microsoft.com/library/mt432940.aspx).
@@ -54,21 +27,7 @@ By default in Exchange Online, the Address List role isn't assigned to any role
 
 ## EXAMPLES
 
-### Example 1 -------------------------- (Exchange Server 2010)
-```
-Enable-AddressListPaging
-```
-
-This example enables virtual list view for your organization.
-
-### Example 1 -------------------------- (Exchange Server 2013)
-```
-Enable-AddressListPaging
-```
-
-This example enables virtual list view for your organization.
-
-### Example 1 -------------------------- (Exchange Server 2016)
+### Example 1
 ```
 Enable-AddressListPaging
 ```
@@ -78,26 +37,12 @@ This example enables virtual list view for your organization.
 ## PARAMETERS
 
 ### -Confirm
-!!! Exchange Server 2010, Exchange Server 2013
-
-The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
-
-- Destructive cmdlets (for example, Remove-* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false.
-
-- Most other cmdlets (for example, New-* and Set-* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding.
-
-
-
-!!! Exchange Server 2016
-
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
 - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false.
 
 - Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding.
 
-
-
 ```yaml
 Type: SwitchParameter
 Parameter Sets: (All)
@@ -127,60 +72,6 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
-### -DoNotUpdateRecipients
-This parameter is available for multi-tenant deployments. It isn't available for on-premises deployments. For more information about multi-tenant deployments, see Multi-Tenant Support.
-
-The DoNotUpdateRecipients switch specifies that the Address List container be created in Active Directory but no recipients be added to the virtual list view.
-
-```yaml
-Type: SwitchParameter
-Parameter Sets: (All)
-Aliases:
-Applicable: Exchange Server 2010
-
-Required: False
-Position: Named
-Default value: None
-Accept pipeline input: False
-Accept wildcard characters: False
-```
-
-### -ForceUpdateOfRecipients
-This parameter is available for multi-tenant deployments. It isn't available for on-premises deployments. For more information about multi-tenant deployments, see Multi-Tenant Support.
-
-The ForceUpdateOfRecipients switch specifies that all system address lists be updated.
-
-```yaml
-Type: SwitchParameter
-Parameter Sets: (All)
-Aliases:
-Applicable: Exchange Server 2010
-
-Required: False
-Position: Named
-Default value: None
-Accept pipeline input: False
-Accept wildcard characters: False
-```
-
-### -Identity
-This parameter is available for multi-tenant deployments. It isn't available for on-premises deployments. For more information about multi-tenant deployments, see Multi-Tenant Support.
-
-The Identity parameter specifies the identity of the tenant organization.
-
-```yaml
-Type: OrganizationIdParameter
-Parameter Sets: (All)
-Aliases:
-Applicable: Exchange Server 2010
-
-Required: False
-Position: 1
-Default value: None
-Accept pipeline input: True
-Accept wildcard characters: False
-```
-
 ### -WhatIf
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -215,4 +106,3 @@ To see the return types, which are also known as output types, that this cmdlet
 ## RELATED LINKS
 
 [Online Version](https://technet.microsoft.com/library/d20e96a9-8742-4f6b-8acc-6433e79a23db.aspx)
-

exchange/exchange-ps/exchange/Set-MapiVirtualDirectory.md

@@ -6,14 +6,6 @@ schema: 2.0.0
 # Set-MapiVirtualDirectory
 
 ## SYNOPSIS
-!!! Exchange Server 2013
-
-This cmdlet is available only in on-premises Exchange.
-
-Use the Set-MapiVirtualDirectory cmdlet to modify Messaging Application Programming Interface (MAPI) virtual directories on MicrosoftExchange 2013 servers. A MAPI virtual directory is used by supported versions of MicrosoftOutlook to connect to mailboxes by using the MAPIHTTP protocol.
-
-!!! Exchange Server 2016
-
 This cmdlet is available only in on-premises Exchange.
 
 Use the Set-MapiVirtualDirectory cmdlet to modify Messaging Application Programming Interface (MAPI) virtual directories that are used in Internet Information Services (IIS) on Microsoft Exchange servers. A MAPI virtual directory is used by supported versions of Microsoft Outlook to connect to mailboxes by using the MAPIHTTP protocol.
@@ -22,46 +14,25 @@ Use the Set-MapiVirtualDirectory cmdlet to modify Messaging Application Programm
 
 ```
 Set-MapiVirtualDirectory [-Identity] <VirtualDirectoryIdParameter> [-ApplyDefaults <$true | $false>] [-Confirm]
- [-DomainController <Fqdn>] [-ExtendedProtectionFlags <MultiValuedProperty>]
- [-ExtendedProtectionSPNList <MultiValuedProperty>] [-ExtendedProtectionTokenChecking <None | Allow | Require>]
- [-ExternalUrl <Uri>] [-IISAuthenticationMethods <MultiValuedProperty>] [-InternalUrl <Uri>] [-WhatIf]
+ [-DomainController <Fqdn>] [-ExternalUrl <Uri>] [-IISAuthenticationMethods <MultiValuedProperty>] [-InternalUrl <Uri>] [-WhatIf]
  [<CommonParameters>]
 ```
 
 ## DESCRIPTION
-!!! Exchange Server 2013
-
-You need to be assigned permissions before you can run this cmdlet. Although all parameters for this cmdlet are listed in this topic, you may not have access to some parameters if they're not included in the permissions assigned to you. To see what permissions you need, see the "Client Access virtual directory settings" entry in the Clients and mobile devices permissions topic.
-
-!!! Exchange Server 2016
-
 You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://technet.microsoft.com/library/mt432940.aspx).
 
 ## EXAMPLES
 
-### Example 1 -------------------------- (Exchange Server 2013)
-```
-Set-MapiVirtualDirectory -Identity "ContosoMail\mapi (Default Web Site)" -InternalUrl https://contoso.com/mapi -IISAuthenticationMethods NTLM,Negotiate
-```
-
-This example makes the following configuration changes to the MAPI virtual directory on the default web site of the server named ContosoMail:
-
-
-Internal URL https://contoso/mapi.
-
-IIS authentication methods NTLM and Negotiate.
-
-### Example 1 -------------------------- (Exchange Server 2016)
+### Example 1
 ```
 Set-MapiVirtualDirectory -Identity "ContosoMail\mapi (Default Web Site)" -InternalUrl https://contoso.com/mapi -IISAuthenticationMethods NTLM,Negotiate,OAuth
 ```
 
 This example makes the following configuration changes to the MAPI virtual directory on the default web site of the server named ContosoMail:
 
+- Internal URL: https://contoso/mapi.
 
-Internal URL: https://contoso/mapi.
-
-IIS authentication methods: NTLM, Negotiate, and OAuth.
+- IIS authentication methods: NTLM, Negotiate, and OAuth.
 
 ## PARAMETERS
 
@@ -92,7 +63,7 @@ Accept wildcard characters: False
 ```
 
 ### -ApplyDefaults
-The ApplyDefaults switch specifies whether to apply the correct defaults to the related internal IIS application settings. Typically, this switch is used only by Exchange setup during the installation of Exchange Cumulative Updates or Service Packs, and you shouldn't need to use it.
+The ApplyDefaults switch specifies whether to apply the correct defaults to the related internal IIS application settings. Typically, this switch is used only by Exchange setup during the installation of Exchange Cumulative Updates or Service Packs and you shouldn't need to use it.
 
 This switch doesn't affect the values you configure by using the IISAuthenticationMethods, InternalUrl or ExternalUrl parameters.
 
@@ -145,54 +116,6 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
-### -ExtendedProtectionFlags
-This parameter is reserved for internal Microsoft use.
-
-```yaml
-Type: MultiValuedProperty
-Parameter Sets: (All)
-Aliases:
-Applicable: Exchange Server 2013
-
-Required: False
-Position: Named
-Default value: None
-Accept pipeline input: False
-Accept wildcard characters: False
-```
-
-### -ExtendedProtectionSPNList
-This parameter is reserved for internal Microsoft use.
-
-```yaml
-Type: MultiValuedProperty
-Parameter Sets: (All)
-Aliases:
-Applicable: Exchange Server 2013
-
-Required: False
-Position: Named
-Default value: None
-Accept pipeline input: False
-Accept wildcard characters: False
-```
-
-### -ExtendedProtectionTokenChecking
-This parameter is reserved for internal Microsoft use.
-
-```yaml
-Type: None | Allow | Require
-Parameter Sets: (All)
-Aliases:
-Applicable: Exchange Server 2013
-
-Required: False
-Position: Named
-Default value: None
-Accept pipeline input: False
-Accept wildcard characters: False
-```
-
 ### -ExternalUrl
 The ExternalURL parameter specifies the URL that's used to connect to the virtual directory from outside the firewall.
 
@@ -214,24 +137,6 @@ Accept wildcard characters: False
 ```
 
 ### -IISAuthenticationMethods
-!!! Exchange Server 2013
-
-The IISAuthenticationMethods parameter specifies the authentication methods that are enabled on the virtual directory in Internet Information Services (IIS). Valid values for this parameter are:
-
-- Basic
-
-- Negotiate
-
-- NTLM
-
-To enter multiple values and overwrite any existing entries, use the following syntax: \<value1\>,\<value2\>.... If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\<value1\>","\<value2\>"....
-
-To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="\<value1\>","\<value2\>"...; Remove="\<value1\>","\<value2\>"...}.
-
-
-
-!!! Exchange Server 2016
-
 The IISAuthenticationMethods parameter specifies the authentication methods that are enabled on the virtual directory in Internet Information Services (IIS). Valid values are:
 
 - Basic
@@ -246,8 +151,6 @@ You can specify multiple values separated by commas.
 
 The default values are NTLM, OAuth, and Negotiate. We recommend that you always have the virtual directory configured for OAuth.
 
-
-
 ```yaml
 Type: MultiValuedProperty
 Parameter Sets: (All)
@@ -298,7 +201,7 @@ Accept wildcard characters: False
 ```
 
 ### CommonParameters
-This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see about_CommonParameters (https://go.microsoft.com/fwlink/p/?LinkID=113216).
+This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction and -WarningVariable. For more information, see about_CommonParameters (https://go.microsoft.com/fwlink/p/?LinkID=113216).
 
 ## INPUTS
 
@@ -315,4 +218,3 @@ To see the return types, which are also known as output types, that this cmdlet
 ## RELATED LINKS
 
 [Online Version](https://technet.microsoft.com/library/c9308fe6-3b61-4d99-a5f2-ef47abbc7656.aspx)
-