The following instructions will detail how to App-V sequence Microsoft Edge Browser, if the sequencing client hasn't been configured read this page.
First thing, revert the Hyper-V checkpoint to ensure the sequencing client is clean and the virtual network. is disabled.
Download the latest version of Microsoft Edge for x64 systems from here to your Windows 10 host.
Power on the Sequencing client, when the display settings prompt, click 'Show Options
Select the 'Local Resources' tab and click 'More...'
Select 'Windows (C:)' to pass through the host C:\ to the Sequencing client VM.
Browse and locate Microsoft Edge Browser and copy to the sequencing client.
Launch App-V Sequencer and click on 'Create a New Virtual Application Package'
Go with the default 'Create Package (default)'
The sequencer will check to confirm that there are no outstanding issues, such at required reboots
Again, go with the default 'Standard Application (Default)',
Select 'Perform a custom installation'
Provide the Package Name with something meaningful.
Click on 'Run...' to start the installation of MS Edge.
Browse to the installation media and open
When the installation completes, check 'I am finished installing'
The sequencer will capture the changes, this make take sometime depending on the application.
Select 'Microsoft Edge' and 'Run Selected'.
MS Edge will open, accept EULA and run through the startup configuration.
Make any desired changes to MS Edge and close
Click past the 'Installation Report'
Select 'Allow the package to run only on the following operating systems' and select 'Winodws 10 64-bit'
Select 'Continue to modify package without saving the package editor'
MS Edge generates 'DCOM subsystem detected' and 'Files excluded package'
Click on each of the warnings for further information, these are to be expected and on the whole can be ignored for now. Testing will highlight and issues.
To make sure the sequenced app-v package the following changes are required.
in the description of the 'Properties' tab add the version and any other support comments.
The DCOM error was related to the MS Edge services for updating itself. certainly dont want that.
Change the 3 services 'Start' to 4 (disabled), in the 'Virtual Registry' tab.
Without the following folder deletion MS Edge will not work, it fails to load during testing with error '0xc0000142'. This is not due to 8.3 name creations being disabled.
Delete both 'System' and 'Windows' directories
This what the folder structure will look like after the tidy up.
With those changes made, save the package.
Now for a quick test of the sequences package. From Windows 10 1607 App-V was integrated and requires enabling.
Open elevated Powershell window and run the following, no reboots required
To publish the sequenced package and ultimately test its functionality, run the following command
Add-AppvClientPackage -Path 'C:\Packages\Edge\Microsoft Edge Browser.appv' -DynamicDeploymentConfiguration 'C:\Packages\Edge\Microsoft Edge Browser_DeploymentConfig.xml' |
The package will publish and mount itself in C:\ProgramData\App-V. This may take a while and some of the files may appear offline until its fully published.
Go to the Start Menu and launch 'Microsoft Edge'. Not forgetting that Edge was previously installed during the sequencing. Check the shortcut to make sure its the correct version.
Or run 'Appwiz.cpl' and remove Microsoft Edge
Now copy the sequenced package to the host and up to ConfigMgr for deployment. This will be covered next