App-V on Anything About IT

PowerShell - Retrieve App-V 4.6 Package Information

Mon, 02 Dec 2013 21:44:12 +0000

Today we’ve been looking at App-V 4.6 package settings before and after migrating them from ConfigMgr 2007 to ConfigMgr 2012, so after opening the App-V mmc console 3x manually…..another script was born.

The below Get-Appv4PkgInfo.ps1 script retrieves information from the App-V Package WMI class. You can run the script against one or more computers and the optional –View parameter lets you define what information you want to see.

<#
.Synopsis
 Retrieve local App-V 4.6 Package information
.DESCRIPTION
 Retrieve local App-v Package Information from root\Microsoft\appvirt\client
.PARAMETER Computer
 One or multiple computernames
.PARAMETER View
 Specifies the information that is displayed for the identified App-V Package
 Valid options for the view parameter are Default,Path, Cache, Inuse, Size, GUIDS, Locked,All
.EXAMPLE
 Get-Appv4PkgInfo.ps1 -Computer TestClient1, TestClient2

 Shows the same output as when providing the -View Default parameter

.EXAMPLE
 Get-Appv4PkgInfo.ps1 -Computer TestClient1 -View Default

 Computer AppVname Version 
 -------- -------- ------- 
 TestClient1 SCCM Client Center 2.0.4.1 x64 R1 5

.EXAMPLE
 Get-Appv4PkgInfo.ps1 -Computer TestClient1,Testclient2 -View Path 
 
 Computer AppVname SFTPath 
 -------- -------- ------- 
 TestClient1 SCCM Client Center 2.0.4.1 x64 R1 FILE://c:\windows\ccmcache\7\sccm client.
.LINK
 http://technet.microsoft.com/en-us/library/cc843631.aspx
.NOTES
 Version 1.0, by Alex Verboon
#>
[CmdletBinding()]
Param(
 [Parameter(Mandatory=$true,
 ValueFromPipelineByPropertyName=$true,HelpMessage="Enter Computername(s)",
 Position=0)]
 [Alias("ipaddress","host")]
 [String[]]$Computer, 

 [Parameter(Mandatory=$false,
 ValueFromPipelineByPropertyName=$true,HelpMessage="Select the type of information to display",
 Position=1)]
 [ValidateSet("Default","Path","Cache","Inuse","Size","GUIDS","Locked","All")] 
 $View="Default"
)

Begin{}

Process{
$appv =@()
ForEach($c in $Computer) 
{
 $applications = get-wmiobject -ComputerName $c -query "SELECT * FROM Package" -namespace "root\Microsoft\appvirt\client" -ErrorAction SilentlyContinue
 ForEach($app in $applications)
 {
 $object = New-Object -TypeName PSObject
 $object | Add-Member -MemberType NoteProperty -Name "Computer" -Value $c
 $object | Add-Member -MemberType NoteProperty -Name "AppVname" -Value $app.Name
 $object | Add-Member -MemberType NoteProperty -Name "Version" -Value $app.Version
 $object | Add-Member -MemberType NoteProperty -Name "SFTPath" -Value $app.SftPath
 $object | Add-Member -MemberType NoteProperty -Name "PackageGUID" -Value $app.PackageGUID
 $object | Add-Member -MemberType NoteProperty -Name "VersionGUID" -Value $app.VersionGUID
 $object | Add-Member -MemberType NoteProperty -Name "Locked" -Value $app.Locked
 $object | Add-Member -MemberType NoteProperty -Name "LaunchSize" -Value $app.LaunchSize
 $object | Add-Member -MemberType NoteProperty -Name "InUse" -Value $app.InUse
 $object | Add-Member -MemberType NoteProperty -Name "CachedSize" -Value $app.CachedSize
 $object | Add-Member -MemberType NoteProperty -Name "CachedPercentage" -Value $app.CachedPercentage
 $object | Add-Member -MemberType NoteProperty -Name "CachedLaunchSize" -Value $app.CachedLaunchSize
 $object | Add-Member -MemberType NoteProperty -Name "TotalSize" -Value $app.TotalSize
 $appv += $object
 } # end foreach application
} # end foreach computer
} # end process 

End{
# Define the properties to display based on -View parameter option
switch($view)
 {
 Default {$selcol = "Computer", "AppVname","version"}
 Inuse {$selcol = "Computer", "AppVname","Inuse"}
 Size {$selcol = "Computer", "AppVname","LaunchSize","TotalSize"}
 Cache {$selcol = "Computer", "AppVname","CachedSize","CachedPercentage","CachedLaunchSize"}
 GUIDS {$selcol = "Computer", "AppVname","PackageGUID","VersionGUID"}
 Path {$selcol = "Computer", "AppVname","SFTPath"}
 Locked {$selcol = "Computer", "AppVname","Locked"}
 All {$selcol = "*"}
 }
$appv | Select-Object -Property $selcol 
}

PowerShell Script–Set App-V 4.6 Cache Size

Fri, 29 Nov 2013 18:13:07 +0000

Background: As part of our migration process from Configuration Manager 2007 to Configuration Manager 2012 R2 we also adjust the App-V Cache Size that is currently set to 6GB to 11GB because the ConfigMgr Agent Cache is set to 10GB, this by following the best practice described in Microsoft’s whitepaper Virtual Application Management with Microsoft Application Virtualization 4.5/4.6 and System Center Configuration Manager 2007 R2**** where it says.

“The App-V Client cache free disk space threshold parameter should be set to ensure that the available disk space on the client PC is at least 1 GB larger than the Configuration Manager Client cache size.”

App-V Management Server Setup and SQL Server Configuration

Sun, 14 Mar 2010 00:01:02 +0000

During the Installation of the App-V Management Server on a Windows Server 2008 with SQL Server 2008 Express installed I ran into an problem specifying the database server and got an error as shown in the picture below.

The installation program could not connect to the configuration data store. Please see the installation log file for more information.

I solved the problem by opening the SQL Server Configuration Manager and enabled TCP/IP in the SQL Server Network Configuration options.

App-V Visio Stencil

Sun, 07 Mar 2010 16:06:55 +0000

Just found a nice Visio Stencil for App-V on Kirx.org. Well done ! Get the stencil from kirx.org

ReadTip: Choosing the right App-V Delivery Model

Thu, 04 Mar 2010 23:58:08 +0000

If you’re planning on deploying App-V, but still busy with thinking of how you will get the virtualized applications to your end users I strongly recommend that you read the whitepaper “Choosing the right App-V Delivery Model” from Ment van der Plas.

The document provides an excellent overview of the different App-V delivery scenarios and their pros and cons.

Configuring App-V Standalone Mode through Group Policy

Tue, 02 Mar 2010 00:17:58 +0000

If you plan to use the Microsoft App-V Stand-Alone Mode some Registry Settings are required for the Application Virtualization Client as described in detail on this App-V site here. But instead of setting these registry keys manually or through a custom script, you can also manage these settings through Group Policy.

First download the Microsoft Application Virtualization Administrative Template (ADM Template). The ADM Template provides configuration options for the App-V 4.5/4.6 Client settings such as Client Permissions, Client Interface behavior and Client Communication Settings.

ViewTip: Application Virtualization (App-V) Video Series

Mon, 22 Feb 2010 21:15:12 +0000

Learn how to configure App-V; create, publish, and update virtual applications; and create and manage policies for virtual applicationss. The videos can be downloaded from here

4 Great App-V videos

Wed, 23 Dec 2009 13:31:56 +0000

I’m just about to expand my knowledge a bit around App-V. I haven’t done any hands-on yet, because I usually first focus on gathering all the useful resources available on the net, and then start reading these. By doing so, I found these fantastic videos on The Blogcast Repository.

Deployment Scenarios with App-V 4.5 Planning Considerations before Implementing App-V 4.5 The App-V Client (part 1) The App-V Client Part 2- Deep Dive

By the way, if you are not familiar with The Blogcast Repository but like video based trainings, have a look at the Repository, there is lots of other Microsoft related Technology training material there.