Version 2.5.0 November 5, 2013
AppV_Manage is a free tool designed to be used for stand-alone client virtual application deployment and especially for the debugging of new virtual packages.
App-V Manage allows you to add and publish virtual applications to an App-V 5 client from a GUI interface, instead of powershell.
It is the fastest way to get a newly sequenced application tested and debugged.
It works no matter how you like to deploy your virtual packages, via the App-V Server, SCCM, or Stand-alone Client.
Most of your use of the tool will be with a stand-alone client to add and debug newly sequenced packages,
but it works well anywhere you have admin rights.
Download links and version changes are located at the bottom of this page.
Demo: 13 minute Video
The software has a single MSI installer that will install the appropriate bitness of the tool.
The only requirement is DotNet 4.0, which you already have if you installed the App-V Client.
When you launch the tool, it uses powershell and other system interfaces to analyze the configured package store and the App-V client as well.
The initial display shows the package store and which applications have already been added or published.
The publishing tab shows you all of the packages under the folder configured for package storage.
From this tab you can add and publish these packages to the client.
You can use the refersh button to re-read everything on request at any time.
Select any of the packages in this display to see details and your options. You can add and remove packages, publish and unpublish, and request a package repair.
Options not currently available are disabled; keep in mind that you cannot repair,unpublish, or remove a package when in use,
including group usage.
You can add a package to the client with or without the DeploymentConfiguration file.
The config files must be located in the same folder as the App-V file.
If you request to publish with the config file and there is more than one DeploymentConfig file present, you are prompted to choose which one you want to use.
Once the package is added, information about the package is available to view in the lower window.
The dark line is a splitter which you can use to change the size of the upper/lower windows. All of the "Extensions" are visible from here!
Publishing may be done globally, or for the current user.
When publishing globally, the App-V client does not support the use of a UserConfig file.
When publishing to the current user, you have three options.
The "Client Packages" tab shows details on packages that have been added to the client.
This tab shows the packages that have been added to the client.
The information panel at the bottom shows information such as applications and connection groups that the package is part of.
The panel also shows where any cached xml files, including the AppXManifest file from the package and any Dynamic Configuration files that may be in use for the package as published, are located.
You may right-click on any of those files to view the file contents, which appear as shown below:
The "Connection Groups" tab shows the details of any Connection groups.
You can also create and remove groups when necessary.
Once the packages are set up with the client, the "Debug Packages" tab is where package debugging takes place.
Click on a package and select your tool.
The tool displays client configuration. There are a few Client Configuration items that you can change the configuration of.
Right click on a row and if modification is supported by the tool, a menu appears with your options.
This can also be useful if you don't remember what AutoLoad value of 1 means.
If a publishing server is defined, you can test the connection and see the XML output of the Publishing Server,
either as the current user or system (Global/Machine publishing).
The tool makes extensive use of the App-V Client Powershell API.
"PowerShell Results" tab shows you all of the powershell commands executed, and a summary of the results.
The tool pulls events from the three primary Windows Event Logs for App-V.
If you try something and it doesn't work because the client rejected the request, check here to find out why.
From this page you can manage and view events from the "Secret Hidden App-V Debug Event Logs".
Right click on a log to enable/disable the log, or view the events.
From this page you can change the Package Store UNC path, as well as the Debug Log level for this tool.
You can also clear out the debug log to make it easier to find your next issue.
Version information is supplied about the OS, App-V Client, and this tool.
TMurgent believes in giving back to the community. AppV_Manage is free for for use./p>
The tool makes use of published APIs, when applicable, but also uses some unpublished interfaces, to obtain information or request system modifications.
Anywhere the App-V Client works.
TMurgent has a bunch of tools on this page. Usually they are free, unless you are a Software Vendor.
Tools for performance have a segregated list here.
Version 184.108.40.206 The publishing tab now displays in internal manifest file, as parsed using the latest schema and displays it as a tree when you select one of the packages.
This exposes all of the package details, especially of the extensions.
Version 220.127.116.11 The publishing tab now supports dynamic configuration files when adding or publishing a package.