App-V 5.0 beta released

Microsoft released App-V 5.0, time to get our hands dirty!

The App-V Management Server remains, but changes are huge! No more RTSP(S) protocol, bits & bytes will transfert over HTTP. The Client Console is Siverlight based in Metro style (screenshot below), there is no more Q-Drive, OSD files are gone and SFT package format is history! Goodbye Softgrid!

Time for some hands on with the beta release!

App-V Client

We have to respect the order for upgrading the infrastucture. That is clients first, server second and sequencer last. Let’s start with the client.

Installing App-V 5.0 beta is a follow-the-wizard-process:

image

Joining the Customer Experience Improvement Program is mandatory:

image

After installing the product, I wanted to launch the App-V Client Console with the command sftcmc.msc, but apparently they got rid of the SFT –naming?

image

After browsing to All Programs > Microsoft Application Virtualization Client –container, a shortcut to AppVClientUX.exe is available;

image

Wow! A Metro Style interface!

My packages did not appear, probably I have to convert them to the new format.

App-V Server

Hitting the App-V 5.0 beta server executable (appv_server_setup.exe) didn’t launched the installer. Probably .NET Framework 4.0 is also a prerequisite for the server component?

The AppV Server log:

Loading prerequisite bootstrapper application because managed host could not be loaded, error: 0×80070490.
Error 0x8007007e: Failed to create the pre-requisite bootstrapper application.

After installing .Net Framework 4.0 the App-V installer finally shows an error:

image

I’ll have to remove my 4.5.3 server prior to installing the 5.0 beta server!

The AppV Server log shows the same:

Loading managed bootstrapper application.
AppvUX: Application Virtualization Server cannot be installed on this system because an incompatible version of the Microsoft Application Virtualization Server has been detected. Please uninstall the previous version and try again.

Upgrading isn’t supported, so a side-by-side migration is the only way. From the App-V 5.0 beta AdminGuide:

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.
As I don’t have another server for the moment, an uninstall is necessary. After removing the 4.5 server, de installation of the 5.0 beta server could proceed:

image

image

image

I need to install a updated SQL Server version, because I’m running SQL Server 2008 SP1.

The AppV Server log says:

The database pre-deployment feature can only be installed on a server running the Standard, Enterprise or Datacenter editions of SQL Server 2008 SP2, SQL Server 2008 R2 or greater.
AppvUX: The database pre-deployment feature can only be installed on SQL Server 2008 R2 or SQL Server 2008 servers running Service Pack 2.

Ok, I’m running SQL Server 2008 SP1 (10.0.2531.0). Need to upgrade to SP2.

The database pre-deployment feature can only be installed on a server running the Standard, Enterprise or Datacenter editions of SQL Server 2008 SP2, SQL Server 2008 R2 or greater.

..Also no SQL Express, although it wasn’t supported in previous App-V versions, it does work (in a Lab environment).

After installing SQL Server 2008 with SP2, the installation can proceed.

Next blog will be about converting sequences (packages) to the new format.

Leave a reply