How To: Schedule a Report and Have It Delivered via Email

Version 15

    Verified Product Versions

    LANDESK Management Suite 9.5LANDESK Management Suite 9.6LANDESK Management Suite 2016.x

    Overview

     

    This article describes how to create a report, how to schedule that report to be run at regular intervals and how to have that report emailed to a specified user(s).

    ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    How To Create a Report

     

    1) In the Console navigate to Tools | Reporting / Monitoring | Reports

     

    2) In the lower pane: Right-click on My reports then select New Report

     

    3) Give the report a Title and Description

    Capture.PNG

    4) You can base the report off a previously created query or code your own report using the Report Designer, for this example I am using a previously created query.  So click on the Load from LDMS query button.

     

    Note: If you do not have a query setup that you would like to report on see the section Setting Up a Query at the end of this document.

    Capture.PNG

    5) Locate and select the query to base the report from and click OK.

     

    Capture.PNG

    6) A report can include a Pie or Bar chart, if desired, select a Chart type: and a Query field: to base the chart data from, in this example we will create a report listing all PC's not on the domain with a Pie chart broken out by Operating System of those PC's.  With this report we will visually be able to see what percentage of our PC's not on the domain have a certain OS.  This can be handy since perhaps some operating systems may not be a priority for domain migration as we know that we are getting ready to upgrade a particular OS and we can add those PC's to the domain at that later time.  Once these values are configured, click OK to commit the report or Preview to test output with the availability to return to this screen to make changes.

    Capture.PNG

    7) The report is saved in the section of the Reports pain that New Report screen was initiated from.

     

    8) To run the report right-click on the report and select Run or alternatively double-click on the report.

    Capture.PNG

    Capture.PNG

     

    9) Check to ensure the report is displaying the desired data in the desired format, if not changes to the query in which the report is based on may be in order.

     

    Note: If the query parameters are changed, the report will also need to be edited and re-associated to the changed query.

    ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    Schedule a Report To Be Delivered via Email


    1) Right-click on the report, hover over Schedule, then select the document format you want to deliver the report (PDF, XLS, DOC, CSV or HTML)

     

    Capture.PNG

    2) Double-click on the newly created scheduled task.

    Capture.PNG

    3) Since this is a report most of the options on the Overview screen are not configurable, except changing the User who is the Report Owner, configure that option and then select Schedule task.

    Capture.PNG

    4) I want to set this report to run every Sunday so it can be available in the domain migrations team email box every Monday morning.  Set a start date and to repeat frequency.

     

    5) Select the Recipients screen.

    Capture.PNG

    6) The Recipient list is based on the users on the Core console that have an email address attached to them.  So if you are not seeing who you would like to distribute your report too, go to User Management on your core console and setup additional users, groups and supply email addresses for those user and groups.

    Capture.PNG

    Capture.PNG

    Capture.PNG

    7) Now that we have the users that we want to receive the report configured, place a check-mark next to those users as well as the LANDesk Reports Share which will place a copy of the report to the LANDesk reports directory in addition to emailing them to the desired users.  Which you can share that directory to the recipients of the report so they have a historical archive of all reports or share this directory with additional users who maybe do not get emailed every report but you would like to have the ability to have access to those reports should they need them.

     

    8) Enter a Reply e-mail: address.  This field is required and should be an email that will return to someone who has the ability to edit and explain the report as most people will be motivated to reply for those reasons.

     

    9) Select SMTP Configuration

    Capture.PNG

    10) Configure your SMTP Server information as required and enter an email address to send a test message to, click Test and ensure the email arrived at the tested destination.

        Capture1.png

    NOTE: On the recipeient's end, the test email will show "SMTP configuration test"(1) as the subject line and "This is a STMP configuration test e-mail sent by LANDESK Task Scheduler"(2) in the body of the email.

     

    11) Once satisfied with your configuration, click Save.

     

    12) Now sit back and wait for the reports to roll in.

    ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    Setting Up a Query

     

    1) In the Network View (Top Pane), expand out Queries, Right-Click on My Queries or Public Queries (Depending if you want other users to be able to access the query, the select New Query.)

     

    2) Provide a name for the query.

     

    3) You can query on anything that the inventory scanner scans, hardware items, software items, LANDesk scan information or any custom registry tags that the agent is configured to pickup.

     

    4) For this example I am going to query on computers that are not logging into a particular Domain.  I am trying to convert all PC's to login to a certain domain, so I want a report of all of those PC that are not logging on to that domain.

     

    5) The best practice is to identify an object that has the condition that you want to report on and another object that has a condition that you want to exclude from the report and compare what about these two objects is unique to each object but different that will allow you to put the objects into two separate groups. For this example we want to identify a PC that we know we have converted to the new domain and one that we know we have not converted.

     

    This picture shows a side-by-side of a PC that has been converted to the domain (left) and a PC that has not been converted to the domain (right):

    Capture.PNG

    A close-up ff the LDAP Location Tag (Left PC):

    Capture.PNG

    A close-up of the LDAP Location tag (Right PC):

    Capture.PNG

    6) The Inventory Scan from PC on the left is on the domain while the Inventory scan from the PC on the right is not; the general system tags LDAP Location would seem to be a great tag as a PC on any domain will have LDAP information and we can further query on where the DC (Domain Component) is equal too the domain we want the PC's to be migrated too.  But since in this example we are going from not on any domain at all to the only domain we have, we will just need to query for PC's that do not have any LDAP location info.  Having those PC's on a report will tell us what PC's we need to target for migration.  Further you can also reverse the query to report on what PC's have been migrated; some may find that helpful as the total of the two reports should reconcile to the number of PC in the environment to ensue every machine has been accounted for.

     

    Capture.PNG

    7) Give the query a name by entering a name in the Name: field.

     

    8) In the left pane labeled Machine Components: select LDAP Location.

     

    9) In the middle pane select Not Exists.

     

    10) Click on the Insert button below the Machine Components: pane, this will insert the query value of: "Computer"."LDAP Location" Not Exists.

     

    11) That's all this query needs to do so click Save.

     

    Capture.PNG

    12) By Default the query returns some initial data, to rerun it or refresh it, right-click on the query name and then select Run.

     

    13) Here the query has returned the name of the machine we were expecting as well as two more machines, which was also to be expected, however the machine on the domain was not returned so on the surface it looks like our query is working.