> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/powershell/it/powershell-commands/get-dsdeleteduser.md).

# Get-DSDeletedUser

Get-DSDeletedUser recupera gli utenti di Devolutions Server contrassegnati come eliminati ma non ancora rimossi definitivamente, con supporto per la paginazione.

### Sinossi

Ottiene gli utenti eliminati.

### Sintassi

#### \_\_AllParameterSets

```
Get-DSDeletedUser [-PageNumber <int>] [-PageSize <int>] [<CommonParameters>]
```

### Descrizione

Recupera gli utenti che sono stati contrassegnati come eliminati ma non rimossi definitivamente. Per impostazione predefinita, recupera i primi 10 000 risultati.

### Esempi

#### Esempio 1

```powershell
PS C:\> Get-DSDeletedUser
```

Ottiene tutti gli utenti eliminati.

#### Esempio 2

```powershell
PS C:\> Get-DSDeletedUser -PageNumber 2 -PageSize 50
```

Ottiene la seconda pagina con 50 utenti per pagina.

#### Esempio 3

```powershell
PS C:\> Get-DSDeletedUser | ForEach-Object { Restore-DSDeletedUser -ID $_.ID }
```

Ripristina tutti gli utenti eliminati.

#### Esempio 4

```powershell
PS C:\> $deletedUser = Get-DSDeletedUser | Where Name -EQ 'johndoe'
PS C:\> Remove-DSDeletedUser -ID $deletedUser.ID
```

Ottiene un utente eliminato tramite il nome utente e lo elimina definitivamente.

### Parametri

#### -PageNumber

Numero di pagina per i risultati paginati. Predefinito: 1

```yaml
Type: System.Int32
DefaultValue: ''
SupportsWildcards: false
Aliases: []
ParameterSets:
- Name: (All)
  Position: Named
  IsRequired: false
  ValueFromPipeline: false
  ValueFromPipelineByPropertyName: false
  ValueFromRemainingArguments: false
DontShow: false
AcceptedValues: []
HelpMessage: ''
```

#### -PageSize

Numero di risultati per pagina. Predefinito: 10000

```yaml
Type: System.Int32
DefaultValue: ''
SupportsWildcards: false
Aliases: []
ParameterSets:
- Name: (All)
  Position: Named
  IsRequired: false
  ValueFromPipeline: false
  ValueFromPipelineByPropertyName: false
  ValueFromRemainingArguments: false
DontShow: false
AcceptedValues: []
HelpMessage: ''
```

#### CommonParameters

Questo cmdlet supporta i parametri comuni: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutBuffer, -OutVariable, -PipelineVariable, -ProgressAction, -Verbose, -WarningAction e -WarningVariable. Per maggiori informazioni, veda [about\_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).

### Output

#### Devolutions.RemoteDesktopManager.Business.Models.UserListItem

### Note

Per maggiori informazioni, digiti "Get-Help Get-DSDeletedUser -detailed". Per informazioni tecniche, digiti "Get-Help Get-DSDeletedUser -full".


---

# 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.devolutions.net/powershell/it/powershell-commands/get-dsdeleteduser.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.