Tag : message

Alerts the user if FSLogix failed to attach a container.

This is an example of how the 'Send Slack message on Session condition' script can be used in a Trigger follow up action.
Configure the defaults for your Slack environment and set the script as a follow up action on User Logon on a machine.
NOTE: In Settings the following changes have been made (compared to the 'Send Slack message' script)
Action Assigned to: Session
Execution Context: User Session
Security Context: Default (Session's User)

Sends a message to Slack using an Incoming Webhook with an option to include a clickable button with a URI link. Customize the Message input to use this as an Automated Action for alerts on session metrics.
If you want to include a clickable button with your message the ButtonExplanation, ButtonText and ButtonURI must be provided. If any of these is missing the script will return an error.
Useful for Triggered scripts, fill the title and message with data from the console as required.
This script requires a webhook to be configured in your Slack site. See the link on how to do this: https://slack.com/help/articles/115005265063-Incoming-webhooks-for-Slack

Sends a message to Slack using an Incoming Webhook with an option to include a clickable button with a URI link. Customize the Message input to use this as an Automated Action for alerts on machine metrics.
If you want to include a clickable button with your message the ButtonExplanation, ButtonText and ButtonURI must be provided. If any of these is missing the script will return an error.
Useful for Triggered scripts, fill the title and message with data from the console as required.
This script requires a webhook to be configured in your Slack site. See the link on how to do this: https://slack.com/help/articles/115005265063-Incoming-webhooks-for-Slack

Sends a message to Slack using an Incoming Webhook with an option to include a clickable button with a URI link. Customize the Message input to use this as an Automated Action for alerts on session metrics.
If you want to include a clickable button with your message the ButtonExplanation, ButtonText and ButtonURI must be provided. If any of these is missing the script will return an error.
Useful for Triggered scripts, fill the title and message with data from the console as required.
This script requires a webhook to be configured in your Slack site. See the link on how to do this: https://slack.com/help/articles/115005265063-Incoming-webhooks-for-Slack

Sends a message to Teams using an Incoming Webhook, with an option to include a clickable button with a URI link.Customize the Message input to use this as an Automated Action for alerts on machine metrics.
If you want to include a clickable button with your message, ButtonText and ButtonURI must be provided. If either of these is missing the script will return an error.
Useful for Triggered scripts, fill the Title and message with data from the console as required.
This script requires a webhook to be configured in your Teams site. See the link on how to do this: https://docs.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/how-to/add-incoming-webhook

Sends a message to Teams using an Incoming Webhook, with an option to include a clickable button with a URI link.Customize the Message input to use this as an Automated Action for alerts on session metrics.
If you want to include a clickable button with your message, ButtonText and ButtonURI must be provided. If either of these is missing the script will return an error.
Useful for Triggered scripts, fill the Title and message with data from the console as required.
This script requires a webhook to be configured in your Teams site. See the link on how to do this: https://docs.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/how-to/add-incoming-webhook

Example script for an automated action when CPU threshold is exceeded using the 'Send Teams message on machine condition' script.When configured as an automated action triggered from high CPU use a message will be posted in the configured Teams environment, with a button that can be clicked to open the console in the machine location.

Sends a message to Teams using an Incoming Webhook, with an option to include a clickable button with a URI link.Customize the Message input to use this as an Automated Action for alerts on machine metrics.
If you want to include a clickable button with your message, ButtonText and ButtonURI must be provided. If either of these is missing the script will return an error.
Useful for Triggered scripts, fill the Title and message with data from the console as required.
This script requires a webhook to be configured in your Teams site. See the link on how to do this: https://docs.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/how-to/add-incoming-webhook

Displays a Toast notification on the users'desktop (Windows 10/Server 2016 or higher only). Designed to be used as an automated action with client metrics requiring ControlUp 8.5 or higher.
Take a copy of the script and either use as a regular SBA, or set the defaults in the Param() block so it can be used in an automated action. If you are using the standard parameters setting default values for these will also allow use in an automated action.

Use WPF to display a modal dialogue in a user's session with a message, optional title, and solid colour background.
Take a copy of the script and either add parameters to use as a regular SBA, or set the defaults in the Param() block so it can be used in an automated action. If you have created parameters setting default values for these will also allow use in an automated action.
Unless -showForSeconds is specified and the value is less than the script timeout, it will timeout and show an eror but if no other errors are shown, the message will have been displayed

This is an example of how the 'Show message dialogue' script can be tailored for a specific use case.
_ClientMetric1 has been set to the Memory (Working Set) from ControlUp and the message includes this metric.
Use WPF to display a modal dialogue in a user's session with a message, optional title, and solid colour background.
Take a copy of the script and either add parameters to use as a regular SBA, or set the defaults in the Param() block so it can be used in an automated action. If you have created parameters, setting default values for these will also allow use in an automated action.
Unless -showForSeconds is specified and the value is less than the script timeout, it will timeout and show an eror but if no other errors are shown, the message will have been displayed

Envoie des messages au(x) utilisateur(s) Horizon sélectionné(s). Ce script peut être utilisé pour envoyer des messages à une session d'utilisateur unique à l'aide des API SOAP d'Horizon. Il peut également être utilisé comme action automatisée avec un message et un niveau de gravité fixes. Les niveaux de gravité suivants sont autorisés INFO, AVERTISSEMENT, ERREUR

Ce script nécessite l'installation de VMWare PowerCLI sur la machine qui exécute le script.
PowerCLI peut être installé via PowerShell (version 5 ou supérieure de PowerShell requise) en exécutant la commande "Install-Module VMWare.PowerCLI -Force -AllowCLobber -Scope AllUsers" ou en utilisant le script "Install VMware PowerCLI".
Si vous obtenez des erreurs TLS/SSL, utilisez la commande Set-PowerCLIConfiguration -InvalidCertificateAction ignore.
ou Set-PowerCLIConfiguration -InvalidCertificateAction warn
Pour se débarrasser de l'avertissement du CEIP, utilisez Set-PowerCLIConfiguration -ParticipateInCeip $true.
ou Set-PowerCLIConfiguration -ParticipateInCeip $false
Les informations d'identification peuvent être définies à l'aide du script "Create credentials for Horizon View scripts" (Créer des informations d'identification pour les scripts Horizon View).