> 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/v2.1/help-and-support/powershellmodule/get-amslocaladminpassword.md).

# Get-AmsLocalAdminPassword

## SYNOPSIS

Gets the local admin password of the specified device

## SYNTAX

### Get password by computer name (Default)

```
Get-AmsLocalAdminPassword [-ComputerName] <String> [<CommonParameters>]
```

### Get password by device authority information

```
Get-AmsLocalAdminPassword -AuthorityDeviceId <String> -AuthorityId <String> -AuthorityType <AuthorityType>
 [<CommonParameters>]
```

## DESCRIPTION

This cmdlet gets the local admin password of the specified computer.

Note, this cmdlet is not subject to the authorization rules and audit events. Only AMS administrators can call this cmdlet.

## EXAMPLES

### Example 1

```powershell
PS C:\> Get-AmsLocalAdminPassword -ComputerName "PC1"
```

Returns the local admin password for the computer named `PC1`

### Example 2

```powershell
PS C:\> Get-AmsLocalAdminPassword -ComputerName "DEV\SERVER1"
```

Returns the local admin password for the Active Dircetory computer named `SERVER1` int he `DEV` domain

### Example 3

```powershell
PS C:\> Get-AmsDevice -Name "macos12" |  Get-AmsLocalAdminPassword
```

Returns the local admin password for the AMS-managed computer named `macos12`

## PARAMETERS

### -ComputerName

The name of the computer object. This can be a simple name like `PC1` or a fully qualified name like `DOMAIN\PC1`

```yaml
Type: String
Parameter Sets: Get password by computer name
Aliases:

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

### -AuthorityDeviceId

The ID of the device

```yaml
Type: String
Parameter Sets: Get password by device authority information
Aliases:

Required: True
Position: Named
Default value: None
Accept pipeline input: True (ByPropertyName)
Accept wildcard characters: False
```

### -AuthorityId

The device's Authority

```yaml
Type: String
Parameter Sets: Get password by device authority information
Aliases:

Required: True
Position: Named
Default value: None
Accept pipeline input: True (ByPropertyName)
Accept wildcard characters: False
```

### -AuthorityType

The authority type

```yaml
Type: AuthorityType
Parameter Sets: Get password by device authority information
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

### None

## OUTPUTS

### Lithnet.AccessManager.PowerShell.PasswordPSObject

## NOTES

## 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.lithnet.io/ams/v2.1/help-and-support/powershellmodule/get-amslocaladminpassword.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.