APP-V FOR TERMINAL SERVERS

What’s New In

Tim ManganKahuna: TMurgent Technologies LLPhttp://www.tmurgent.comMicrosoft MVP for Application VirtualizationPresident, Virtualization Boston

http://www.virtg.com

Agenda What is Application Virtualization? Who are the Players? New

Licensing Impact of the Microsoft RDS CAL Server 2008 R2 is 64-bit Only App-V Without a Server Infrastructure

What is Application Virtualization?

Server Farm

Thousands of UsersTens of

4

But software…

…can be full of holes

Concept: State Separation

Operating

System

App 1

App 3

App 4

App 2

Operating

System

App 1

App 3

App 4

App 2

App to OS

App to OS &

App to App

App to OS

App to App

UserA

PrefsUser

B Prefs

UserC

Prefs

Operating

System

App 1

App 3

App 4

App 2

State Separation

Who is in the App Virt Space?

Microsoft App-V

App-V for Terminal Services (RDS)

App-V for Windows Desktops (Part of MDOP)

Warning: I am going to talk about

Licensing.

How to get App-V for ”free”.

For Information Only; verify with Microsoft on details

Updated Licensing for TS

Sold by App-V CAL (Client Access License)

Server 2008 R2 RDS CAL: includes App-V CAL Server 2008 TS CAL: grandfathers App-V

in! Server 2003 TS CAL: no such luck! Exchange:

“Old” App-V TS CALs for “New” 2008RS RDS CALs at 4x1 If SA is current on old CALs as of 9/09

New

Understanding CALs

Server 2003 with TS Server 2008 with TS Server 2008 R2with RDS

2003 TS CAL 2008 TS CAL 2008 R2 RDS CALRequires separate App-V for TS CAL

App-V for TS CALincluded

App-V for TS CALincluded

How does App-V for TS Work?

Virtual Applicatio

n

X

Group Policy

User ProfileVirtualization Settings

Package VirtualizationSettings

Windows Registry

Files (Data)

Non virtualizedApplications, Services, dlls, and COM components

Three ways to Deploy1. Dedicated Infrastructure

App-V Management Servers and DatabasePublish virtual apps per user (group)Automatic updatesMetering & License checks supported

2. Shared InfrastructureUses existing SCCM Servers and DatabasePublish virtual and non virtual apps per deviceApplication updates possibleNo metering or license check of app usage

3. Stand-alone ClientNo back end infrastructure requiredPublish virtual apps per deviceUpdates are uninstall, reinstallNo metering or license check of app usageWraps Virtual App into an MSI for Deployment

The “New” Way to Deploy

4. Stand-alone Client With StreamingNo back end infrastructure requiredDeploy virtual apps per device,Publish virtual apps per user.Central Updates (“Active Updates”)No metering or license check of app usageUses Active Directory for User

Assignment

BOLD items are differences from #3

Step 1: Prepare Apps Sequence as always Save Package in a folder of same name Copy to central File Share

Step 2: Prepare TS Install App-V Client in “Stand-Alone” Mode

with Streaming AllowStreamingFromFile = 1 RequireAuthorizationIfCached = 0 LimitedDisconnectedMode = 0

Give User Rights to “Publish App” Needed for logon script

Install AppV_DeployApp Configure Server Share Configure Application OU

Add AppV_Publish to user login script

Step 3: Authorize Apps Create an “Organization Unit “ (OU) in

A.D. Create a user group for each package Package names much match sequence

package Assign users as members of package

group This step typically carried out by many

people

Step 4: Deploy & Publish Use AppV_Deploy to add virtual app to

terminal server AND load cache (without /GLOBAL)Now…

As users log in, application shortcuts and FTAs are published to their account.

Later…Update package by copying updated pkg.Can use “Soft-link” to eliminate downtime

Demo

LinksHere are some

links to Microsoft sites and pages

most relevant to this topic.

App-V on TechNet:http://technet.microsoft.com/en-us/appvirtualization/default.aspx

Remote Desktop Services Team Blog:http://blogs.msdn.com/rds/archive/2009/09/04/what-s-the-difference-between-a-rds-cal-and-a-ts-cal.aspx

Remote Desktop Services Licensing:http://www.microsoft.com/windowsserver2008/en/us/rds-product-licensing.aspx