Script library

Retrieves the password for the selected machine protected by the Local Administrator Password Solution, generates an RDP file then connects to the machine.

Performs a test of all the technical requirements for HDX content redirection, which can potentially save bandwidth and CPU. The script's output provides the test results along with recommendations on components that need to be enabled or upgraded for content redirection to work.

Run on a Delivery Controller or where the CVAD PowerShell snapins are available, e.g. Studio is installed or on a machine with the DaaS Remote PowerShell SDK (for Cloud). User running the script for on-prem must have sufficient permission to change the enabled state of the selected delivery groups. For Cloud, CU stored credentials must have previously been saved for the local user running the script.

To use this script as an automated action where parameters cannot be passed, copy the script and set the $disable parameter in the Param() block at the top of the script to "true" or "false" depending on whether you are disabling or enabling delivery groups respectively.

The Cloud Customer Id or Delivery Controller is an optional argument which can be used when there are more than 1 credential file for the user running the script so that the correct Cloud customer can be chosen. When used on-prem, the parameter is used to tell the script what delivery controller to connect to when the script is not run on a DDC.

Run on a Delivery Controller or where the CVAD PowerShell snapins are available, e.g. Studio is installed. User running the script must have sufficient permission to chage the enabled state of the selected delivery groups

Adds or Removes Windows Features from Server or Desktop operating systems.

Show how recently (in number of days) delivery groups have had sessions launched from them, by checking the last used property for each machine in a delivery group.
Specify the minimum number of days last launched to show only delivery groups which have not had sessions launched within that number of days and optionally disable them. Specify 0 days to show all delivery groups.

Run on a Delivery Controller or where the CVAD PowerShell snapins are available, e.g. Studio is installed.

ControlUp binaries by default generate minimum logging to prevent disk exhaustion.
To enable DEBUG logs, deploying the log4net file in the same directory as a ControlUp process initiates the capture.
This script will initiate the logging process and allows placing of the log file in a custom location.
If log duration is greater than zero, the log capture with stop at the end of the period.

Support Mode changes the format of the lines in the resultant log file to make it easier to merge multiple log files, where required.

Resets the password assigned to the Local Administrator Password Solution account

Get's the local administrator password for the selected machines protected by the Local Administrator Password Solution (LAPS)

Enables Firewall Auditing Events and then tails the event log remotely. The tailing of events for this script is closer to realtime then the text log.

The script displays VDI machines and RDS hosts that are not running on the same Golden Image and Snapshot that are configured in the Desktop Pool settings. It offers the option to delete VDI machines with or without forcing the user to logoff. Uses the Horizon PowerCLI api's to pull all snapshot information for Horizon Linked Clones and Instant Clones Desktops pools and RDS farms.
The script also uses the Horizon api's to poll the Cloud Pod status of the system and connects to other pods if Cloud Pod has been enabled.

This Script Requires a Horizon Credential file for the user running the scipt. This can be created using the Create credentials for Horizon scripts Script Action.
Requires Horizon 7.5 or later
This script requires VMware PowerCLI to be installed on the machine running the script. PowerCLI can be installed using the Install and configure VMware PowerCLI Script Action

Opens Windows Admin Center to the server manager for the selected machine

Uses the Horizon REST api's to pull all Error, Warning and Audit_Fail events from the Horizon Event database for all pods. If there is no cloud pod setup it will only process the local pod. After pulling the events it will translate the id's for the various objects to names to show the proper names where needed.

Output is displayed in the console but also saved to a default location of c:windowstempCU_Horizon_error_log.csv

This action should be executed against a Horizon endpoint machine (one which has the HZ Primary Connection Server column populated in ControlUp Console). The script uses the target machine to determine the connection server address, and is executed on the machine running ControlUp Console.
This script requires Horizon Credentials to be set for the account running the scipt on the target machine, these need to be created using the 'Create credentials for Horizon scripts' Script Action

Query the selected delivery controller via OData to retrieve connection failure details for a specific user, or all users, within a specified number of days ago

Retrieve event id 7470 instances from the security event logs to gives details of the user account, the time and location of the lock out. Can filter a specified number of days back and/or a specific user name

This AVD Script Based Action prepares the machine with the required PowerShell modules to run the AVD script based actions
README: https://support.controlup.com/hc/en-us/articles/360011378518

Test connectivity from the ControlUp console machine to the ControlUp Agent port (40705 by default) of the destination machine

This will make a connection to the destination machine and gather the dynamic ports used by RPC and then check each one for connectivity from the ControlUp console machine.

Gets the AVD Sessions hosts in the same pool as the target machine/session.

The script will parse the records from the last X minutes (enter '0' to get all records from the past year). For all records with matching SessionID, UserName and MachineName the Active Application, Active Application Title and Active URL (if the active application is a browser) are displayed.