Defining an Application for Usage Monitoring

A monitored application enables customers to query the actual usage of applications on the managed devices. In this node you can define the applications which are to be monitored and on which clients in your network. The actual monitoring will be done by the local agent according to the definitions set up in the respective Monitored Application Model. The agent stores the logged data, the date and time the application was started and ended as well as the duration of the usage, in the local database and uploads these periodically to the master database.

1. Select the Wizards> Application Management menu item or launch it directly from the dashboard.
2. In the Introduction window select the Configure a list of applications to manage radio button.
3. Click Next.
4. In the Application List window enter Monitoring Adobe Reader into the Name field.
5. From the Type drop-down list select the Monitored Application option.
6. Click Next.
7. In the Applications window click Add an application from the inventory list.

8. To find the application enter all or part of its name into the Value field, for example, Reader and then click the Find button.

   If your network has different versions of Reader installed you can see here all versions.
   

9. Select the desired version and click OK.
10. Click Next.
11. In the Assigned Objects window click Add Device on top of the list field.
12. Go to the All tab of the Select a Device window and select the master from the list.
13. Click OK.
14. Click Finish.
15. In the Confirmation dialog box, click Yes to confirm the activation.
     The application is defined for monitoring.
16. Now launch and close the Adobe Reader application several times on the assigned device (master) and leave it finally running.
17. Open the Device Topology> Master> Agent Configuration> Module Configuration> Application Monitoring node.

18. Select the List tab.

    It displays all applications that were selected for managing on the local client, monitored as well as prohibited applications. For the moment you will only see the Adobe Reader entry.
    

19. Go to the Monitored Application Usage Details tab.

    This table displays the details on the monitoring of Adobe Reader. You will see that there are as many entries in the table as you have effected opening and closings of the application. The last opening is not yet counted as the application has neither yet been closed nor has it been open for more than 24 hours.
    

20. Close the Adobe Reader application now and then refresh the console view.
     Another entry was added to the list.

To define an application for prohibited launch detection via the software catalog

A prohibited application list allows the administrator to disable the launching of specific applications on a managed device using the criteria defined through the Prohibited Application Model. It allows the denial of certain application launches, both on online as well as off-line devices.

The following example prohibits the execution of the Pinball game on the master during working hours.

1. Select the Wizards > Application Management  menu item or launch it directly from the dashboard.
2. In the Introduction window select the Configure a list of applications to manage radio button.
3. Check the Define a specific schedule to manage these applications box.
4. Click Next .
5. In the Application List window enter Prohibiting Pinball into the Name box.
6. From the Type drop-down list select the Prohibited Application option.
7. Click Next .
8. In the Applications window click the Add license units from the software catalog  icon.
9. Click the Search  tab button on the left.
10. From the Type drop-down list select the Application value.
11. Into the Value box enter Pinball .
12. Click the Find  icon next to it.
13. Select the Pinball entry and click the Add  button.
14. Click the OK button to confirm.
15. Click Next .
16. In the Schedule Template check the Create a new schedule template option.
17. Click Next .

18. In the Schedule Template Configuration window enter the name into the respective text box, e.g. No Working Hours .

    The current planning prohibits the execution at all times, indicated by red crosses in all boxes.
    

19. To allow the execution for non-working hours mark the boxes Mon-Fri 12:00-13:59 by clicking the first box (Mon 12:00) and dragging the mouse key to the last box (Fri 14:00).
20. Click the Allow Time-slot  icon to allow the application to execute in this time range.
21. Click Next .
22. In the Assigned Objects window click Add Device  on top of the list box.
23. Go to the All  tab of the Select a Device window and select the master from the list.
24. Click OK .
25. Click Finish .
26. In the Confirmation dialog box, click Yes to confirm the activation.
    The application is defined for launch prohibition.

27. Now start Pinball on the assigned device (master).
    The execution will be stopped and an Information window appears telling you that Pinball was prohibited from execution.

    Note:

    If Pinball is launched instead of being stopped, maybe you are currently in the allowed timeframe?

28. Click OK to close the message box.
29. Open the Device Topology > Master > Agent Configuration > Module Configuration > Application Monitoring node.

30. Select the List tab.

    It displays all applications that were selected for managing on the local client, monitored as well as prohibited applications. Here you will see now the monitored application Adobe Reader (if you have executed the preceding example) as well as the new prohibited Pinball . If this is not the case refresh the view.
    

31. Go to the Prohibited Application Usage Details tab.

    This table displays the details on the monitoring of Pinball execution and should now show the tentative to launch the software.