| AppV_SelfService |
All new client tool for App-V 5. May be used as a self-service portal, or as a way to automaticaly apply packages without servers. |
|
Updated August 4, 2013 (version 2.0.0.0)
Two uses:
- As a "Self-Service" app that allows users to add pre-authorized App-V packages to their client without admin credentials.
- As a simple replacement for the App-V Management/Publishing server or SCCM. Or using Automatic distribution and updates of packages with just
a file share and (optinoally) an Active Directory OU.
|
|
| AppV_DefConGroups |
Create and Manage Connection Group Files for App-V 5. |
|
Updated July 2, 2013 (version 1.0.1.0)
Demo: 8 minute Video
For use with virtual MSI deployment (e.g.: SCCM 2007) and with upcoming version of AppV_SelfService (version 1.5).
|
|
| AppV_Manage |
All new client tool for App-V 5. The fastest way to test and debug your new packages. |
|
Updated Nov 5, 2013 (version 2.5.0.0)
Demo: 13 minute Video
No need to mess with PowerShell! Just a slick GUI tool to do all the work.
|
|
| PublishFromAppV |
All new tool pulls App-V 4 and 5 apps and publishes to XenApp 6.5. Independent of how you publish to the App-V Clients. |
|
Updated March 1, 2013 (BETA version 2.9.0.0)
No need to mess with PowerShell or long GUID encrusted paths for icons! Just a slick GUI tool to do all the work.
|
|
App_Remediation (Zipped)
Solves issues with App-V 5 in roaming like environments for apps that save settings and data to non roaming locations.
See this page for more information. Updated Apr 7, 2013. |
Connection Group Schema XSD (Zipped)
To add a connection group to the App-V Client, you need to create an XML file defining the group. Microsoft has not
properly documented the format, so we created this XSD file that can be used in an XML editor to create and/or validate
the syntax. Updated Nov 20, 2012. |
AppV Manifest Schema XSD (Zipped)
The AppXManifest.xml file is generated by the sequencer and stored internal to the App-V file.
The AppxManifest file contains the complete package definition for applications and extension points. Portions of the contents of the AppXManifest file
may be overridden by either DeploymentConfiguration or UserConfiguration files.
Microsoft has done a half-hearted job to define the syntax in the external config files, with more of an example than definition,
but have not defined the format of the internal AppXManifest file at all. While very similar, there are many things in the AppXManifest
file that have not been seen in the external config files. Additionally, the syntax changes on a few items.
This is a work-in-progress, currently built using information from about 80 different packages.
This XSD file that can be used in an XML editor to create and/or validate the syntax.
Updated Mar 25, 2013. |
DeploymentConfig Schema XSD (Zipped)
The DeploymentConfig.xml file is generated by the sequencer for you to modify when you want to alter the way the package
integrates with the system. The DeploymentConfig makes systemwide changes.
Microsoft has done a half-hearted job to define the syntax, with more of an example than definition; this is a more serious
attempt to provide a concrete definition. This is a work-in-progress, as portions of the definition not properly documented
are yet to be understood.
This XSD file that can be used in an XML editor to create and/or validate the syntax. It is known to not work with NotepadXML
for some unknown reason, however the files output by the sequencer appear to have xml validation issues against many validation
tools, even without this schema.
Updated Nov 26, 2012. |
UserConfig Schema XSD (Zipped)
The UserConfig.xml file is generated by the sequencer for you to modify when you want to alter the way the package
integrates with the system. The UserConfig makes changes on a per-user basis.
Microsoft has done a half-hearted job to define the syntax, with more of an example than definition; this is a more serious
attempt to provide a concrete definition. This is a work-in-progress, as portions of the definition not properly documented
are yet to be understood.
This XSD file that can be used in an XML editor to create and/or validate the syntax. It is known to not work with NotepadXML
for some unknown reason, however the files output by the sequencer appear to have xml validation issues against many validation
tools, even without this schema.
Updated Nov 26, 2012. |
Test_Directory
A simple tool to look at what parts of the App-V files are cached. |
VC Versions
A list of known VC Runtime version numbers and installers, including mapping to KBs.
This is a really useful mapping for when you catch one of these in your package;
you can use it to figure out exactly what the prerequisite is.
See this blog article for explanation. |
MSXML Versions
A list of known MSXML Runtime version numbers and installers, including mapping to KBs.
This is a really useful mapping for when you catch one of these in your package;
you can use it to figure out exactly what the prerequisite is. |
ScriptLauncher
Program to parse environment variables and then launch resulting command line. Solves issues with App-V 5 scripting engine.
Click on the link to learn more. |
xPerf Profile for App-V 5 Client
WPRP configuration file for xPerf that integrates the App-V Client debug log events into the capture. Great for app issue captures at the App-V client. |
App-V 5 File I/O Analysis
Analysis of the App-V 5 file I/O activity. |
Most are zip files of stand-alone programs that need no installer, some have installers.
TMurgent believes in giving back to the community. These tools are free for for use by all.