> 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/da/automatisering/schedules/run-schedules-with-powershell.md).

# Kør tidsplaner med PowerShell

Brug Invoke-PSUSchedule til at udløse en eksisterende tidsplan i PowerShell Universal med det samme ved hjælp af den samme kørselssti som admin console.

Brug `Invoke-PSUSchedule` til at udløse en eksisterende tidsplan med det samme. Den bruger den samme udførelsessti som admin console, så tidsplanen beholder sit konfigurerede script, miljø, sin legitimationsoplysning, sin målcomputer og andre kørselsindstillinger.

Kalderen kræver udførelsestilladelse til **Automation Schedules**.

## Vælg en tidsplan

Udløs en tidsplan efter Id:

```powershell
Invoke-PSUSchedule -Id 10
```

Udløs en tidsplan efter navn:

```powershell
Invoke-PSUSchedule -Name 'Nightly maintenance'
```

De kan også pipe et tidsplanobjekt:

```powershell
Get-PSUSchedule -Name 'Nightly maintenance' | Invoke-PSUSchedule
```

`Invoke-PSUSchedule` starter en ny kørsel; den ændrer ikke tidsplansdefinitionen eller dens næste planlagte udførelse.


---

# 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/da/automatisering/schedules/run-schedules-with-powershell.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.