locked
App-V reporting RRS feed

  • Question

  • From the reporting point of view, what are the exact feature gain/lost by integration with SCCM compare to having a Full Infrastructure?
    Wednesday, June 24, 2009 5:16 PM

Answers

  • Hello,

    Well, the documentation for SCCM R2 says this;
    • Reporting of virtual application distribution and usage is limited to the capabilities described in this document.  Depending on which Configuration Manager virtual application delivery method is chosen, some options limit reporting further compared to the reporting features that are provided by a full Application Virtualization 4.5 infrastructure.  For example: when using local delivery (download and execute), it is not possible to report on how many times an application has been used, only that it has been used and the “last launch date.”

    Reporting includes this;
    • Configuration Manager R2 includes the following built-in reports that can be used to report the status of virtual application distribution throughout the Configuration Manager hierarchy and virtual application delivery to Configuration Manager Clients:
    o All distribution points with virtual application streaming enabled
    o All virtual application packages in the streaming store of a distribution point
    o Computers with a specific virtual application
    o Computers with a specific virtual application package
    o Count of all instances of virtual application packages
    o Count of all instances of virtual applications
    o Streaming store distribution status of a specific virtual application package
    o Virtual application launch failures for a specific application
    o Virtual application launch failures for a specific computer
    o Virtual application launch failures over a number of days

    and regarding SW meetering;
    • Configuration Manager can track and report on virtual application usage using Configuration Manager’s built-in software metering features.  The same application metering methods are used to track virtual and non-virtual applications with Configuration Manager.  Tracking application usage with Configuration Manager requires the Configuration Manager administrator to set up metering rules to track execution of specific application programs contained within the application package.
    • For Configuration Manager metering to work correctly, a restart of the client system is necessary after the Application Virtualization 4.5 Client is installed.


    Compare this to the "normal" reporting;
    System Utilization Report
    Graphs the total daily usage, to help you determine the load on your Application Virtualization System.
    Software Audit Report
    Lists the usage information during the reporting period for all applications defined in the database, to help you determine which applications are the most heavily used.
    Application Utilization Report
    Tracks usage information for a specified application, to help you determine how heavily a specific application is used.
    System Error Report
    Tracks the number of errors and warnings logged over time during the specified reporting period for the specified server or for the specified server group.
    which can be read more about here;
    http://technet.microsoft.com/en-us/library/cc843659.aspx

    /Znack
    • Proposed as answer by znack Wednesday, June 24, 2009 8:10 PM
    • Marked as answer by Aaron.ParkerModerator Saturday, August 11, 2012 7:25 PM
    Wednesday, June 24, 2009 6:55 PM

All replies

  • Hello,

    Well, the documentation for SCCM R2 says this;
    • Reporting of virtual application distribution and usage is limited to the capabilities described in this document.  Depending on which Configuration Manager virtual application delivery method is chosen, some options limit reporting further compared to the reporting features that are provided by a full Application Virtualization 4.5 infrastructure.  For example: when using local delivery (download and execute), it is not possible to report on how many times an application has been used, only that it has been used and the “last launch date.”

    Reporting includes this;
    • Configuration Manager R2 includes the following built-in reports that can be used to report the status of virtual application distribution throughout the Configuration Manager hierarchy and virtual application delivery to Configuration Manager Clients:
    o All distribution points with virtual application streaming enabled
    o All virtual application packages in the streaming store of a distribution point
    o Computers with a specific virtual application
    o Computers with a specific virtual application package
    o Count of all instances of virtual application packages
    o Count of all instances of virtual applications
    o Streaming store distribution status of a specific virtual application package
    o Virtual application launch failures for a specific application
    o Virtual application launch failures for a specific computer
    o Virtual application launch failures over a number of days

    and regarding SW meetering;
    • Configuration Manager can track and report on virtual application usage using Configuration Manager’s built-in software metering features.  The same application metering methods are used to track virtual and non-virtual applications with Configuration Manager.  Tracking application usage with Configuration Manager requires the Configuration Manager administrator to set up metering rules to track execution of specific application programs contained within the application package.
    • For Configuration Manager metering to work correctly, a restart of the client system is necessary after the Application Virtualization 4.5 Client is installed.


    Compare this to the "normal" reporting;
    System Utilization Report
    Graphs the total daily usage, to help you determine the load on your Application Virtualization System.
    Software Audit Report
    Lists the usage information during the reporting period for all applications defined in the database, to help you determine which applications are the most heavily used.
    Application Utilization Report
    Tracks usage information for a specified application, to help you determine how heavily a specific application is used.
    System Error Report
    Tracks the number of errors and warnings logged over time during the specified reporting period for the specified server or for the specified server group.
    which can be read more about here;
    http://technet.microsoft.com/en-us/library/cc843659.aspx

    /Znack
    • Proposed as answer by znack Wednesday, June 24, 2009 8:10 PM
    • Marked as answer by Aaron.ParkerModerator Saturday, August 11, 2012 7:25 PM
    Wednesday, June 24, 2009 6:55 PM
  • I read those in the white paper as well but I don't see much of a loss of reporting features when comparing between Full Infrastructure and SCCM integration. 

    Is there a way for App-V full infrastructure to do software metering on streaming apps in real time?  Let's say if I only have 5 license of WinZip packaged as a virtual app to stream, will App-V be able to disable the streaming of WinZip to the 6th requester if I already have 5 concurrent stream of WinZip?  Is it safe to assume that SCCM integration can do it since it already has that reporting feature capability. 
    Wednesday, June 24, 2009 10:03 PM
  • Hello,

    There is not built-in reporting todo it, however the data is available in the database and could probably be extracted somehow. Tim Mangan suggested this in another post, but then again you would have to extract and present all the data yourself.

    /Znack
    Thursday, June 25, 2009 4:37 AM
  • Is this for the Full Infrastructure that you are referring to?
    Thursday, June 25, 2009 4:13 PM
  • Hello,

    Yeah, since you asked about the full infrastucture modell and howto report software meetering for it..

    /Znack
    Thursday, June 25, 2009 4:28 PM
  • It is not neccessary to actually install the full infrastructure to get the reporting, if you do a little work yourself.

    The trick starts at the client.  If you add a URL for a publishing source, this triggers the client to save reporting information locally.  As long as you don't point the URL to a real full infrastructure server, no publishing occurs and you still get everything from SCCM.

    This post http://www.tmurgent.com/TmBlog/?p=722 explains how to make a little webpage gatherer using just aspx and a Sql database to pop the data into.  This is what you point the URL to.  Then you use Sql Reporting services to write your own report.

    Since it isn't out of the box not many people bother with this.


    Tim Mangan MVP for App-V and Citrix CTP Author of AppV books: "The Client Book" and "OSD Reference Book" (http://www.tmurgent.com/Books )

    Saturday, August 11, 2012 12:44 PM
    Moderator
  • We also discuss that here:

    http://blogs.technet.com/b/appv/archive/2011/11/10/how-to-create-a-sample-app-v-http-reporting-service.aspx


    Steve Thomas, Senior Consultant, Microsoft

    App-V/MED-V/SCVMM/Server App-V/MDOP/AppCompat

    http://blogs.technet.com/gladiatormsft/
    The App-V Team blog: http://blogs.technet.com/appv/
    The MED-V Team Blog: http://blogs.technet.com/medv
    The SCVMM Team blog: http://blogs.technet.com/scvmm/

    “This posting is provided "AS IS" with no warranties, and confers no rights. User assumes all risks.”

    Tuesday, August 21, 2012 2:34 AM