Lars' System Center Blog

SCCM 2007 and App-V integration

The last year I noticed that a lot of other products got SCCM 200 integration, every time extending the functionality of SCCM 2007 and expanding the scope of this product.
I already tested the integration of Forefront Endpoint Protection 2012 you can find the step by step procedure here and also the Windows Embedded Device Manager 2011 integration read it here.
 
So let’s have a look at the App-V integration:

Configuration Manager and App-V can be integrated to provide a comprehensive deployment and update service for virtual applications. With Configuration Manager, the typical App-V infrastructure is reduced to the App-V Sequencer and Client. Configuration Manager takes the place of the publishing and streaming components in a typical App-V full infrastructure. The App-V Sequencer produces packages that can be distributed via a Configuration Manager infrastructure to the App-V Clients. This eliminates the need for two separate infrastructures to support application deployment. Configuration Manger can be used to deploy both traditional and virtual applications.

If you want more information on this you can find it the white papers here:

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

So what do you need to do for App-v integration? Honestly, when you already have SCCM 2007 R2/3 installed not a lot of work J it just 3 steps:

Configure the Advertised Programs Client Agent for Running Virtual Applications

1. In the Configuration Manager console, navigate to System CenterConfiguration Manager / Site Database / Site Management / <site code> - <site name> / Site Settings / Client Agents.
   
   
   
2. Right-click Advertised Programs Client Agent, and then select Properties.
3. On the General tab, to enable the client agent for running virtual applications, click Allow virtual application package advertisement.
   
   
   
4. Click OK to exit the properties dialog box.

Enable Streaming for Virtual Application Packages

1. In the Configuration Manager console, navigate to System CenterConfiguration Manager / Site Database / Site Management / <site code> - <site name> / Site Settings / Site Systems, and then click the name of the server.
   
   
   
2. To open the ConfigMgr Distribution Point Properties, in the results pane, right-click ConfigMgr distribution point, and then click Properties. On the General tab ensure Allow clients to transfer content from this distribution point using BITS, HTTP, and HTTPS (required for device clients and Internet-based clients). has been selected. Configuration Manager 2007 client computers that connect to a branch distribution point will run virtual application packages using SMB.
   
   
   
3. On the Virtual Applications tab, select Enable virtual application streaming.
   
   

If Allow clients to transfer content from this distribution point using BITS, HTTP, and HTTPS (required for device clients and Internet-based clients). Has not been selected you can’t change this settings.

1. To close the distribution point properties, click OK.

Attention: You need to do this on all your DP where you would like to enable application streaming!

Install the Microsoft Application Virtualization.

1. In the Configuration Manager console, navigate to System Center Configuration Manager / Site Database / Computer Management / Software Distribution.
   
   

1. If necessary, expand the Software Distribution node and select Packages. To open the Create Package from Definition Wizard, right-click Packages, and then click New / Package From Definition.
   
   
   
2. On the welcome page, click Next.
   
   
   
3. On the Package Definition page, to specify the publisher and definition for the new package, click Browse.
   
   
   
4. Locate and select the AppVirtMgmtClient.sms file. The default location for the AppVirtMgmtClient.sms file is <ConfigMgrInstallationPath> \ SMS \ Tools \ VirtualApp \ AppVirtMgmtClient.sms. The Name, Version, and Language associated with the specified .sms file are displayed in the Package definition pane.
   
   
5. Click Next.
   
   
   
6. On the Source Files page, select Always obtain files from a source directory to help ensure the latest version of the client software will be available, and then click Next.

1. On the Source Directory page, specify the directory that contains the source files for the package. This is the directory that contains the Microsoft Application Virtualization Desktop Client or the Microsoft Application Virtualization for Terminal Services installation file depending on the version of the client you are planning to install. Specify the source location by providing the UNC path. Alternatively, click Browse to specify the location that contains the setup files for the type of client you want to install. Click Next.
   
   

Remark: here I browsed to the sources of the App-V client 4.6 SP1 that I downloaded earlier.

1. On the Summary page, review the Details for the package definition file. To create the package definition file and close the wizard, click Finish. To access the new package select the Packages node and the package will be available in the results pane.
   
   
   
2. I selected the Microsoft Application Virtualization 4.6 SP1 Client sources, so after the package has been created, I selected the Packages node, right-clicked the package in the in the Results pane and selected Properties. On the General tab, I updated the Name of the package so that it reflects that it is the 4.6 SP1 version of the client.
   
   

Now your SCCM infrastructure is ready to start streaming App-V packages J

There’s video with a pretty girl that the shows you most off this here:

http://technet.microsoft.com/en-us/windows/hh463534

Keep it Clean!

Lars Verbist
twitter: @LarsVerbist