Common Questions about LDMS 8.8 Rollup

Version 6

    Verified Product Versions

    LANDESK Management Suite 9.5LANDESK Management Suite 9.6



    LANDesk Management Suite 8.8


    What is a Rollup Core?


    A rollup core enables you to take multiple source core databases and combine them into a single destination core rollup database, allowing you to create reports or query the managed devices across your organization. . A core server database can support several thousand devices, and the rollup core device limit depends on your hardware and acceptable performance levels. The source database can be either a core server or a rollup core server.


    What can I do with the Rollup Core?


    • Create Queries that show data from all cores
    • Create Reports that show data from all cores
    • View Inventory from all Core
    • Create and deploy software distribution packages
    • Remote control (Depending on Domain Access)

    How do I install a Rollup Core?

    View the following article for installing the LANDesk 8.8 Rollup Core:


    Things to keep in mind regarding the Rollup Core

    • All cores that are being added to the rollup core must be the same version and service pack level
    • All cores that are being added to the rollup core must have the same language (LMDS 8.8 Ver.)
    • The web console is how  you will utilize the Rollup Core Reports, Queries and Software Distribution
    • With large rollup databases, the Web console's query editor may time out when it tries to query and display a large list, such as the Software Package Name list. When this happens, the list you are trying to display won't show any data. If you experience timeouts you need to increase the database timeout value on the core running the IIS service or the Web console server. At the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\LANDesk\ManagementSuite\Core Add a new DWORD, Timeout, with a decimal value of 1800. This value is in seconds. You can adjust this value based on your query types and database performance. Stop and restart the IIS service for the change to take effec


    • Only one rollup can be processed at a time. A scheduled rollup will fail if another rollup is already in progress. When scheduling rollups, allow enough time between rollups that there won't be any overlap. If the rollup times are hard to predict, it's best to schedule all the rollups in a single task. Do this by targeting multiple cores before scheduling. This way, the rollups are handled one at a time automatically.

    Where can I find more information about the Rollup Core?