MSIX

From Piszczynski
Revision as of 16:21, 31 December 2022 by piszczynski>Aleks (Created page with " == MSIX == ===Overview=== All MSIX images must be stored on a network share that can be accessed by users in a host pool with read-only permissions. MSIX app attach doesn'...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

MSIX

Overview

All MSIX images must be stored on a network share that can be accessed by users in a host pool with read-only permissions.

MSIX app attach doesn't have any dependencies on the type of storage fabric the file share uses. The considerations for the MSIX app attach share are same for an FSLogix share.

Azure offers multiple storage options that can be used for MISX app attach. We recommend using Azure Files or Azure NetApp Files as those options offer the best value between cost and management overhead.

Here are some other things we recommend you do to optimize MSIX app attach performance:

  • The storage solution you use for MSIX app attach should be in the same datacenter location as the session hosts.
  • To avoid performance bottlenecks, exclude the following VHD, VHDX, and CIM files from antivirus scans:
    • <MSIXAppAttachFileShare\>\*.VHD
    • <MSIXAppAttachFileShare\>\*.VHDX
    • \\storageaccount.file.core.windows.net\share*.VHD
    • \\storageaccount.file.core.windows.net\share*.VHDX
    • <MSIXAppAttachFileShare>.CIM
    • \\storageaccount.file.core.windows.net\share**.CIM
  • All VM system accounts and user accounts must have read-only permissions to access the file share.
  • Any disaster recovery plans for Azure Virtual Desktop must include replicating the MSIX app attach file share in your secondary failover location.