application virtualization with microsoft app-v

APPLICATION VIRTUALIZATION WITH

MICROSOFT APP-V

Robert Bourque – Senior Support SpecialistAran Gilmore – Senior Support Specialist

Installing the App-V Management ServerImportant information for SQL Admins and

Systems Administrators Installing the App-V ClientSequencing an applicationScripting with App-VReal world comparisonPotential future uses

AGENDA

Small liberal arts college in Boston, MA near Fenway ParkRoughly 1800 undergraduate and 2800

graduate studentsApproximately 1800 computers in classrooms,

labs, and staff/faculty75% PC (Dell) / 25% MacIncluding two dual boot classrooms and 15

dual boot public space computersRoughly 6000 users total

SIMMONS COLLEGE

App-V Components

App-V Client – This is the application that runs on the end-user computer to contact the server and provision the applications

Sequencer – This refers to the machine on which you “sequence” the applications.

This computer should be as basic an installation of the OS as possible

App-V Management Server

Installing App-v Management Server

To be provided to SQL administrators

Installers\Server\Management\Support\SQLServer\CreateDB\Create_Tables.bat

Server\Management\Support\SQLServer\CreateDB\Create_Schema.bat

Name of AD group that is going to be the App-V administrators

Name of the server where App-V Management Server will be installed

Installing App-v Management Server

To be returned to the App-V administrators

Name of the database server or instance and the name of the App-V database

Once the database has been prepared, the App-V administrators can run the App-V installation without SQL administrator privileges.

Sequencing Overview

Copy the application installer locally to the App-V sequencer

Start the sequencer

Start Monitoring Install the application

Test the application

Configure any settings (if required)

Stop Monitoring

Test the virtual application

Save the package and upload to the App-V Server

Microsoft Application Virtualization 4.6 Sequencing Guide – Chapter 8.1

The Welcome Screen is new in App-V 4.6 and provides quick access to the common tasks of creating, editing, and upgrading a package.

App-V Sequencing Guide


Creating a package starts with providing information about the package. The picture and table below describe the different options that are available.



When advanced options are selected in the package information screen, the Sequencer will be presented with options for Microsoft Update and Rebasing DLLs.



Monitor Installation


Microsoft Application Virtualization 4.6 Sequencing Guide – Chapter 8.4.1

Applications that require a reboot

Some applications will require a reboot of the operating system after installation to accommodate files that are in use during installation that need to be replaced. The Sequencer is aware of reboot tasks and the operating system will not need to be rebooted.

Microsoft Application Virtualization 4.6 Sequencing Guide – Chapter 8.4.1

While sequencing an application that requires a reboot, perform the following tasks:

When prompted, select to reboot. The Sequencer will capture this request and the machine will not restart.

Next select Stop Monitoring from the Sequencer.

Then select Begin Monitoring again. All of the reboot tasks will be processed once the Sequencer starts monitoring again.

Proceed with additional installations or click Next if no additional installations are required for the package.


Configure Applications



Launch Applications



Package Deployment



Saving the Package


Sequencing Web based Applications and Plug-ins

Internet Explorer is NOT supported as a sequenced application. However, you can sequence plug-ins or ActiveX controls for Internet Explorer.

Sequencing Web based Applications and Plug-ins

Begin the normal procedure for sequencing an application.

When it comes time to install the web app, install it normally via a package or go to the appropriate Web site to get the app.

On the “Configure Applications” page of sequencing add a shortcut and point to the local Internet Explorer (i.e. C:\Program Files\Internet Explorer\iexplore.exe).

After the Iexplore.exe enter the web site that you want to launch (i.e. http://www.microsoft.com).

Finish sequencing the package normally.

Sequencing


When you save your package you will have several files. The following is a list of those files and descriptions of each of them.

Installing the App-v Client

Software Deployment

Must install prerequisites first.Microsoft Visual C++ 2005 SP1

Redistributable PackageMicrosoft Core XML Services (MSXML) 6.0

SP1Microsoft Application Error Reporting

Group Policy Startup Script

Silent switch automatically installs prerequisites. Appv_client_setup.exe /s /v/qb

For setting communication, client interface, and permissions preferences (including the definition of a publishing server) you can use command line parameters, run a .reg file, or a GPO.

Group Policy Preferences

Installing the App-v Client

Script Timing and Events

PRE STREAM

POST STREAM

PRE LAUNCH

POST LAUNCH

POST SHUTDOWN

Scripting within App-V

Script Timing and Events continued

Protect

Protect=TRUE (script runs inside virtual environment)

Protect=FALSE (script runs outside virtual environment)

Timeout

Timeout=xx (wait xx seconds for script to complete before reporting error)

Timeout=0 (wait indefinitely for script to complete)


Script Timing and Events continued

WaitWait=TRUE (wait for script to complete

before continuing)Wait=FALSE (do not wait for script to

complete before continuing)


Scripts can be written in any language but their language must be installed locally on the client machine. For example if they are using PERL, the PERL runtime must be locally installed on the client machine.


There are two different methods for running scripts. The <SCRIPTBODY> tag and <HREF> tag:

HREF – Normally used when executing a single command

SCRIPTBODY – Used when needing more complex operations and/or multiple commands to be run.


<SCRIPTBODY>

Can call non-executable commands (md)

Creates a temporary script on the client, which executes and is then deleted

Uses escape ( \ ) character

DOS window appears


<HREF>

Used to call direct executables (xcopy)

No non-executables permitted

Command is executed directly on the client

No DOS window appears


OSD scripts can be useful for administration and are sometimes needed to get an application to function properly.

Example 1: Abort launching the virtual application if certain conditions are/are not met (i.e., Specific computers, time range, etc.).



OSD File:<DEPENDENCY><SCRIPT TIMING="PRE" EVENT="LAUNCH" PROTECT="TRUE" WAIT="TRUE" TIMEOUT="10" SUCCESSRESULT="1" ABORTRESULT="0"><HREF>\\APPV\Content\ALTOVA\cname.bat</HREF></SCRIPT></DEPENDENCY>Cname.bat:IF %COMPUTERNAME:~0,8% == LEF01201 exit 1IF %COMPUTERNAME:~0,8% == LEF01202 exit 1IF %COMPUTERNAME:~0,8% == LEF01203 exit 1IF %COMPUTERNAME:~0,8% == LEF01204 exit 1IF %COMPUTERNAME:~0,8% == LEF01205 exit 1exit 0::Computer name must be in caps

This example runs an external batch file to make sure the computer name is allowed to run the application.


OSD XML Syntax CheckTo check the XML format of an OSD file, change the .OSD file extension to .XML and drop the .XML file into an Internet Explorer window. If there are any open or missing tags the file will not be displayed.Note: XML file editors such as XML Notepad can also be used to check XML file format

March 2008 – need to deploy new Meeting Maker versionServer/Client functionality requires that the versions

of both be made live at the same time.

Packaged installation of specific application version as an msi.

Deployed via Group Policy Software Installation

Required at least one reboot initiated by the user, and in some instances two or three.

Real world ComparisonGPO software distribution v. App-V

March 2009– need to deploy new Meeting Maker version…again

Created a GPO to deploy the App-V Client –This was done more than a week prior to the Meeting Maker deployment.

Sequenced the application, configured it in the App-V Management Console.

Tested the deployment to a limited user group (Helpdesk)


Once server had been made live, we simply checked the box to publish the application to the user group “Domain Users”

The following morning users found a shortcut on their Desktop and Quick Launch tray for the new version of Meeting Maker

App was loaded the first time it’s opened

Network traffic was monitored and no issues were found


Frequently updated software

General Access Software

especially apps specific to a room

Apps that faculty request…after the semester has started

Class/department specific software that will be able to “follow” the user to any PC on campus.

Future Implementations

ResourcesPrescriptive Guidance for sequencing Microsoft Office 2007http://support.microsoft.com/kb/939796

Prescriptive Guidance for sequencing Microsoft Office 2010http://support.microsoft.com/kb/983462

Application Virtualization Documentationhttp://technet.microsoft.com/en-us/appvirtualization/cc843994.aspx

How to Configure the App-V Client Registry Settings by Using the Command Linehttp://technet.microsoft.com/en-us/library/cc843710.aspx

Application Virtualization Client Installer Command-Line Parametershttp://technet.microsoft.com/en-us/library/cc843737.aspx

App-V Administrative Templatehttp://www.microsoft.com/downloads/details.aspx?FamilyID=67CDF9D2-7E8E-4D76-A552-FD82DBBFF9BC&displaylang=en

Group Policy Preferences: Getting Startedhttp://technet.microsoft.com/en-us/library/cc731892(WS.10).aspx

http://support.microsoft.com/kb/939796�



http://technet.microsoft.com/en-us/appvirtualization/cc843994.aspx�

http://technet.microsoft.com/en-us/library/cc843710.aspx�

http://technet.microsoft.com/en-us/library/cc843737.aspx�

http://www.microsoft.com/downloads/details.aspx?FamilyID=67CDF9D2-7E8E-4D76-A552-FD82DBBFF9BC&displaylang=en�

http://www.microsoft.com/downloads/details.aspx?FamilyID=67CDF9D2-7E8E-4D76-A552-FD82DBBFF9BC&displaylang=en�

http://technet.microsoft.com/en-us/library/cc731892(WS.10).aspx�

application virtualization with microsoft app-v

Documents