How To: Troubleshoot the 32-bit Console (Console Landing Page)

Version 22

    Verified Product Versions

    LANDESK Management Suite 9.6LANDESK Management Suite 2016.x





    This article functions as a landing page of sorts for the 32-bit console. Due to the complexity of the console and the various ways in which it can break this article will branch out into 5 sub-articles. Each sub-article will contain a link back to this main article.


    Console Design and Logs


    Console Cache: Console.exe makes use of cache in order to increase the speed of operations. While testing, duplicating an issue, or trying to resolve a problem it becomes important that the console be closed and restarted again and again.


    Console User Layouts: The console layout is stored automatically when a user closes the console. A user can also create multiple layouts and revert to them as needed. Sometimes these layouts can cause problems with the console. See the "General Troubleshooting" area below for details on how to delete the user layout.


    Core Console vs 32-bit Remote Console: By design only the console on the core server will have access to certain features and settings.



    • Console.exe.log
      • LANDesk 8.8 Location: C:\Program Files\LANDesk\ManagementSuite
      • LANDesk 9.0 Location: C:\Program Files\LANDesk\ManagementSuite\Logs
    • Console.exe.Licensing:
      • LANDesk 9.0 Location: C:\Program Files\LANDesk\ManagementSuite\Logs
    • Windows Event Logs
    • IIS Logs
      • IIS 6 Location: C:\Windows\system32\LogFiles\W3SVC1\exXXXX.log (name includes date stamp)
      • IIS 7 Location: C:\inetpub\logs\logfiles\W3SVC1\u_exXXXXX (name includes date stamp)


    Console Problem Types and Troubleshooting


    Troubleshooting is broken out in the areas below for easy reference however the steps in each of the areas may help resolve any console issue.


    General Console Troubleshooting (Layouts, Column Sets, Third Party Applications, UAC, Remote Consoles)


    Console Slowness (Identification, Resources, Active Directory, Database Optimization, IIS, Communication Issues)


    Error Messages (Identification, Interpretation)


    Missing Features or Icons (Licensing, RBA, General Corruption)


    How to Interpet the Console.exe.log


    Known Issues


    Agent Status/Discovery isn't working correctly

    32-bit Console may lock up if you attempt to view the properties of a vulnerability

    Console Problems after installing .NET 4.0

    Remote Console 9.0 SP1 Licensing Error after Upgrading


    Recommended Articles


    What do those icons in the 32-bit console mean?


    Miscellaneous Console Files


    • enutools.xml = This is a tools configuration file which has some control in regards to displaying icons in the Toolbox however this file will not resolve licensing problems on the core. If tools are missing then the section above should be followed first.
    • CoreConnectionMRU.xml = This is an XML document that contains the information of the last user who logged into the console.  In addition this file contains information for the dropdown list of core servers both in the logon screen and in the "Core:" dropdown within the console.  This file can be edited to modify the default core server to log in to, or to remove core servers from the dropdown list.
    • Console.exe.config = This is a standard configuration file and normally will never need to be modified. The settings contained are parameters used for compatibility and functionality and may render the console broken if they are modified incorrectly.