Microsoft App-V 5.1 Sequencer – Preparation and Installation

Preparing for your App-V Sequencing environment?

Here is a quick rundown of some of the things to consider as well as installation steps.

 

 

Sequencer Supported Configurations

Sequencer system requirements

The following table lists the operating systems that are supported for the App-V 5.1 Sequencer installation

Operating system Service pack System architecture
    Microsoft Windows Server 2012 R2
    64-bit
    Microsoft Windows Server 2012
    64-bit
    Microsoft Windows Server 2008 R2
    SP1
    64-bit
    Microsoft Windows 10
    32-bit and 64-bit
    Microsoft Windows 8.1
32-bit and 64-bit
Microsoft Windows 8
    32-bit and 64-bit
    Microsoft Windows 7
    SP1
    32-bit and 64-bit

 

Sequencer Pre-requisites

The following table indicates the software that is already installed for different operating systems.

Operating system Prerequisite description
    Windows 10
    All of the prerequisite software is already installed.
    Windows 8.1
    All of the prerequisite software is already installed.
    Note
    If you are running Windows 8, upgrade to Windows 8.1 before using App-V 5.1.
Windows Server 2012 The following prerequisite software is already installed:

  • Microsoft .NET Framework 4.5.1
  • Windows PowerShell 3.0
    Note
    Installing PowerShell 3.0 requires a restart.
    Windows 7
    The prerequisite software is not already installed. You must install it before you can install App-V.

 

    What to know before installing the prerequisites:
  • Best practice: The computer that runs the Sequencer should have the same hardware and software configurations as the computers that will run the virtual applications.
  • The sequencing process is resource intensive, so make sure that the computer that runs the Sequencer has plenty of memory, a fast processor, and a fast hard drive. The system requirements of locally installed applications cannot exceed those of the Sequencer.
Prerequisite Details
Microsoft .NET Framework 4.5.1 (Web Installer)
Windows PowerShell 3.0
    Installing PowerShell 3.0 requires a restart.
KB2533623
    Applies to Windows 7 only: Download and install the KB.

 

Installing the Sequencer

After having reviewed that he pre-requisites exist on your chosen OS proceed with the following steps

  1. Run the appv-Sequencer_setup.exe you will be presented with the first dialog to begin the installation. Click on Install link.
  2. Next select I accept the license terms and then click Next.
  3. The next option allows you to choose whether to join the MS customer experience. Select your choice and then click Install.
  4. If no errors appear during the installation the Application Sequencer will be ready for you to launch and start sequencing.

Microsoft Services to Disable

With the latest release of App-V the only Native Microsoft operating system services to disable are

  • Windows Defender
  • Windows Search

Third party Services / Applications to Disable

For hassle free application sequencing, it is recommended that you use a Vanilla or base image of your corporate SOE to sequence applications on. In some cases it may not be an option, in that case look at disabling the following third party software and services to minimise sequencing and in turn App-V application testing.

  • Antivirus Client software
  • Profile Management services (Appsense/RES/Citrix)
  • OS management Client’s. Eg System Center 2012, Altiris, Novell…

Advanced Unattended Installation

You can also use the command line to install the App-V 5.1 sequencer. The following list displays information about options for installing the sequencer using the command line and appv_sequencer_setup.exe:

Command Description
/INSTALLDIR Specifies the installation directory.
/CEIPOPTIN Enables participation in the Microsoft Customer Experience Improvement Program.
/Log Specifies where the installation log will be saved, the default location is %Temp%. For example, C:\ Logs \ log.log.
/q Specifies a quiet or silent installation.
/Uninstall Specifies the removal of the sequencer.
/ACCEPTEULA Accepts the license agreement. This is required for an unattended installation. Example usage: /ACCEPTEULA or /ACCEPTEULA=1.
/LAYOUT Specifies the associated layout action. It also extracts the Windows Installer (.msi) and script files to a folder without installing App-V 5.1. No value is expected.
/LAYOUTDIR Specifies the layout directory. Requires a string value. Example usage: /LAYOUTDIR=”C:\Application Virtualization Client”.
/? Or /h or /help Displays associated help.

App-V Visual C++ Redistributable Management

App-V 5.0 has been able to successfully virtualise Visual C++ Runtimes since the release of SP2. In the case of whether to manage redistributables separate to the virtualised package, that is to install them natively on the App-v client OS. There is no definitive rule to state the recommended management methodology. For the administrator looking for best practice recommendations and new to application virtualisation.

Natively installed on the Sequencer and Client
      –          Requires management of application sequencer builds
      –          Requires management of the application’s client builds
      –          Minimise potential SXS conflicts of Grouped Virtual apps with VisualC++ data running on clients with native instances of the same Visual C++ components.
      –          Managed Visual runtimes allow you to easily transition or deploy Virtual Packages from one Windows OS to Another. Win7, 8, 10, server 2008, 2012 cutting down rework and testing.
    –          Avoid mismatch of Visual C++ Components between Sequencer and Client.
Included with the Virtualised Applications
      –          Less management of application sequencer builds
      –          Less management of application client builds
      –          In conjunction with heavy connection group usage of virtual apps a relaxed management approach of app components can potentially open up more instances of issues/conflicts to resolve as virtual application portfolios grow over time.
      –          Incorporating Visual Runtimes into virtual packages still allows for easy package transition and deployment across different operating systems, so long as there is a consistent methodology applied to incorporating visual C++ components and other pre-requisites into virtual packages.
    –          Higher chance of mismatch of runtimes between the sequencer and client.

 

 

 

The screenshot above demonstrating the option in the sequencer where to Enable or Disable packaging Visual C_++ runtimes.

 

 

Leave a Reply

Your email address will not be published. Required fields are marked *