Parallels RAS 19 provides a new and modern application delivery method - Application Packages, which is based on MSIX app attach technology. MSIX app attach is a Microsoft’s application layering solution that allows you to dynamically attach applications (containerized MSIX packages) to a user session. Separating the application from the operating system makes it easier to get more control by providing the right application for the right user. Additional third party solutions such as appCURE may be used for application moderation with Parallels RAS.
RD Sessions Hosts, VMs, or AVD hosts.
MSIX app attach requires hosts running Windows Server 2022, Windows 11, Windows 10 version 2004 or later.
A network share where the MSIX images will be stored. Storage requirements and recommendations are highlighted here: https://docs.microsoft.com/en-us/azure/virtual-desktop/app-attach-file-share.
All hosts (computer accounts) must have read permissions on the network share where the MSIX images are stored.
Note: In Parallels RAS 19, MSIX app attach applications can be deployed and managed directly from the Parallels RAS console only when using Windows Server 2022.
To start working with MSIX application packages, you need to enable the Application Packages feature.
To enable the Application Packages feature:
Navigate to Farm > Site > Settings and select the Application packages tab.
Select the Enable Application Packages feature option.
Next, you need to add the package to Parallels RAS.
To create an MSIX package from any desktop installer such as MSI, EXE, ClickOnce, or App-V you can use the MSIX Packaging tool https://docs.microsoft.com/en-us/windows/msix/packaging-tool/tool-overview.
To expand MSIX-packaged applications into MSIX images you can use the MSIXMGR tool https://docs.microsoft.com/en-us/azure/virtual-desktop/app-attach-msixmgr.
To add an MSIX application package to Parallels RAS:
Navigate to Farm > Site > Application Packages.
Click Tasks > Add (or click the [+] icon). The Add from MSIX Image wizard opens.
In the MSIX Image path field, specify the path to your image or click the Browse button to select it in File Explorer. The file must be located on a network share. You can add packages from VHD, VHDX, and CIM images. All hosts (computer accounts) must have read permissions on the network share where the MSIX images are stored.
In the Package drop-down list select the package that you want to add.
In the Display Name field specify the name that will be used for this package in Parallels RAS. After that, the rest of the fields will be populated automatically.
Click Finish.
Next, you need to add the package to a host. After being added, a packaged application behaves the same way as a regular application as if it was installed on a host.
To add a package to a host:
Make sure that the package is added to Parallels RAS as described above.
Go to Farm > Site > RD Session Hosts > RD Session Hosts.
Double-click the host that you want to install the package to.
In the properties dialog, on the Application Packages tab, click Tasks > Add (or click the [+] icon).
In the first column to the left, select the packages that you want to install on the host.
In the Version column, select the version of the package. It is recommended to make use of version tags, which can facilitate application version updates. If the selected packages have dependencies, you will see a warning that lists all of them.
Click OK.
The selected packages will be added to the host.
To add a package to a VDI pool:
Make sure that the package is added to Parallels RAS as described above.
Go to Farm > Site > VDI > Pools.
Double-click the pool that you want to install the package to.
In the properties, on the Application Packages tab, clear option Inherit default settings.
Continue from Step 4 as described in the subsection "Adding a package to a host" above.
The selected packages will be added to all VMs in the pool.
To add a package to an AVD pool:
Make sure that the package is added to Parallels RAS as described above.
Go to Farm > Site > Azure Virtual Desktop > Host pools.
Double-click the pool that you want to install the package to.
In the properties, on the Application Packages tab, clear option Inherit default settings.
In the properties, continue from Step 4 as described in the subsection "Adding a package to a host" above.
The selected packages will be added to all hosts in the pool.
To add a package to Group Defaults:
Make sure that the package is added to Parallels RAS as described above.
Go to Farm > Site > RD Session Hosts > Groups.
Double-click the group or pool that you want to install the package to.
In the properties, continue from Step 4 as described in the subsection "Adding a package to a host" above.
To add a package to Site Defaults:
Make sure that the package is added to Parallels RAS as described above.
Open group or pool properties as described above.
On the Application Packages tab, click Site Defaults.
In the dialog that opens, continue from Step 4 as described in the subsection "Adding a package to a host" above.
You can use version tags to simplify package management. For example, you can assign different tags to packages that are ready for publishing and these that are still in the testing stage. By default, Parallels RAS uses three tags: Production, Pre-production, and Custom. You can rename tags, but you cannot add or delete them.
To rename a tag:
Navigate to Farm > Site > Settings and select Application packages tab.
Select the tag that you want to rename.
Click Tasks > Edit.
Change the name of the tag and press Enter.
To use tags, you need to assign them.
To assign tags to a package:
Navigate to Farm > Site > Application Packages.
Double-click the package.
In the Version tag section, select the tags that you need. You can assign several tags to one package.
To remove all tags assigned to a package:
Navigate to Farm > Site > Settings and select the Application packages tab.
Select the package.
Click Tasks > Remove all tags.
Parallels RAS uses code signing certificates to ensure authenticity and content integrity of MSIX application packages.
The following code signing certificates can be used:
Self-signed certificates
CA certificates
Internal CA certificates
You can provision code signing certificates via GPO or let Parallels RAS install them to hosts automatically. The code signing certificate of a package must be trusted by all hosts that use that package.
Parallels RAS allows you to add certificates to hosts automatically. This option is recommended for self-signed certificates.
To enable automatic certificate provisioning:
Navigate to Farm > Site > Settings and select the Application packages tab.
Select option Provision package certificates automatically.
Certificate expiration dates are shown in Farm > Site > Application packages.
You can manage the added packages on the Farm > Site > Application Packages tab.
The following actions are available in the Task drop-down list:
Add: Adds a new package.
Change version tag: Assigns tags to a package.
Remove all tags: Removes all tags from the package.
Show published resources: Opens the list of all published applications from the package and the hosts they were published from.
Show assigned session hosts: Opens the list of hosts the selected package is assigned to.
Search: Allows you to search for a package in the list by applying a filter.
Delete: Deletes the package from Parallels RAS.
Settings audit: Opens the Settings Audit dialog where you can view the changes that were done to the packages.
Refresh: Refreshes the package list.
Properties: Shows the properties of the package (see below).
The following settings are available in the Application package properties window:
The General tab:
Enable application package in site: Select this option to enable the package.
Package: Name of the package.
Display Name: Name used for the package inside Parallels RAS.
Version: Version of the package.
Publisher: Common name of the publisher.
MSIX image path: Path to the MSIX image.
Version tag: Tags assigned to the package. You can change the assigned tags to the package from here.
Applications: List of applications added from the package.
Dependencies: All dependencies of the package.
The Certificate tab:
Key size: Size of the certificate.
Expiration date: Certificate expiration date.
Common name: Common Name specified in the certificate.
View certificate info: Shows information about the certificate.
Green
Ready
Package is enabled and ready for registration.
Green
In use
Package is being used in a session.
Orange
Disabling
Waiting for deregistration in sessions.
Red
Staging failed
A problem with registration has occurred. You can retry registration as described in Application Packages.
Red
Not found
The image file or network location unavailable. The admin can retry staging.
Red
Certificate missing
Package certificate is missing on the host.
Red
No version found
There is no application package marked with the tag selected in the host configuration.
Not applied
Not applied
Settings were changed but not applied