> 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/fr/commandes-powershell/add-psucomputertag.md). # Add-PSUComputerTag Add-PSUComputerTag ajoute une étiquette composée d'un nom et d'une valeur à un ordinateur PowerShell Universal enregistré, en le ciblant par Id ou par le pipeline. ## SYNOPSIS Ajoute une étiquette à un ordinateur PowerShell Universal enregistré. ## SYNTAXE ### Id ``` Add-PSUComputerTag [-Id] [-Name ] [-Value ] [-ComputerName ] [-AppToken ] [-Credential ] [-UseDefaultCredentials] [-Integrated] [-TrustCertificate] [-Cookies] [] ``` ### Ordinateur ``` Add-PSUComputerTag [-Computer] [-Name ] [-Value ] [-ComputerName ] [-AppToken ] [-Credential ] [-UseDefaultCredentials] [-Integrated] [-TrustCertificate] [-Cookies] [] ``` ## DESCRIPTION Ajoute une nouvelle entrée d'étiquette à un ordinateur existant et écrit l'étiquette créée dans le pipeline. Vous pouvez cibler l'ordinateur par Id ou transmettre un objet ordinateur existant via le pipeline. ## EXEMPLES ### Exemple 1 ```powershell PS C:\> Add-PSUComputerTag -Id 42 -Name Environment -Value Production ``` Ajoute l'étiquette Environment=Production à l'ordinateur ayant l'Id 42. ## PARAMÈTRES ### -AppToken Spécifie le jeton d'appli à utiliser lors de l'authentification auprès de l'API de gestion PowerShell Universal. ```yaml Type: String Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Computer Spécifie l'ordinateur à cibler. ```yaml Type: Computer Parameter Sets: Computer Aliases: Required: True Position: 0 Default value: None Accept pipeline input: True (ByValue) Accept wildcard characters: False ``` ### -ComputerName Spécifie l'URL ou le nom d'hôte de l'instance PowerShell Universal cible. Les noms d'hôte seuls sont normalisés en une URL `http://:5000`. ```yaml Type: String Parameter Sets: (All) Aliases: Uri Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Cookies Réutilise et conserve les témoins d'authentification pour la session PowerShell en cours. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Credential Spécifie les identifiants à utiliser pour l'authentification de base auprès de l'API de gestion PowerShell Universal. ```yaml Type: PSCredential Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Id Spécifie l'Id numérique de la ressource. ```yaml Type: Int64 Parameter Sets: Id Aliases: Required: True Position: 0 Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Integrated Utilise le client de gestion intégré en cours de processus lorsque l'applet de commande s'exécute dans 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 Spécifie le nom de la ressource. ```yaml Type: String Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -TrustCertificate Permet les connexions aux serveurs avec des certificats TLS non approuvés. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -UseDefaultCredentials Utilise les identifiants Windows actuels lors de l'authentification auprès de l'API de gestion. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Value Spécifie la valeur à stocker ou à assigner. ```yaml Type: String Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### CommonParameters Cette applet de commande prend en charge les paramètres communs : -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutBuffer, -OutVariable, -PipelineVariable, -Verbose, -WarningAction, -WarningVariable et -ProgressAction. Pour plus d'informations, consultez [about\_CommonParameters](http://go.microsoft.com/fwlink/?LinkID=113216). ## ENTRÉES ### PowerShellUniversal.Computer ## SORTIES ### System.Object ## NOTES ## LIENS CONNEXES --- # 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/fr/commandes-powershell/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.