Skip to content

Commit c0eb530

Browse files
committed
Update Update-Recipient.md
Issue #6670
1 parent c165dfa commit c0eb530

File tree

1 file changed

+11
-21
lines changed

1 file changed

+11
-21
lines changed

exchange/exchange-ps/exchange/Update-Recipient.md

Lines changed: 11 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -12,36 +12,29 @@ ms.reviewer:
1212
# Update-Recipient
1313

1414
## SYNOPSIS
15-
This cmdlet is available only in on-premises Exchange.
15+
This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
1616

17-
Use the Update-Recipient cmdlet to add Microsoft Exchange attributes to recipient objects created by the global address list (GAL) synchronization management agent in Microsoft Forefront Identity Manager (FIM) 2010. The recipient objects you modify using this cmdlet must reside on a server running Microsoft Exchange Server 2010 or later.
17+
Use the Update-Recipient cmdlet to add Exchange attributes to recipient objects.
1818

1919
For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
2020

2121
## SYNTAX
2222

2323
```
24-
Update-Recipient [-Identity] <RecipientIdParameter> [-Confirm] [-Credential <PSCredential>]
25-
[-DomainController <Fqdn>] [-WhatIf] [<CommonParameters>]
24+
Update-Recipient [-Identity] <RecipientIdParameter>
25+
[-Confirm]
26+
[-Credential <PSCredential>]
27+
[-DomainController <Fqdn>]
28+
[-WhatIf] [<CommonParameters>]
2629
```
2730

2831
## DESCRIPTION
29-
Because of mergers, acquisitions, or legal requirements, customers may need to deploy Exchange in a multiple Exchange forest topology. These deployments require the synchronization of recipient objects across disparate Active Directory forests.
30-
31-
Microsoft provides the GAL synchronization management agent for synchronizing recipient objects. The version of the GAL synchronization management agent included in Microsoft Identity Integration Server (MIIS) 2003 was designed to work with Exchange Server 2003 and relied on the Recipient Update Service. Because the Recipient Update Service is a deprecated feature and is no longer required, the new GAL synchronization management agent included in FIM 2010 is designed to function without the Recipient Update Service.
32-
33-
As part of the synchronization process, the FIM 2010 GAL synchronization management agent creates recipient objects in both Active Directory forests. After the recipients are created, the management agent uses the Update-Recipient cmdlet to add the attributes required by Microsoft Exchange to complete the provisioning of these recipients.
34-
35-
In Exchange, before you can run the Update-Recipient cmdlet to convert an Active Directory user object into an Exchange mailbox, you must stamp the user object with the following three mandatory Exchange attributes:
32+
In on-premises Exchange, before you can run the Update-Recipient cmdlet to convert an Active Directory user object into an Exchange mailbox, you must stamp the user object with the following three mandatory Exchange attributes:
3633

3734
- homeMDB
38-
3935
- mailNickname
40-
4136
- msExchHomeServerName
4237

43-
If you're using MIIS 2003, you must run various cmdlets to complete the provisioning process of the mail contacts created by the GAL synchronization management agent. The Update-Recipient cmdlet provides an alternate and more efficient method to do this. You can run the Update-Recipient cmdlet against the recipient objects created by the MIIS 2003 GAL synchronization management agent to complete the provisioning process.
44-
4538
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://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
4639

4740
## EXAMPLES
@@ -58,23 +51,18 @@ This example adds Exchange attributes to the mail contact that represents John S
5851
Get-MailContact -OrganizationalUnit "contoso.com/fabrikam.com Users" | Update-Recipient
5952
```
6053

61-
This example updates all contacts in a specific organizational unit (OU). This example assumes that recipients are synchronized between two forests, contoso.com and fabrikam.com, and all the synchronized recipients from the fabrikam.com domain are stored in a specific OU called fabrikam.com Users in the contoso.com domain.
54+
In on-premises Exchange, this example updates all contacts in a specific organizational unit (OU). This example assumes that recipients are synchronized between two forests, contoso.com and fabrikam.com, and all the synchronized recipients from the fabrikam.com domain are stored in a specific OU called fabrikam.com Users in the contoso.com domain.
6255

6356
## PARAMETERS
6457

6558
### -Identity
6659
The Identity parameter specifies the recipient that you want to update. You can use any value that uniquely identifies the recipient. For example:
6760

6861
- Name
69-
7062
- Alias
71-
7263
- Distinguished name (DN)
73-
7464
- Canonical DN
75-
7665
- Email address
77-
7866
- GUID
7967

8068
```yaml
@@ -129,6 +117,8 @@ Accept wildcard characters: False
129117
```
130118

131119
### -DomainController
120+
The parameter is available only in on-premises Exchange.
121+
132122
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.
133123

134124
```yaml

0 commit comments

Comments
 (0)