Installing applications on the session host virtual machine(s)
Application Delivery Methodology
Users can access any applications that are installed the session host virtual machine (SHVM) where their user session is running.
Users are assigned to a pool of SHVMs ("host pool") based on their membership in a user group. Every SHVM in that host pool is based on the same VM Image, has the same applications and runs on the same VM resources. Each time a user connects, they are assigned to SHVM in their host pool with the fewest current user sessions.
By adding or removing applications from each SHVM in the host pool the VDMS administrator can control which applications VDMS users can access.
Adding (or removing) applications from each SHVM can be performed directly on each SHVM or to a single VM Image which in turn can be deployed to all SHVMs in the host pool.
This article covers directly installing applications on the SHVMs. VM Image management is covered in this article.
The VDMS management portal provides direct access to each VM via a just-in-time local admin account for all SHVMs and business servers. This access can be used to manually connect to each VM to manually install applications and make other configuration changes.
This functionality is found in Workspace > Servers > Actions > Connect
If domain admin credentials are required, VDMS privileged access management (PAM) functionality to generate domain admin credentials. Details can be found here.
With the VDMS portal, the "Scripted Events" section includes functionality to remotely run code.
Within Scripted Events, the Repository tab contains "global" scripts that are published by NetApp. Custom scripts can be added using the "+ Add Script" button.
Within Scripted Events, the Activities tab contains the trigger that causes a script to run against a set of VMs. For VDMS, the "Manual" and "Scheduled" event types are best to push a script across the appropriate virtual machines.
|Activities have many available triggers called "Event Types". For VDMS, the "Application Install" and "Application Uninstall" types do not apply. These are RDS-specific triggers and should not be used for VDMS since VDMS is a WVD-based service, and does to follow the design architecture of RDS.|
Other Automation Tools
Virtual machines in VDMS can be managed with 3rd party management tools. Application changes and other VM configuration changes can be applied via any compatible tools.