Merge pull request #237965 from dknappettmsft/avd-msix-combine-articles

AVD MSIX combine articles

Author: JamesJBarnett

.openpublishing.redirection.virtual-desktop.json

@@ -174,6 +174,16 @@
             "source_path_from_root": "/articles/virtual-desktop/environment-setup.md",
             "redirect_url": "/azure/virtual-desktop/terminology",
             "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/virtual-desktop/app-attach-image-prep.md",
+            "redirect_url": "/azure/virtual-desktop/msix-app-attach-create-msix-image",
+            "redirect_document_id": true
+        },
+        {
+            "source_path_from_root": "/articles/virtual-desktop/app-attach-msixmgr.md",
+            "redirect_url": "/azure/virtual-desktop/msix-app-attach-create-msix-image",
+            "redirect_document_id": false
         }
     ]
 }

articles/virtual-desktop/TOC.yml

@@ -202,20 +202,18 @@
           href: publish-apps.md
         - name: MSIX app attach
           items:
+          - name: Create an MSIX image
+            href: msix-app-attach-create-msix-image.md
+          - name: Set up a file share
+            href: app-attach-file-share.md
+          - name: Use Azure NetApp Files and MSIX app attach
+            href: create-netapp-files.md
           - name: Set up MSIX app attach with the Azure portal
             href: app-attach-azure-portal.md
           - name: Set up MSIX app attach with PowerShell
             href: app-attach-powershell.md
           - name: Test and troubleshoot MSIX packages
             href: app-attach.md
-          - name: Prepare an MSIX image
-            href: app-attach-image-prep.md
-          - name: Set up a file share
-            href: app-attach-file-share.md
-          - name: Use Azure NetApp Files and MSIX app attach
-            href: create-netapp-files.md
-          - name: Set up the MSIXMGR tool
-            href: app-attach-msixmgr.md
           - name: MSIXMGR tool parameters
             href: msixmgr-tool-syntax-description.md 
         - name: Use Microsoft Teams

articles/virtual-desktop/app-attach-azure-portal.md

@@ -9,7 +9,9 @@ manager: femila
 ---
 # Set up MSIX app attach with the Azure portal
 
-This article will walk you through how to set up MSIX app attach in a Azure Virtual Desktop environment.
+MSIX app attach is an application layering solution that allows you to dynamically attach apps from an MSIX package to a user session. The MSIX package system separates apps from the operating system, making it easier to build images for virtual machines. MSIX packages also give you greater control over which apps your users can access in their virtual machines. You can even separate apps from the custom image and make them available them to users later.
+
+This article will walk you through how to set up MSIX app attach in an Azure Virtual Desktop environment.
 
 ## Requirements
 

articles/virtual-desktop/app-attach-file-share.md

@@ -34,7 +34,7 @@ Requirements can vary widely depending how many MSIX-packaged applications are s
 
 ## Storage recommendations
 
-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. The article [Storage options for FSLogix profile containers in Azure Virtual Desktop](store-fslogix-profile.md) compares the different managed storage solutions Azure offers in the context of Azure Virtual Desktop.
+Azure offers multiple storage options that can be used for MSIX app attach. We recommend using Azure Files or Azure NetApp Files as those options offer the best value between cost and management overhead. The article [Storage options for FSLogix profile containers in Azure Virtual Desktop](store-fslogix-profile.md) compares the different managed storage solutions Azure offers in the context of Azure Virtual Desktop.
 
 ## Optimize MSIX app attach performance
 

articles/virtual-desktop/app-attach-image-prep.md

@@ -0,0 +1,97 @@
+---
+title: Create an MSIX image for Azure Virtual Desktop - Azure
+description: To use MSIX app attach with Azure Virtual Desktop, you need to expand an MSIX-packaged application into an MSIX image. This article shows you how to create an MSIX image.
+author: dknappettmsft
+ms.topic: how-to
+ms.date: 05/12/2023
+ms.author: daknappe
+---
+
+# Create an MSIX image for Azure Virtual Desktop
+
+To use MSIX app attach with Azure Virtual Desktop, you need to expand an MSIX-packaged application into an MSIX image. This article shows you how to create an MSIX image, which you then need to upload to a file share and publish in Azure Virtual Desktop.
+
+## Prerequisites
+
+Before you can create an MSIX image, you need to meet the following prerequisites:
+
+- Download the [MSIXMGR tool](https://aka.ms/msixmgr) and extract it to a folder.
+
+- Administrative permissions on a Windows 10 or Windows 11 device to create the MSIX image.
+
+- An MSIX-packaged application (`.msix` file) you want to use with Azure Virtual Desktop. To learn how to convert a desktop installer to an MSIX package, see [Create an MSIX package from any desktop installer (MSI, EXE, ClickOnce, or App-V)](/windows/msix/packaging-tool/create-app-package).
+
+   > [!NOTE]
+   > If you're using packages from the Microsoft Store for Business or Education on your network or on devices not connected to the internet, you'll need to download and install package licenses from the Microsoft Store to run the apps. To get the licenses, see [Use packages offline](app-attach.md#use-packages-offline).
+
+## Create an MSIX image
+
+When creating an MSIX image, you convert an MSIX package to a *VHD*, *VHDX*, or *CIM* disk image using the MSIXMGR tool. We recommend using CIM for best performance, particularly with Windows 11, as it consumes less CPU and memory, with improved mounting and unmounting times. We don't recommend using VHD; use VHDX instead.
+
+Select the relevant tab for your scenario.
+
+# [CIM](#tab/cim)
+
+Here are example commands to create an MSIX image as a CIM disk image. You'll need to change the example values for your own.
+
+You should create a new folder for the destination because a CIM disk image is made up of multiple files and this helps differentiate between the images.
+
+> [!IMPORTANT]
+> To guarantee compatibility, make sure the CIM files storing your MSIX images are generated on a version of Windows that is lower than or equal to the version of Windows where you are planning to run the MSIX packages. For example, CIM files generated on Windows 11 may not work on Windows 10.
+
+1. Open command prompt as an administrator and change to the directory you extracted the MSIXMGR tool. 
+
+1. Create a new folder for the destination.
+
+1. To create the CIM disk image, run the following command:
+
+   ```cmd
+   msixmgr.exe -Unpack -packagePath "C:\msix\myapp.msix" -destination "C:\msix\myapp\myapp.cim" -applyACLs -create -fileType cim -rootDirectory apps
+   ```
+
+   The output should be as follows:
+
+   ```Output
+   Successfully created the CIM file: C:\msix\myapp\myapp.cim
+   ```
+
+# [VHDX](#tab/vhdx)
+
+Here's an example command to create an MSIX image as a VHDX disk image. A single VHDX file is created. 
+
+1. Open command prompt as an administrator and change to the directory you extracted the MSIXMGR tool. 
+
+1. To create the VHDX disk image, run the following command:
+
+   ```cmd
+   msixmgr.exe -Unpack -packagePath "C:\msix\myapp.msix" -destination "C:\msix\myapp.vhdx" -applyACLs -create -fileType vhdx -rootDirectory apps
+   ```
+
+   The output should be as follows:
+
+   ```Output
+   Successfully created virtual disk
+   Stopping the Shell Hardware Detection service
+   Stopping dependent services if necessary.
+   Successfully initialized and partitioned the disk.
+   Formatting the disk.
+   Successfully formatted disk
+   Starting the Shell Hardware Detection service
+   Successfully started the Shell Hardware Detection Service
+   Finished unpacking packages to: C:\msix\myapp.vhdx
+   ```
+---
+
+## Next steps
+
+After you've created the MSIX package, you'll still need to do the following tasks:
+
+1. Copy the resulting VHD, VHDX, or CIM file to a share where your session hosts can access it. To learn about the requirements, see [File share requirements for MSIX app attach](app-attach-file-share.md).
+
+1. [Publish MSIX applications in Azure Virtual Desktop](app-attach-azure-portal.md).
+
+Here are some other articles you might find helpful:
+
+- Learn more about the available [MSIXMGR tool parameters](msixmgr-tool-syntax-description.md).
+- [MSIX app attach glossary](app-attach-glossary.md)
+- [MSIX app attach FAQ](app-attach-faq.yml)

articles/virtual-desktop/app-attach-msixmgr.md

@@ -104,23 +104,20 @@ msixmgr.exe -Unpack -packagePath "C:\SomeDirectory\myapp.msix" -destination "C:\
 
 To unpack a package into a VHDX disk image:
 
-> [!NOTE]
-> If you're using VHD or VHDX, we recommend the size is four times the size of MSIX package.
-
 ```
-msixmgr.exe -Unpack -packagePath "C:\SomeDirectory\myapp.msix" -destination "C:\Apps\myapp" -applyACLs -create -vhdSize 200 -filetype VHDX -rootDirectory apps
+msixmgr.exe -Unpack -packagePath "C:\SomeDirectory\myapp.msix" -destination "C:\Apps\myapp\myapp.vhdx" -applyACLs -create -filetype VHDX -rootDirectory apps
 ```
 
 To unpack a package into a CIM disk image:
 
 ```
-msixmgr.exe -Unpack -packagePath "C:\SomeDirectory\myapp.msix" -destination "C:\Apps\myapp" -applyACLs -create -filetype CIM -rootDirectory apps
+msixmgr.exe -Unpack -packagePath "C:\SomeDirectory\myapp.msix" -destination "C:\Apps\myapp\myapp.vhdx" -applyACLs -create -filetype CIM -rootDirectory apps
 ```
 
 |Optional parameters|Description|Example|
 | -------- | -------- | -------- |
 |-applyacls|Applies ACLs to the resulting package folder(s) and their parent folder. |`msixmgr.exe -Unpack -packagePath "C:\SomeDirectory\myapp.msix" -destination "C:\Apps\myapp" -applyACLs` |
-|-create|Creates a new image with the specified -filetype and unpacks the packages to that image. |`msixmgr.exe -Unpack -packagePath "C:\SomeDirectory\myapp.msix" -destination "C:\Apps\myapp" -applyACLs -create -fileType VHDX -vhdSize 200` |
+|-create|Creates a new image with the specified -filetype and unpacks the packages to that image. |`msixmgr.exe -Unpack -packagePath "C:\SomeDirectory\myapp.msix" -destination "C:\Apps\myapp" -applyACLs -create -fileType VHDX` |
 |-fileType|The type of file to unpack packages to. Valid file types include `VHD`, `VHDX`, `CIM`. This is a required parameter when unpacking to CIM files. |`msixmgr.exe -Unpack -packagePath "C:\SomeDirectory\myapp.msix" -destination "C:\Apps\myapp" -applyACLs -create -fileType CIM -rootDirectory apps` |
 |-rootDirectory|Specifies root directory on image to unpack packages to. Required parameter for unpacking to new and existing CIM files. |`msixmgr.exe -Unpack -packagePath "C:\SomeDirectory\myapp.msix" -destination "C:\Apps\myapp" -applyACLs -create -filetype CIM -rootDirectory apps` |
 |-validateSignature|Validates a package's signature file before unpacking package. This parameter will require that the package's certificate is installed on the machine.<br /><br />For more information, see [Certificate Stores](/windows-hardware/drivers/install/certificate-stores).|`msixmgr.exe -Unpack -packagePath "C:\SomeDirectory\myapp.msix" -destination "C:\Apps\Myapp" -validateSignature -applyACLs`|