Transcript Document

Microsoft Application Virtualization
(App-V) ver 4.5 overview
Nguyen An Que
Microsoft Vietnam
Email: [email protected]
Tech blog: blogs.technet.com/quenguyen
Download URL:
http://blogs.technet.com/quenguyen/archive/2009/11/12/
application-virtualization-app-v-version-4-5.aspx
What is MDOP?
Microsoft Desktop Optimization Pack
MED-V = Microsoft Enterprise Desktop Virtualization
App-V = Microsoft Application Virtualization (formerly SoftGrid)
For desktop OS software assurance (SA)
Exception: App-V for RDS (Remote Desktop Services) can be bought as
Open License
From Data Center to Desktop
Server
Presentation
Application
Desktop
VECD
Enterprise Challenges in the desktops
Deployment, Upgrading, Terminating of applications
Application-to-Application compatibility issues
Regression Testing
Application Patch Management issues
App/OS Model Comparison
Traditional App/OS Model
Microsoft Vision – App/OS Model
(2007 + beyond)
Microsoft Application Virtualization (App-V)
Run applications without
even installing it locally
Eliminate Application-toApplication Compatibility
issues
Run same application with
different versions on same
PC/Terminal Server
Manage your applications
centrally
Set the Application
Permissions/Licenses
Upgrade applications centrally
Office
2003 and
2007
running
together…
…applies to custom applications as well
Microsoft Application Virtualization (App-V)
Java 1.5 for
Application 2…Java
1.6 for Application 1
Applications will still be published
seamlessly…
Virtualized application
icons will show in the
desktop so users can run
them (like what they’re
used to).
But applications are never
installed (no Client Footprint)!
A note on the application performance…
App-V enabled applications will have little difference with the
performance (negligible) of a local installation
Remember the process will still run locally on the desktop…not
on the server
Does not need to make any investment to upgrade existing
desktops or laptops
The Application Management Problem…
Users
Support
Remedy
Clarify
Clearcase
Clearquest
Office XP
Access 97
Java 1.4.2_04
Legal
Documentum
Abacus Law
Westlaw
Office XP
Shepards
Java 1.3.1_02
Java 1.4.2_04
Executives
Remedy
Clarify
Documentum
Office XP
SAP
Java 1.4.2_04
Designers
AutoCAD 2004
AutoCAD 2002
Prometric
DesignPro
Visio 2003
Project 2003
Java 1.4.2_04
Java 1.3.1_02
N+ Groups
As needed
Provide Desktop Sharing…
With App-V, users can now
share the same desktop
machine.
Users will only see their
respective applications
assigned to them.
Desktops will become more
generic instead of user/group
specific.
App-V Components
App-V Sequencer
App-V Server
App-V Streaming Server
(new in 4.5)
App-V Client
Sequencing Overview
Same steps as installing your desktop application
Imagine it is like a CD recorder…will just monitor the installation
High-Level View:
Copy the application installer on 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
Sequencing – 7 easy steps
Step 1: Provide Suite name (no spaces and dot).
Step 2a: Begin Monitoring. This would prompt you where to
save temporary files. You should save this in Q:\<Folder>. Folder
name should follow 8.3 standard.
Correct: Q:\AdRdr.007
Not Correct: Q:\Adobe Reader
Step 2b: After selecting the above folder, the Sequencer GUI
will be minimized and you can now install the application.
Install the application as you would normally do on a desktop
(exactly the same steps).
Sequencing – 7 steps (cont)
Step 2c: After the installation, test the application to ensure
that everything is fine.
Example: If you sequenced WinRAR, you may want to run and launch
winrar.exe to ensure that everything is fine and no errors.
Step 2d: When you testing is finished, click Stop Monitoring.
Step 3: Add additional files not captured by the monitoring.
Normally you would just click Next here.
Step 4: Specify application shortcuts. Remove unnecessary
shortcuts created during the sequencing.
Step 5: Launch Virtual Application. After launching the
applications and last minute testing, you can click Next.
Step 6: Just click Next
Sequencing – 7 steps (cont)
Step 7: Click the deployment tab and configure the following:
The path should be equal to the Suite Name (from Step 1).
Provide the server name and change to RTSP. Ensure port is 554. You can
only use RTSPS if you have configured the necessary certificates on the
server.
Add the Operating Systems that the application is required to run by
clicking the arrow toward the Selected Combo box.
Save package.
Create a folder (same as Suite Name and the Path).
Save the package inside the created folder.
Save sprj file same name as Suite Name.
App-V Sequencing Limitation
Not all applications can be sequenced. First of all it is only
meant for desktop applications. It cannot be used to sequence
server applications.
Supported: Sequence SAP front end, Oracle Client, SQL Client, etc.
Not supported: SQL Server, Oracle Server, MSDE, etc.
Which applications that can be sequenced or cannot be
sequenced???
70% of desktop applications can easily be virtualized
20% may require advanced sequencing in order for it to be virtualized
(i.e. by using “recipes”, running some scripts, etc)
10% maybe impossible to “virtualized” such as anti-virus, VPN client (i.e.
applications that uses system specific drivers)
App-V Sequencing Limitation
You are not expected to sequence all your desktop applications
Remember not all applications can be virtualized!
Use the 60/40 rule
Example: 60% are locally installed, while 40% are virtualized
Example: 40% are locally installed, while 60% are virtualized
If you already has ConfigMgr in place, strongly consider using
ConfigMgr infrastructure to manage App-V.
There’s no “one size fits-for-all” kind of thing…it really depends
on environment and requirement.
Which OS to sequence the application…
If application can work in both XP and Windows 7, sequence it
to the lowest OS (XP)
In some cases, you may need create package…one sequenced in
Windows 7 and the other sequenced for XP.
Note that 4.5 does not support Windows 2000
Active Upgrade feature in App-V
Upgrade application patches seamlessly
LAB: Create upgrade file for Adobe 7.0 (using patch 7.1)
Step 1: Copy Adobe folder (from content) to the Sequencer machine.
Step 2: Open Sequencer-> New Package Upgrade.
Step 3: Open the sprj file
Step 4: Extract the package to Q:\. No need to create folder.
Step 5: Begin Monitoring. Install the patch. Stop monitoring.
Step 6: Launch virtual application to test it.
Step 7: Save package.
Copy PKG_NAME_X.sft to the content Adobe folder in the
server.
Under Adobe package (Packages), right click and Add Version.
Scripting within App-V
Run Scripts before or after launching the applications
Example: Open cmd prompt or run task kill command.
Example: Abort launching the virtual application if certain conditions are
not met (i.e. can only use the application during office hours).