Added: Katee Falgoust - Date: 17.01.2022 00:20 - Views: 26461 - Clicks: 1076
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. 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.
Use the Add-DistributionGroupMember cmdlet to add a single recipient to distribution groups and mail-enabled security groups. To replace all members, use the Update-DistributionGroupMember cmdlet. For information about the parameter sets in the Syntax section below, see Exchange cmdlet syntax. You need to be ased 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 ased 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. The BypassSecurityGroupManagerCheck switch specifies whether to allow a user who isn't an owner of the group to modify or delete the group.
If you aren't defined in the ManagedBy property of the group, you need to use this switch in commands that modify or delete the group. To use this switch, your requires specific permissions based on the group type:. 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.
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, dc The Identity parameter specifies the group that you want to modify. You can use any value that uniquely identifies the group. For example:. The Member parameter specifies the recipient that you want to add to the group.
A member can be any mail-enabled recipient in your organization. You can use any value that uniquely identifies the recipient. Although it isn't required, it's a good idea to add only security principals for example, mailboxes and mail users with user s or other mail-enabled security groups to mail-enabled security groups. If you as permissions to a mail-enabled security group, any members that aren't security principals for example, mail contacts or distribution groups won't have the permissions ased. 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. To see the input types that this cmdlet accepts, see Cmdlet Input and Output Types. If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. To see the return types, which are also known as output types, that this cmdlet accepts, see Cmdlet Input and Output Types.
Role groups: You need to be a member of the Organization Management role group or have the Role Management role ased. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. This parameter is available only in on-premises Exchange. For example: Name Alias Distinguished name DN Canonical DN address GUID Although it isn't required, it's a good idea to add only security principals for example, mailboxes and mail users with user s or other mail-enabled security groups to mail-enabled security groups.
Is this helpful? Yes No. Any additional feedback?
Skip Submit. Submit and view feedback for This product This. View all feedback.Need someone for 2013
email: [email protected] - phone:(524) 791-8270 x 5352
MRSA and the Workplace