Script library

Finds Azure resources, either for the resource group the VM the script is run against resides in or all resource groups in the subscription, that are not currently attached to a parent resource.

Note that Citrix MCS machine catalogs may have resources which are not currently assigned but will be assigned when a VM is created in that catalog so should not be removed.

The information returned should be cross referenced & checked to another source, such as the Azure portal, before any resources are deleted just because they feature in the output of this script.

Gets the name, version and install path of all found Office 365 installations.

Lists current service health events in the subscription.

Retrieve the list of all current Azure emerging issues and show those which are marked as impacting the locations which are used in the resource group or subscription for the selected VM

Show FSLogix currently mounted volume details and cross reference to FSLogix session information in the registry.

Uses data from the Azure Monitor API to find resources which have not got an entry in the logs in the given period which could mean that they have not been used in that time and be candidates for removal for simplifcation and cost reduction, depending on the resource type. Resources not directly in the logs, such as network interfaces, will be checked by looking for log entries for their parent VM.

Only resources within the same resource group as the chosen resource can be searched or all rescure groups for the tenant depending on the parameters passed.

The output can be sorted/grouped by any of the output columns.

Parameters to specifically include and/or exclude providers by regular expression are available.

Note that not all resources when used will generate an activity in the log so may be shown as no being used when they have actually been used in the given time period.

Exports Metrics to be used by the ControlUp Stress Calculator v2 by using the ControlUp Monitor Powershell Module. Uses True or False as string for the benefit of using the script as a ControlUp Script Action. See this link for Documentation:

Show the Azure activity logs for the last number of (fractional) days.
Options to just show entries for the chosen AZ resource, the resource group it is in or the whole subscription.

Create a number of Azure VMs using the selected machine as a template in terms of machine, disk sizes/types and network interfaces.
If the machine name contains # characters, these will be replaced, with leading zeroes, by the next available machine name
It does not clone or copy any disks other than any gallery image the original was built from.
If domain details are provided, it will attempt to join the given domain when creation is complete.
Multiple tags can be added in a comma separated list of the form Tag name=Tag text

Enables the WMI-Activity trace event log for a given period of seconds and then processes any resulting events to show what processes are generating what WMI activity and how long they took.
The summary option will summarise by process and display ordered by the total duration taken by all WMI operations.
Without a summary, each individual WMI operation will be listed along with the actual WMI operation.
The trace event log will be disabled at the end of the trace.

This script gets all the computer devices and checks the status.

Create the credential files (locally) required by the Citrix Cloud script actions.
Stored in %ALLUSERSPROFILE%ControlUpScriptingSupport but the client secret stored in the files can only be decrypted by the Windows user that created that file.
The files created contain the tenant id in the file name so that a single Windows user can have credential files for multiple tenants. Original Azure scripts did have this feature and the files contained the tenant id so only a single file can exist - this script creates both credential files so both new and old Azure script actions can be run.
The script willl overwrite any existing credential files for the user and tenant.

Create the credential files (locally) required by the Azure script actions.
Stored in %ALLUSERSPROFILE%ControlUpScriptingSupport but the client secret stored in the files can only be decrypted by the Windows user that created that file.
The files created contain the tenant id in the file name so that a single Windows user can have credential files for multiple tenants. Original Azure scripts did have this feature and the files contained the tenant id so only a single file can exist - this script creates both credential files so both new and old Azure script actions can be run.
The script willl overwrite any existing credential files for the user and tenant.

This script can be used to watch events being written in the logs on several machines in real-time. For example, if a user logs on to a remote session the events recorded for this on several machines such as the RDS/VDA machine, Storefront and Delivery Controller can all be displayed as they are being written.
Run the script with an account or Shared Credential with sufficient privileges on all targeted machines to read the event logs.
NOTE: this script should be run in the Real-time Console. Due to a dependcy on Gridview it cannot be run in Solve.

Change the type of disk assigned to the Azure VM. Valid disk types are:

Standard_LRS
Premium_LRS
StandardSSD_LRS
UltraSSD_LRS
Premium_ZRS
StandardSSD_ZRS

Note that costs of this VM once updated could be very different.

Gets the PowerShell modules installed/available to the account running the script; with type, version and description. If specified extra details will be displayed.

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

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

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 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