> 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/es/comandos-de-powershell/add-psucomputertag.md). # Add-PSUComputerTag Add-PSUComputerTag añade una etiqueta con nombre y valor a un ordenador registrado de PowerShell Universal, indicándolo por Id o a través de la canalización. ## SINOPSIS Añade una etiqueta a un ordenador registrado de PowerShell Universal. ## SINTAXIS ### 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] [] ``` ## DESCRIPCIÓN Añade una nueva entrada de etiqueta a un ordenador existente y escribe la etiqueta creada en la canalización. Puede seleccionar el ordenador por Id o pasar un objeto de ordenador existente a través de la canalización. ## EJEMPLOS ### Ejemplo 1 ```powershell PS C:\> Add-PSUComputerTag -Id 42 -Name Environment -Value Production ``` Añade la etiqueta Environment=Production al ordenador con Id 42. ## PARÁMETROS ### -AppToken Especifica el token de aplicación que se utilizará al autenticarse en la API de gestión de 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 Especifica el ordenador de destino. ```yaml Type: Computer Parameter Sets: Computer Aliases: Required: True Position: 0 Default value: None Accept pipeline input: True (ByValue) Accept wildcard characters: False ``` ### -ComputerName Especifica la URL o el nombre de host de la instancia de PowerShell Universal de destino. Los nombres de host simples se normalizan a una 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 Reutiliza y conserva las cookies de autenticación para la sesión actual de PowerShell. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Credential Especifica las credenciales que se utilizarán para la autenticación básica en la API de gestión de 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 Especifica el Id numérico del recurso. ```yaml Type: Int64 Parameter Sets: Id Aliases: Required: True Position: 0 Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Integrated Utiliza el cliente de gestión integrado en proceso cuando el cmdlet se ejecuta dentro de 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 Especifica el nombre del recurso. ```yaml Type: String Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -TrustCertificate Permite conexiones a servidores con certificados TLS no confiables. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -UseDefaultCredentials Utiliza las credenciales actuales de Windows al autenticarse en la API de gestión. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Value Especifica el valor que se almacenará o asignará. ```yaml Type: String Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### CommonParameters Este cmdlet admite los parámetros comunes: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutBuffer, -OutVariable, -PipelineVariable, -Verbose, -WarningAction, -WarningVariable y -ProgressAction. Para más información, consulte [about\_CommonParameters](http://go.microsoft.com/fwlink/?LinkID=113216). ## ENTRADAS ### PowerShellUniversal.Computer ## SALIDAS ### System.Object ## NOTAS ## ENLACES RELACIONADOS --- # 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/es/comandos-de-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.