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.