> For the complete documentation index, see [llms.txt](https://docs.lithnet.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lithnet.io/ams/v3.0/help-and-support/powershellmodule/remove-amsgroupmember.md).

# Remove-AmsGroupMember

## SYNOPSIS

Removes one or more members of an AMS group

## SYNTAX

```
Remove-AmsGroupMember -Id <String> [-Devices <Object[]>] [-Force] [<CommonParameters>]
```

## DESCRIPTION

This cmdlet removes one or more members from a group

## EXAMPLES

### Example 1

```powershell
PS C:\> Remove-AmsGroupMember -Id '0c1ecad4-3581-42c5-8501-22f13559e418' -Devices '0b5cffd6-d22f-49d7-b5e2-4631997a7416'
```

Removes a device by its ID from a group by its ID

### Example 2

```powershell
PS C:\> Remove-AmsGroupMember -Id '0c1ecad4-3581-42c5-8501-22f13559e418'
```

Removes all members of the group

### Example 3

```powershell
PS C:\> Get-AmsGroup -Name "My group" | Remove-AmsGroupMember -Devices '0b5cffd6-d22f-49d7-b5e2-4631997a7416'
```

Gets a group by name, and removes a specific member by its known ID

### Example 4

```powershell
PS C:\> Get-AmsGroup -Name "My group" | Remove-AmsGroupMember -Devices (Get-AmsDevice -Name 'PC1')
```

Gets a group by name, and removes a specific member by retrieving the object by its name

## PARAMETERS

### -Devices

A list of IDs or device objects to remove from the group

```yaml
Type: Object[]
Parameter Sets: (All)
Aliases:

Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### -Force

When removing all members from the group, this parameter indicates that the members should be removed without any confirmation prompt

```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:

Required: False
Position: Named
Default value: False
Accept pipeline input: False
Accept wildcard characters: False
```

### -Id

The ID of the group

```yaml
Type: String
Parameter Sets: (All)
Aliases:

Required: True
Position: Named
Default value: None
Accept pipeline input: True (ByPropertyName)
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](http://go.microsoft.com/fwlink/?LinkID=113216).

## INPUTS

### System.String

## OUTPUTS

### System.Void

## NOTES

Use of this cmdlet requires an Enterprise Edition license.

## RELATED LINKS


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.lithnet.io/ams/v3.0/help-and-support/powershellmodule/remove-amsgroupmember.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.