View the SLA Compliance of Device Boot Times (Boot)

The Boot dashboard monitors the time it takes for devices across your organization to start up, and compares it to expected SLA targets.

In many enterprises, long boots and slow startup times directly contribute to a loss of productivity, so it is really important to know if you have a boot problem. This dashboard enables you to see at a glance the boot situation within the company. The system accumulates boot data from the monitored devices throughout your organization to build a comprehensive insight into boot metrics. Use this dashboard as a starting point for troubleshooting boot times and continue with the Boot Analysis dashboard if necessary.

The final purpose is to reduce the boot times across the enterprise, by identifying and fixing the contributing factors to a long boot.

View the boot SLA compliance and the average boot times

For example, you may have set certain boot time targets for the devices in the organization, or you may have invested in hardware and infrastructure to reach those targets, and now you need to validate the investment by demonstrating the improvements in performance. Or, if you have a contract with external vendors for certain boot performance of their products, you need to know that they deliver. You can also check the effect on boot times when you implement a change in software. For instance, you updated the version of your printer driver, but this new version takes significantly longer to load on startup.

You may also, for example, receive a complaint from a user that their device takes longer than usual to boot. To debug the issue, you would want to see if other users experience the same phenomenon. If they do, you can see what those users have in common, if they use the same type of computer, if they are grouped in the same geographical area, if they use the same operating system, and so on.

You can view if an application breaks your external (officially committed) SLA thresholds, or show the compliance with your stricter internal (early warning) SLA thresholds, to indicate if you are close to breaking your official SLA commitments.

To... Do This...

To view the number of boots that fail their SLA, to highlight boot times which require your attention

Use the SLA Breakdown pie-chart.

This pie-chart displays the compliance of boot times to your committed SLA. It makes it easy for you to see at a glance the volume of boots that exceed the predefined SLA thresholds.

When you select the sector showing the boots that fail their SLA, you automatically get the full view of the failing boot situation per operating system and geographic area.

To view which operating systems perform worst in terms of boot time, to check if a long boot time is common to all those devices using the same operating system or service pack

Use the Operating System section.

Select the sector showing the boots that fail their SLA in the SLA Breakdown pie-chart and see the boot times in this section.

To view the locations of the systems that fail their SLA, to determine if a feature common to one location is causing slow boot times

Use the Geographies section to view cities, countries or regions.

Select the sector showing the boots that fail their SLA in the SLA Breakdown pie-chart and see the longest boot times in this section.

To view the boot behavior of a particular type of device (like desktops or laptops), to determine if the cause of a slow boot is based on drivers or faulty hardware in certain devices

Select the type of the device in the Device Type drop-down menu in the top bar and view the SLA Breakdown pie-chart, the Operating Systems section, and the Geographies section.


  1. Step 1 Open a browser and log in to Aternity.
  2. Step 2 Access the dashboard by typing its name in the search box in the top bar.

    Alternatively you can drill-down to this dashboard from any of the following dashboards:

    • Desktop Health

    • Desktop Reliability

    • Device Inventory

    • My Enterprise

  3. Step 3 Set the boot time you want to display to Total Boot, Machine Boot, or User Logon in the drop-down menu in the top bar.
    Choose boot time to display by selecting it in the top bar of this dashboard

    There are several boot times defined in Aternity.

    Field Description

    Total Boot

    The total boot time on Windows device starts from the time the Windows logo appears until the desktop appears and all components are loaded. The Agent queries Windows Event Log (ID 100) for the BootTime parameter, calculated as the sum of main path boot and post boot times, located in the Diagnostics > Performance > Windows section of the log.

    For details of main path boot and post boot times (not present in this dashboard), see Troubleshoot Boot Issues (Troubleshoot Boot).

    Machine Boot

    Machine boot is part of a device's boot time, starting a fraction of a second after the Windows logo appears, and ends with the Windows login screen. The Agent queries Windows Kernel-PnP (NOT the Event Log) for the BootStart > Start event to mark the start of this time, and ends when the Windows login screen appears (or the login process starts in case of auto-login).

    User Logon

    User logon measures a part of the boot time, starting when you press OK at the Windows login screen and ending when the Windows desktop Start button appears. The Agent queries Windows Shell-Core (NOT the Event Log) for the Explorer_StartMenu_Ready event to mark the end of this time.

    Various boot time definitions

    The end of the User Logon and the end of the MainPathBoot do not coincide exactly.

  4. Step 4 View how many boots comply or break your SLA, in the SLA Breakdown pie-chart.

    In this chart, you can see the number of devices with abnormal boot times causing inefficiency.

    View the boot compliance with your SLA threshold

    The values of the SLA thresholds (the SLA targets) are displayed below the chart.

    Field Description

    The number of boots that comply with the SLA.


    The number of boots whose time exceeds the internal SLA threshold. This is a first warning that devices in your organization have an increase in their boot time. You may want to watch them closely to resolve potential problems before they worsen.


    The number of boots whose time exceeds the external SLA threshold. If devices exceed this limit, track down the cause to resolve it as quickly as possible.

    Use this chart as the starting point of your investigation. An orange area is a call for immediate action. Drill down to the Boot Analysis dashboard, to investigate deeper into the causes of the low boot performance.

  5. Step 5 View the performance of the operating systems in terms of their average boot time in the Operating Systems section and the location of the slow boots in the Geographies section.

    The Operating Systems section presents the number of boots and the average boot time per operating system. By default, the operating system with the longest average boot time appears at the top, regardless of the number of boots or the compliance with the SLA. The score shows the operating systems that perform worst and which require immediate attention.

    The Geographies section presents the longest average boot time at the top. Check if a poor boot performance is confined to a specific location. In the drop-down menu in the top right corner of this section, choose to view the data per Countries, (default), States, Cities, Regions or Geographies (Map). This way you find out if it could be an infrastructure problem of a certain geographical area (like the new printers installed in your London subsidiary, whose driver is causing boot delays), or perhaps a new system utility that was installed in all locations but takes a long time to launch.

    View which operating systems perform worst and their location
    Field Description
    Boot Performance Score
    The boot score is a reflection of the boot performance. Its status can be:
    Number of Boots

    The number of boots monitored in the selected operating system.

    Average Boot Time

    The average of all the boot times of devices running that operating system (displayed in hours, minutes, and seconds). The average can be of the total boot time, the machine boot time or the user logon time depending on your choice in the View drop-down menu in the top-right corner of the window.

    Break down the information per number of boots which took longer than the minor threshold and the major threshold, hover over the boot performance score icons or over the average boot time horizontal bars and see the pop-up window.

    Field Description

    The average boot time [hours:minutes:seconds], calculated as the average of the monitored boots.


    The number of monitored boots during the dashboard's timeframe.


    The number of boots whose time is as expected, under the SLA's minor threshold


    The number of boots with the status of minor, which break the SLA's minor threshold. These boots are not ideal, and should be watched for further degradation.


    The number of boots with the status of major, which are a call to action to investigate and resolve.


    This activity status is not applicable for boot times.


    This activity status is not applicable for boot times.


    The score of all the boot statuses for this operating system.


    Boot status based on the score: Good, Fair, Poor, Unacceptable.

  6. Step 6 Check the possible correlation between the worst performing operating systems and their geographic distribution.

    After you identify a boot problem with the pie chart, you can determine if all slow boots have a common location or operating system. Select the relevant area (yellow or orange) in the SLA Breakdown pie-chart, and view the Operating Systems and Geographies sections.

    For example, if you select the orange area in the pie-chart, check how the operating systems perform against each other, and select the slowest one. See if the selected operating system is installed in one or several locations in the Geographies section. The longest boots are displayed first. Long boot times in a certain zone could be an indication of a network problem that needs attention.

    View only the boots which least complied with your SLA threshold

    To view more information, drill-down to the Boot Analysis dashboard (see Troubleshoot Boot Issues (Troubleshoot Boot)). There you can view more detailed information, including the recent trend in boot times, the list of each individual process which has a longer than usual boot, or the users and departments that experience boot issues and their device model.

  7. Step 7 To limit the display to a certain type of device or to show the boot data for specific periods of time, use the drop-down menus in the top bar of the dashboard.
    Changing the scope and details of the Boot dashboard




    Choose the start time of the data displayed in this dashboard.

    You can access data in this dashboard (retention) going back up to 30 days. This dashboard's data refreshes every hour.

    Device Type

    Select to view the boot times for just a single type of device.


    Only desktops, laptops, tablets and virtual desktops have a boot sequence, so only these device types are displayed in this dashboard.

    You can continue your investigation to see when the boot problems started, by choosing different periods of time in the Timeframe drop-down menu. To view the recent trend in boot performance to pinpoint the day when the boot performance decreased, see the Boot Analysis dashboard (see Troubleshoot Boot Issues (Troubleshoot Boot)).