> 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/powershell-kommandoer/add-psucomputertag.md). # Add-PSUComputerTag Add-PSUComputerTag føjer et mærke med navn og værdi til en registreret PowerShell Universal-computer og målretter den efter Id eller via pipelinen. ## Synopsis Føjer et mærke til en registreret PowerShell Universal-computer. ## Syntaks ### Id ``` Add-PSUComputerTag [-Id] [-Name ] [-Value ] [-ComputerName ] [-AppToken ] [-Credential ] [-UseDefaultCredentials] [-Integrated] [-TrustCertificate] [-Cookies] [] ``` ### Computer ``` Add-PSUComputerTag [-Computer] [-Name ] [-Value ] [-ComputerName ] [-AppToken ] [-Credential ] [-UseDefaultCredentials] [-Integrated] [-TrustCertificate] [-Cookies] [] ``` ## Beskrivelse Tilføjer en ny mærkepost til en eksisterende computer og skriver det oprettede mærke til pipelinen. De kan målrette computeren via Id eller sende et eksisterende computerobjekt gennem pipelinen. ## Eksempler ### Eksempel 1 ```powershell PS C:\> Add-PSUComputerTag -Id 42 -Name Environment -Value Production ``` Tilføjer mærket Environment=Production til computeren med Id 42. ## Parametre ### -AppToken Angiver det app-token, der skal bruges ved godkendelse til PowerShell Universal Management API. ```yaml Type: String Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Computer Angiver den computer, der skal målrettes. ```yaml Type: Computer Parameter Sets: Computer Aliases: Required: True Position: 0 Default value: None Accept pipeline input: True (ByValue) Accept wildcard characters: False ``` ### -ComputerName Angiver URL'en eller værtsnavnet for den ønskede PowerShell Universal-instans. Rene værtsnavne normaliseres til en `http://:5000`-URL. ```yaml Type: String Parameter Sets: (All) Aliases: Uri Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Cookies Genbruger og bevarer godkendelsescookies for den aktuelle PowerShell-session. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Credential Angiver de legitimationsoplysninger, der skal bruges til Basic-godkendelse mod PowerShell Universal Management API. ```yaml Type: PSCredential Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Id Angiver det numeriske id for ressourcen. ```yaml Type: Int64 Parameter Sets: Id Aliases: Required: True Position: 0 Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Integrated Bruger den integrerede administrationsklient i processen, når cmdlet'en køres inde i PowerShell Universal. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Name Angiver navnet på ressourcen. ```yaml Type: String Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -TrustCertificate Tillader forbindelser til servere med TLS-certifikater, der ikke er tillid til. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -UseDefaultCredentials Bruger de aktuelle Windows-legitimationsoplysninger ved godkendelse til Management API. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Value Angiver den værdi, der skal gemmes eller tildeles. ```yaml Type: String Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### CommonParameters Denne cmdlet understøtter de fælles parametre: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutBuffer, -OutVariable, -PipelineVariable, -Verbose, -WarningAction, -WarningVariable og -ProgressAction. Se [about\_CommonParameters](http://go.microsoft.com/fwlink/?LinkID=113216) for at få flere oplysninger. ## Input ### PowerShellUniversal.Computer ## Output ### System.Object ## Noter ## Relaterede links ## Tilladelser Adgangstokenet kræver `platform.computers/update` for at køre denne cmdlet fra en fjerncomputer. --- # 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/powershell-kommandoer/add-psucomputertag.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.