NetApp VDS has functionality to run scripts in virtual desktop environments using our existing security context and to trigger those based on a variety of events. This functionality allows VDS administrators to build their best practices into automation that can be triggered as appropriate. Some examples include:
Zipping up and archiving a user profile as part of the "delete user" function
Automatically running session host optimization changes when a new session host VM is built
Automated application install when the app is assigned to a client
Until now, the script library shipped empty, requiring a VDS admin to build and test all scripts they wished to implement. With the release of Global Scripts the product now includes a handful of common scripts that can be used as-is or used as a starting point for custom automation.
The first batch of scripts include install and uninstall actions for the following applications:
Adobe Reader DC
AMD Radeon Instinct Drivers
Ezeep Print App
Microsoft Edge Chromium
Microsoft Office 365 (without One Drive and Teams, to allow for stand alone installs below)
Microsoft One Drive
Microsoft Teams (Optimized for WVD)
Nvidia CUDA Drivers
Nvidia GRID Drivers
NetApp has also dedicate resources to ongoing development of additional scripts. We already have a good list of items in the queue but please don't hesitate to add a comment for ideas you'd find useful while managing your VDS environments.
A new filter to only show Global Scripts: A new filter to only show Global Scripts:
Added a "Documentation URL" and corresponding documentation on the docs.netapp.com site: Added a "Documentation URL" and corresponding documentation on the docs.netapp.com site:
Added the "Download" action to allow the administrator to download the script file used in this script. For both audit and re-use purposes:Added the "Download" action to allow the administrator to download the script file used in this script. For both audit and re-use purposes:
I forgot to mention, we've also added the ability to clone existing customer and global scripts. This makes it that much easier to customize and build upon the global scripts and to iterate on them over time. This will be live in v6.0 with the release tomorrow evening.
Cloning an existing script: "Clone" is now available from the actions menu.
The new script can be given a new name: Provide a new Script name.
Success message: Success message
Post cloning, the new script can be edited and used:
The newly created scripts is a "customer" script and fully editable.