Update README.md

Author: Deyda

MSIX App Attach/README.md

@@ -107,142 +107,3 @@ MSIX app attach has four distinct phases that must be performed in the following
 Each phase creates a PowerShell script. Sample scripts for each phase are available here.
 
 After you've disabled automatic updates, you must enable Hyper-V because you'll be using the Mound-VHD command to stage and and Dismount-VHD to destage.
-```
-Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All
-````
-### Stage the PowerShell script
-Before you update the PowerShell scripts, make sure you have the volume GUID of the volume in the VHD. To get the volume GUID:
-
-- Open the network share where the VHD is located inside the VM where you'll run the script.
-- Right-click the VHD and select Mount. This will mount the VHD to a drive letter.
-- After you mount the VHD, the File Explorer window will open. Capture the parent folder and update the $parentFolder variable
-- Open the parent folder. If correctly expanded, you'll see a folder with the same name as the package. Update the $packageName variable to match the name of this folder.
-For example, VSCodeUserSetup-x64-1.38.1_1.38.1.0_x64__8wekyb3d8bbwe.
-- Open a command prompt and enter mountvol. This command will display a list of volumes and their GUIDs. Copy the GUID of the volume where the drive letter matches the drive you mounted your VHD to in step 2.
-For example, in this example output for the mountvol command, if you mounted your VHD to Drive C, you'll want to copy the value above C:\:
-````
-Possible values for VolumeName along with current mount points are:
-
-\\?\Volume{a12b3456-0000-0000-0000-10000000000}\
-*** NO MOUNT POINTS ***
-
-\\?\Volume{c78d9012-0000-0000-0000-20000000000}\
-    E:\
-
-\\?\Volume{d34e5678-0000-0000-0000-30000000000}\
-    C:\
-````
-- Update the $volumeGuid variable with the volume GUID you just copied.
-- Open an Admin PowerShell prompt and update the following PowerShell script with the variables that apply to your environment.
-````
-#MSIX app attach staging sample
-#region variables
-$vhdSrc="<path to vhd>"
-$packageName = "<package name>"
-$parentFolder = "<package parent folder>"
-$parentFolder = "\" + $parentFolder + "\"
-$volumeGuid = "<vol guid>"
-$msixJunction = "C:\temp\AppAttach\"
-#endregion
-#region mountvhd
-try
-{
-Mount-Diskimage -ImagePath $vhdSrc -NoDriveLetter -Access ReadOnly
-Write-Host ("Mounting of " + $vhdSrc + " was completed!") -BackgroundColor Green
-}
-catch
-{
-Write-Host ("Mounting of " + $vhdSrc + " has failed!") -BackgroundColor Red
-}
-#endregion
-#region makelink
-$msixDest = "\\?\Volume{" + $volumeGuid + "}\"
-if (!(Test-Path $msixJunction))
-{
-md $msixJunction
-}
-$msixJunction = $msixJunction + $packageName
-cmd.exe /c mklink /j $msixJunction $msixDest
-#endregion
-#region stage
-[Windows.Management.Deployment.PackageManager,Windows.Management.Deployment,ContentType=WindowsRuntime]| Out-Null
-Add-Type -AssemblyName System.Runtime.WindowsRuntime
-$asTask = ([System.WindowsRuntimeSystemExtensions].GetMethods() | Where {$_.ToString() -eq 'System.Threading.Tasks.Task`1[TResult] AsTask[TResult,TProgress](Windows.Foundation.IAsyncOperationWithProgress`2[TResult,TProgress])'})[0]
-$asTaskAsyncOperation = $asTask.MakeGenericMethod([Windows.Management.Deployment.DeploymentResult],[Windows.Management.Deployment.DeploymentProgress])
-$packageManager = [Windows.Management.Deployment.PackageManager]::new()
-$path = $msixJunction + $parentFolder + $packageName # needed if we do the pbisigned.vhd
-$path = ([System.Uri]$path).AbsoluteUri
-$asyncOperation = $packageManager.StagePackageAsync($path, $null, "StageInPlace")
-$task = $asTaskAsyncOperation.Invoke($null, @($asyncOperation))
-$task
-#endregion
-````
-# AppAttach.ps1
-For each application, you have to define the following properties:
-
-Property |	Note
---------|-------
-vhdSrc | Path to the expanded MSIX app (as vhd)
-volumeGuid |	Guid of the vhd
-packageName |	Name of the MSIX app attach package
-parentFolder |	Root folder name in your vhd
-hostPools |	List of host pool names where the package should be applied
-userGroups |	List of AD groups: Members get the application linked in their start menu
-
-## Refer this file by a group policy:
-
-- Computer Configuration - Policies - Windows Settings - Scripts - Startup
-
-  - Name: %windir%\System32\WindowsPowerShell\v1.0\powershell.exe
-
-  - Parameter: -ExecutionPolicy Unrestricted -File \ads01\Configuration\WVD\MSIX\AppAttach.ps1 -ConfigFile \\ads01\Configuration\WVD\MSIX\AppAttach.json -Mode VmStart
-
-- Computer Configuration - Policies - Windows Settings - Scripts - Shutdown
-
-  - Name: %windir%\System32\WindowsPowerShell\v1.0\powershell.exe
-
-  - Parameter: -ExecutionPolicy Unrestricted -File \ads01\Configuration\WVD\MSIX\AppAttach.ps1 -ConfigFile \\ads01\Configuration\WVD\MSIX\AppAttach.json -Mode VmShutdown
-
-- User Configuration - Policies - Windows Settings - Scripts - Logon
-
-  - Name: %windir%\System32\WindowsPowerShell\v1.0\powershell.exe
-
-  - Parameter: -ExecutionPolicy Unrestricted -File \ads01\Configuration\WVD\MSIX\AppAttach.ps1 -ConfigFile \ads01\Configuration\WVD\MSIX\AppAttach.json -Mode UserLogon
-
-- User Configuration - Policies - Windows Settings - Scripts - Logoff
-
-  - Name: %windir%\System32\WindowsPowerShell\v1.0\powershell.exe
-
-  - Parameter: -ExecutionPolicy Unrestricted -File \ads01\Configuration\WVD\MSIX\AppAttach.ps1 -ConfigFile \\ads01\Configuration\WVD\MSIX\AppAttach.json -Mode UserLogoff
-
-  - Where \\ads01\Configuration\WVD\MSIX\ is the path to the script and \\ads01\Configuration\WVD\MSIX\AppAttach.json the JSON-configuration file.
-
-- Make sure that the GPO is linked to the computer and enable loopback processing:
-
-- Computer Configuration - Policies - Administrative Templates - System/Group Policy
-
-  - Configure user Group Policy loopback processing mode: Enable - Mode: merge.
-
-## Preparing the golden master for the session hosts
-To work with MSIX and have the script do the work you have to prepare your golden image:
-
-- Make sure that you have installed the right version from the insider build
-
-- Double-check that you have NOT prepared your image with the command line commands described in https://docs.microsoft.com/en-us/azure/virtual-desktop/app-attach#prepare-the-vhd-image-for-azure (Disable Store auto-update and so on). It’s only for the VM concerning the converting process.
-
-- Copy the PSTools https://docs.microsoft.com/en-us/sysinternals/downloads/psexec to %Windir%\System32 (you need psexec later)
-
-- Give the service GPSVC the right privileges to mount images:
-
-  - Create a cmd-file with this content:
-```
-sc privs gpsvc SeManageVolumePrivilege/SeTcbPrivilege/SeTakeOwnershipPrivilege/SeIncreaseQuotaPrivilege/SeAssignPrimaryTokenPrivilege/SeSecurityPrivilege/SeChangeNotifyPrivilege/SeCreatePermanentPrivilege/SeShutdownPrivilege/SeLoadDriverPrivilege/SeRestorePrivilege/SeBackupPrivilege/SeCreatePagefilePrivilege
-```
-  - Open an administrative cmd and execute:
-```
-psexec /s cmd
-```
-  - In this service cmd execute the cmd-file to give GPSVC the right permissions
-
-(This adds the SeManageVolumePrivilege which allows mounting of images)
-