|
| 1 | +--- |
| 2 | +applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 |
| 3 | +schema: 2.0.0 |
| 4 | +--- |
| 5 | + |
| 6 | +# Enable-AddressListPaging |
| 7 | + |
| 8 | +## SYNOPSIS |
| 9 | +This cmdlet is available only in on-premises Exchange. |
| 10 | + |
| 11 | +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. |
| 12 | + |
| 13 | +For information about the parameter sets in the Syntax section below, see Exchange cmdlet syntax (https://technet.microsoft.com/library/bb123552.aspx). |
| 14 | + |
| 15 | +## SYNTAX |
| 16 | + |
| 17 | +``` |
| 18 | +Enable-AddressListPaging [-Confirm] [-DomainController <Fqdn>] [-WhatIf] [<CommonParameters>] |
| 19 | +``` |
| 20 | + |
| 21 | +## DESCRIPTION |
| 22 | +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. |
| 23 | + |
| 24 | +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). |
| 25 | + |
| 26 | +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. |
| 27 | + |
| 28 | +## EXAMPLES |
| 29 | + |
| 30 | +### Example 1 |
| 31 | +``` |
| 32 | +Enable-AddressListPaging |
| 33 | +``` |
| 34 | + |
| 35 | +This example enables virtual list view for your organization. |
| 36 | + |
| 37 | +## PARAMETERS |
| 38 | + |
| 39 | +### -Confirm |
| 40 | +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. |
| 41 | + |
| 42 | +- 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. |
| 43 | + |
| 44 | +- 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. |
| 45 | + |
| 46 | +```yaml |
| 47 | +Type: SwitchParameter |
| 48 | +Parameter Sets: (All) |
| 49 | +Aliases: |
| 50 | +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 |
| 51 | + |
| 52 | +Required: False |
| 53 | +Position: Named |
| 54 | +Default value: None |
| 55 | +Accept pipeline input: False |
| 56 | +Accept wildcard characters: False |
| 57 | +``` |
| 58 | +
|
| 59 | +### -DomainController |
| 60 | +The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. |
| 61 | +
|
| 62 | +```yaml |
| 63 | +Type: Fqdn |
| 64 | +Parameter Sets: (All) |
| 65 | +Aliases: |
| 66 | +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 |
| 67 | + |
| 68 | +Required: False |
| 69 | +Position: Named |
| 70 | +Default value: None |
| 71 | +Accept pipeline input: False |
| 72 | +Accept wildcard characters: False |
| 73 | +``` |
| 74 | +
|
| 75 | +### -WhatIf |
| 76 | +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. |
| 77 | +
|
| 78 | +```yaml |
| 79 | +Type: SwitchParameter |
| 80 | +Parameter Sets: (All) |
| 81 | +Aliases: |
| 82 | +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 |
| 83 | + |
| 84 | +Required: False |
| 85 | +Position: Named |
| 86 | +Default value: None |
| 87 | +Accept pipeline input: False |
| 88 | +Accept wildcard characters: False |
| 89 | +``` |
| 90 | +
|
| 91 | +### CommonParameters |
| 92 | +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). |
| 93 | +
|
| 94 | +## INPUTS |
| 95 | +
|
| 96 | +### |
| 97 | +To see the input types that this cmdlet accepts, see Cmdlet Input and Output Types (https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. |
| 98 | +
|
| 99 | +## OUTPUTS |
| 100 | +
|
| 101 | +### |
| 102 | +To see the return types, which are also known as output types, that this cmdlet accepts, see Cmdlet Input and Output Types (https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Output Type field is blank, the cmdlet doesn't return data. |
| 103 | +
|
| 104 | +## NOTES |
| 105 | +
|
| 106 | +## RELATED LINKS |
| 107 | +
|
| 108 | +[Online Version](https://technet.microsoft.com/library/d20e96a9-8742-4f6b-8acc-6433e79a23db.aspx) |
0 commit comments