> 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/de/powershell-commands/start-rdmprofiler.md).

# Start-RDMProfiler

Start-RDMProfiler startet eine Profiling-Sitzung von Remote Desktop Manager und ermöglicht es Ihnen, die Profiler-Ebene und den Ausgabepfad des Protokolls festzulegen.

### Syntax

#### \_\_AllParameterSets

```
Start-RDMProfiler [-Level <ProfilerLevel[]>] [-Path <string>] [-NoClobber]
 [-ForcePromptAnswer <DialogResult[]>] [<CommonParameters>]
```

### Parameter

#### -ForcePromptAnswer

Schalter, der mit Vorsicht zu verwenden ist. Er beantwortet automatisch Eingabeaufforderungen mit den Fragen ja/nein, ja/nein/abbrechen oder ok/abbrechen. Bei mehreren Eingabeaufforderungen können mehrere Werte an diesen Parameter übergeben werden. Hier sind die akzeptierten Werte:

* Yes: Die Eingabeaufforderung annehmen. Deckt die Werte OK und Automatic ab.
* No: Die Eingabeaufforderung ja/nein/abbrechen ablehnen. "Cancel" ist die Ausweichoption, wenn es keine Option "No" gibt.
* Cancel: Die Eingabeaufforderung ja/nein/abbrechen abbrechen. "No" ist die Ausweichoption, wenn es keine Option "Cancel" gibt.

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

#### -Level

Legt fest, was der Profiler anzeigt. Standardmäßig wird alles angezeigt.

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

#### -NoClobber

Verhindert das Überschreiben einer vorhandenen Datei

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

#### -Path

Speichert den Profiler-Text in der angegebenen Textdatei

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

#### CommonParameters

Dieses Cmdlet unterstützt die allgemeinen Parameter: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutBuffer, -OutVariable, -PipelineVariable, -ProgressAction, -Verbose, -WarningAction und -WarningVariable. Weitere Informationen finden Sie unter [about\_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).

### Hinweise

Weitere Informationen erhalten Sie durch Eingabe von "Get-Help Start-RDMProfiler -detailed". Für technische Informationen geben Sie "Get-Help Start-RDMProfiler -full" ein.


---

# 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/de/powershell-commands/start-rdmprofiler.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.