> 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/de/powershell-befehle/new-udcardmedia.md). # New-UDCardMedia New-UDCardMedia fügt ein Bild-, Video- oder Audioelement zum Medienbereich einer mit New-UDCard erstellten PowerShell Universal-Karte hinzu. ### Übersicht Erstellt ein neues Kartenmedium. ### Syntax ```powershell New-UDCardMedia [-Id ] [-Component ] [-Alt ] [-Height ] [-Image ] [-Title ] [-Sx ] [-Style ] [] New-UDCardMedia [-Id ] [-Component ] [-Alt ] [-Height ] [-Title ] [-Source ] [-Sx ] [-Style ] [] ``` ### Beschreibung Erstellt ein neues Kartenmedium. Wird mit New-UDCard verwendet. ### Parameter #### -Id Die ID der Komponente. Standardmäßig ist dies eine zufällige GUID. ``` Required? false Position? named Default value ([Guid]::NewGuid()).ToString() Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -Component Der Typ der Medienkomponente. Dies kann img, video oder audio sein. ``` Required? false Position? named Default value img Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -Alt Der Alt-Text für das Medium. ``` Required? false Position? named Default value Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -Height Die Höhe des Mediums. ``` Required? false Position? named Default value Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -Image Das anzuzeigende Bild. ``` Required? false Position? named Default value Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -Title Der Titel des Mediums. ``` Required? false Position? named Default value Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -Source Die Quelle des Mediums. ``` Required? false Position? named Default value Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -Sx ``` Required? false Position? named Default value Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -Style ``` Required? false Position? named Default value Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### Allgemeine Parameter Dieses Cmdlet unterstützt die allgemeinen Parameter: Verbose, Debug, ErrorAction, ErrorVariable, WarningAction, WarningVariable, OutBuffer, PipelineVariable und OutVariable. Weitere Informationen finden Sie unter [about\_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216). ### Ausgaben System.Collections.Hashtable ### Beispiele #### Beispiel 1 ```powershell $Media = New-UDCardMedia -Image 'https://mui.com/static/images/cards/paella.jpg' New-UDCard -Media $Media -Id 'card1' ``` --- # 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/de/powershell-befehle/new-udcardmedia.md?ask=&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.