> 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/mim-sync-service/usage/cmdlet-reference/get-runprofiles.md).

# Get-RunProfiles

## Synopsis

Gets a management agent's run profiles

## Syntax

```
Get-RunProfiles [-MA] <string> [<CommonParameters>]
```

## Description

The [Get-RunProfiles](/mim-sync-service/usage/cmdlet-reference/get-runprofiles.md) cmdlet returns a list of run profiles for the management agent

## Parameters

#### -MA \<string>

The management agent to get the run profiles from

|                             |       |
| --------------------------- | ----- |
| Required?                   | true  |
| Position?                   | 1     |
| Default value               |       |
| Accept pipeline input?      | false |
| Accept wildcard characters? | false |

#### \<CommonParameters>

This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, ErrorVariable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see [about CommonParameters](http://go.microsoft.com/fwlink/?LinkID=113216).

## Examples

### Get the run profiles from the specified management agent

```
PS C:\> Get-RunProfiles ADMA
ID                   : 135bd4d5-ccb2-4b2a-850c-538be9b648af
Name                 : DI
CreationTime         : 4/03/2016 5:51:33 PM
LastModificationTime : 15/04/2016 1:00:07 PM
Version              : 3
RunSteps             : {Delta import}

ID                   : c4f13355-4c78-4a8b-8148-3b4918fcf7d0
Name                 : DIDS
CreationTime         : 4/03/2016 5:51:33 PM
LastModificationTime : 15/04/2016 1:00:07 PM
Version              : 3
RunSteps             : {Delta import, Delta synchronization}

ID                   : cd8a30fc-2aa2-456b-848e-9b3e2c6c6fc1
Name                 : DIDSC
CreationTime         : 17/04/2016 8:46:02 AM
LastModificationTime : 17/04/2016 8:46:02 AM
Version              : 1
RunSteps             : {Delta import and delta synchronization}

ID                   : 9ae6ce0e-8226-42b9-9518-c67917049237
Name                 : DIFS
CreationTime         : 4/03/2016 5:51:33 PM
LastModificationTime : 15/04/2016 1:00:07 PM
Version              : 3
RunSteps             : {Delta import, Full synchronization}

ID                   : 7b78f9c6-f161-446b-be42-7e721c309c71
Name                 : DS
CreationTime         : 4/03/2016 5:51:33 PM
LastModificationTime : 15/04/2016 1:00:07 PM
Version              : 3
RunSteps             : {Delta synchronization}

ID                   : a5e799f3-37e7-4598-823e-fb78bd8f5314
Name                 : E1
CreationTime         : 4/03/2016 5:51:33 PM
LastModificationTime : 15/04/2016 1:00:07 PM
Version              : 3
RunSteps             : {Export}
```


---

# 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/mim-sync-service/usage/cmdlet-reference/get-runprofiles.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.