Sequencing Client Prep

Microsoft's Application Virtualization (App-V)  is a tool for sequencing applications that run in a self contained bubble. The App-V package contains all the necessary files and registry settings to run without the need to  run the traditional installation routine. This is great for reducing application compatibility conflicts and dll hell, it does not provide compatibility for the OS. 

 To sequence an application a Windows packaging client is required. The packaging client has to be the same as target client that the App-V package will be deployed to. x64 and x86 should also packaged on matching architecture separately and not part of the domain.

I'm using Windows 10 x64 with Hyper-V installed, the sequencer is a virtual machine, in the following case, again, its Windows 10 1809.

This is how the sequencer is configured:

Install Windows 10 x64 and fully patch, don't install any other applications.

Run adksetup.exe

Select 'Microsoft Application Virtualization (App-V) Sequencer', deselected all other options.

The App-V sequencer is installed.

During the sequencing process, you want to prevent Windows Updating and AV scans.

From the Run command type, 'services.msc' and disable and stop the following:

 Windows Update Services

 Windows Search

Or run the following PowerShell command

$svc = "wuauserv","wsearch"

foreach ($sv in $svc)
{
    Get-Service -Name $sv | Set-Service -StartupType Disabled
    Stop-Service -Name $sv -Force -NoWait
 }

Right click on the Windows Shield in the Notification Area, View Security Dashboard

Click 'Manage Settings'

Set both 'Real-Time Protection' and 'Cloud-Delivered Protection' to Off

To prevent all this hard work being undone and having to be repeated for each sequenced application, create a 'Checkpoint'

Each time an application is sequenced revert the 'Checkpoint'.

Next up will be how to Sequence an application.

Windows Defender tries to prevent its services being disabled, the quick solution is to disable 'Active Scans'

However, as Anti-Virus is about to be disabled, the Hyper-V network should be configured  to 'Not Connected'.