> 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-universal/it/comandi-powershell/start-psuserver.md).

# Start-PSUServer

Start-PSUServer individua, configura e avvia l'eseguibile del server PowerShell Universal come nuovo processo in background.

## SINOSSI

Avvia il server PowerShell Universal.

## SINTASSI

### Service (predefinito)

```
Start-PSUServer [<CommonParameters>]
```

### Path

```
Start-PSUServer [[-ExecutablePath] <String>] [[-ListenAddress] <String>] [-Port <Int32>]
 [-Configuration <ScriptBlock>] [<CommonParameters>]
```

## DESCRIZIONE

Avvia il server PowerShell Universal. Questo cmdlet esegue l'individuazione e la configurazione dell'eseguibile Universal.Server. Utilizza Start-Process per avviare il server una volta completata la configurazione. Questo cmdlet richiede di poter trovare l'eseguibile Universal.Server. È possibile usare Install-PSUServer per scaricare i file binari corretti per il proprio sistema.

## ESEMPI

### Esempio 1

```
PS C:\> Start-PSUServer -Port 8080
```

Avvia un server PowerShell Universal sulla porta 8080

### Esempio 2

```
PS C:\> Start-PSUServer -Port 8080 -Configuration {
    New-PSUEndpoint -Url '/test' -Method 'GET' -Endpoint {
        "Hi"
    }
}
```

Avvia un server PowerShell Universal sulla porta 8080 e utilizza la configurazione a file singolo per impostare un nuovo endpoint in ascolto su '/test'

### Esempio 3

```
PS C:\> $Env:Data__RepositoryPath = "C:\repo" 
PS C:\> Start-PSUServer -Port 8080
```

Imposta un percorso di repository alternativo e avvia il server PowerShell Universal.

## PARAMETRI

### -ExecutablePath

Il percorso dell'eseguibile Universal.Server. Il valore predefinito è $Env:ProgramData\Universal.Server. Se non viene trovato in questa posizione, Start-PSUServer cercherà anche in $ENV:PATH

```yaml
Type: String
Parameter Sets: Path
Aliases:

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

### -ListenAddress

L'indirizzo su cui restare in ascolto. Ad esempio: http\://\*:4000

```yaml
Type: String
Parameter Sets: Path
Aliases:

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

### -Configuration

Un blocco di script di configurazione. Abilita la configurazione a file singolo.

```yaml
Type: ScriptBlock
Parameter Sets: Path
Aliases:

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

### -Port

Una porta su cui restare in ascolto.

```yaml
Type: Int32
Parameter Sets: Path
Aliases:

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

### CommonParameters

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

## INPUT

### Nessuno

## OUTPUT

### System.Object

## NOTE

## LINK CORRELATI

[Install-PSUServer](/powershell-universal/it/comandi-powershell/install-psuserver.md)


---

# 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-universal/it/comandi-powershell/start-psuserver.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.