AppV 5.0 Beta Server Installation

Configuring AppV 5.0 Beta Server Installation

Provide the Database Instance in the below screen

Provide Website name and Unique Port Number for Management Server Configuration in below screen

Provide Website name for and Port number for Publishing Server in below screen

Once installation is completed, Provide the URL along with Port Number to access AppV Server as shown below

AppV 5.0 Beta Server Installation - Requirements

Following are the requirements to install AppV 5 Beta Server

• Microsoft Windows .NET Framework 4 Extended Version
• Windows Web Server 2008 with only the following features: Common HTTP Features (static content and default document), Application Development (ASP.NET, .NET Extensibility, ISAPI Extensions and ISAPI Filters), Security (Windows Authentication, Request Filtering)
• Microsoft .NET Framework 3.5 (For PowerShell support.)
• Download and install KB253623.( Its a printing mistake in guide, hence the actual KB is KB2533623)
• The Microsoft Visual C++ 2008 Redistributable Package (x64)(http://www.microsoft.com/download/en/details.aspx?id=15336)
• You must install both versions of the Microsoft .NET Framework (Microsoft .NET 3.5 and Microsoft .NET 4). Microsoft .NET 3.5 is required with Microsoft .NET 4 to enable and support the App-V 5.0 Beta Server PowerShell cmdlets.

Note: Installing the App-V 5.0 Beta server is not supported for the following scenarios:

• Installing on a domain controller.
• Installing on a server running previous versions of App-V server components.
• Installing on Server Core.

Convert Legacy AppV Package to AppV 5.0 format

Following Powershell command should be used to convert AppV packages developed using AppV 4.6SP1 or less TO AppV 5.0 format.


ConvertFrom-LegacyAppvPackage -source "{legacy pkgs}" -target "{vnext pkgs}"


where {legacy pkgs} and {v.Next pkgs} represent the path to the associated packages.

Sftmime and App-V 5.0 BetaPowerShell cmdlets

The following table displays the sftmime functions available with previous versions of App-V 5.0 Beta and the App-V 5.0 Beta PowerShell equivalent:

To install the App-V 5.0 BetaPowerShell Cmdlets

1. To use the Server App-V PowerShell Cmdlets open an elevated PowerShell cmd prompt and import the modules by running one of the following commands:


2. To load the Server App-V client cmdlets, type:
           PS C:\> Import-Module AppVClient
    To load the Server App-V server cmdlets, type:
           PS C:\> Import-Module AppVServer
    To load the Server App-V sequencer cmdlets, type:
           PS C:\> Import-Module AppVSequencer
    To load the Server App-V package converter cmdlets, type:
           PS C:\> Import-Module AppVConverter

AppV 5.0 Client GUI

AppV Client Interface in version 5.0 has changed to resemble Windows 8 tiles

Available AppV packages are visible as displayed below, we can find if its a offline package or streamed and also has the option to reset/repair user state.

The location where AppV package content is stored is C:\ProgramData\AppV\[PackageID]

AppV 5.0 Package Output

Sequencer output in AppV 5.0 has changed a lot, following are no more available

• No OSDs
• No sft file
• No Icons file

New output contains:

• .appv file
• .xml files ( DeploymentConfig.xml and UserConfig.xml)
• .msi file (report.xml)

Packages developed using AppV versions below 5 are to be converted to AppV 5 format, ( there is no native support of AppV 4.6 or below sequenced packages in AppV 5)

Screenshot of sample AppV 5 package output

When you use the sequencer to create a new virtual application, the following list displays the files that are created and comprise the App-V 5.0 Beta package:

• .MSI – this Windows Installer (.msi) file is created by the sequencer and is used to install the virtual package on target computers.
• Report.xml - the sequencer saves all issues, warnings, and errors that were discovered during sequencing and displays the information after the package has been created. You can us this report for diagnosing and troubleshooting.
• .appv file - the virtual application.
• Deployment configuration file - the deployment configuration file determines how the virtual application will be deployed to target computers.
• User configuration file - the user configuration file determines how the virtual application will run on target computers.

AppV 5.0 - Change in Variables

Addressing system locations using CSIDL format has changed in App 5.0. Microsoft made it simpler and similar to Installshield/Wise variables.

AppV 5.0 - No WinXP Support

Microsoft has removed WinXP as TargetOS in AppV 5, hence if AppV support for XP has to be there in any organization environment, they have to stick to AppV version 4.6SP1


Screenshot of TargetOSes in AppV 5

App-V 5.0 Beta Released

Microsoft has released App-V 5.0 Beta recently which has lot of new features.

For more information. Please go through following link

http://www.microsoft.com/getappv5