The new version of my PrepSQL tool now supports the changes that have been introduced with ServicePack 3 for App-V 5. You can silently create the App-V Management Database and Reporting Database on remote SQL servers, on SQL server clusters or in scenarios, where you can’t run App-V’s setup wizard on the SQL server machine. This new version also allows to upgrade the databases from a pre-SP3 version. It already includes the fix for a known error with Microsoft’s original scripts.
Download PrepSQL for App-V 5 SP3 from kirx.org
During the research for the App-V 5 Reporting articles I came across a variety of useful resources. I think they could be interesting for you as well.
With App-V 4, using a Profile Management or User Environment Management solution was recommended, but not highly required, as App-V managed user configurations quite OK for itself. With App-V 5 – especially in a ConfigManager scenario – this changed dramatically. Furthermore, UEM can help overcoming some of App-V 5’s most popular downsides.
Here is why I consider any UEM is a requirement for App-V 5.
Use SQL Reporting Services is the common answer to the question of how to present all the application launch data that App-V’s SQL based reporting collected. In this article you’ll not only see how to use just Excel for creating graphical reports, but you also see that you can use the pure XML based information from the previous parts of this mini-series to feed that.
In the first part of this series we talked about how to collect App-V 5 Reporting data with just a simple file share. In this 2nd part we’ll focus on how to prepare the collected data, allowing further processing.
With App-V 5 Microsoft allows to collect client reporting data also in scenarios, where neither the Native Infrastructure nor the Config Manager integration is used. In this article we discuss how to collect App-V Client reporting data just on a file share – and why this isn’t as easy as it appears to be.
Change generally happens, and so it may happen for the location of your .appv file store, too; esp. in a Native App-V deployment scenario or in a Shared Content Store mode scenario. With PackageSourceRoot you can tell the App-V Clients to get the data from a new location and to forget about the old one… particularly
About a year ago I published a Powershell script that helps preparing the App-V 5 Management and Reporting database for scenarios, where executing App-V’s setup wizard locally on the SQL server is not appropriate. The script has evolved, and a new version is available right now.
With PrepSQL for App-V 5, you can
Dowload PrepSQL v2 from kirx.org
With App-V 5 Microsoft introduced the concept of Dynamic Configurations, allowing to manage and control the way how virtual applications integrate into the base OS or how the virtual packages behave on clients. One of the main benefits of Dynamic Configurations is the ability to apply different settings to different machines or users. However, these Dynamic Configurations are applied differently, depending on the distribution model. In this article we’ll show that the old principle of “A package’s virtual resources are equal regardless of the deployment model’ has changed in App-V 5.
In short: Just having or modifying the XMLs is not enough, in no scenario!
It’s not a secret that I am a super-fan of Gridmetric’s Application Virtualization Explorer (AVE) since it was released and replaced the old SFTExplorer. Therefor I’m really happy that Kalle Saunamäki told me about the release of AVE 3.0, the first and only 3rd party editor for App-V 5 packages. Here is why you should get your hands on it, too.