Life with the App-V AutoSequencer
It’s summer. Who should work all that hard anyway? I’m letting the AutoSequencer do the work for me.
With the March 2017 release of Microsoft Windows also came the 1703 version of the Windows ADK. The ADK contains a number of tools used by both developers and IT Pros and is generally updated with each OS release. When you go to get the ADK you almost always want to get the latest version – it supports features in that release but most of the time also supports prior OS releases as well.
The two major new items in the 1703 ADK were both App-V related, however these only work with Windows 10 1607 and Windows 16, or later, operating systems.
The first new item is the App-V Sequencer. With the App-V Client moving directly into the operating system, the ADK is now the release vehicle for the Sequencer. The primary reason that you cannot install this sequencer on Windows 7 is that it depends on some of the dlls in place for the in-box App-V client (which is present but not enabled by default).
The second new component is the App-V AutoSequencer. I wrote about the tool when it was released here but basically the AutoSequencer is a component that would be used on a Hyper-V enabled machine to control a virtual machine that has the App-V Sequencer installed. Great for that package you have to touch each month if you are an IT Pro, or for an ISV to output an App-V package right from Visual Studio. You probably don’t use the command line sequencer, but in addition to the wizard based GUI sequencer interface, the sequencer also has a command-line sequencing capability that can automatically create an App-V package from an unattended installation script. So the AutoSequencer manages the VM state, copies installers into the VM, runs the command-line sequencer and finally collects the output package.
Read the entire article here, Life with the App-V AutoSequencer
via the fine folks at FSLogix