As part of Boot measurements collected on Windows (https://help.aternity.com/bundle/console_admin_guide_z_console_saas/page/console/topics/console_admin_coll_device_boot_list.html) - Aternity supplies out of the box a set of proprietary boot measurements. The proceeding material covers the measurement in a bit more context for customer understanding.
Aternity EUE Boot Profiler measurements
Description
Solution
The following are details around the boot profiler monitors and how a customer can interpret them.
* Machine Boot:
- This monitor is initiated by turning the power on, or restarting the computer. Boot is considered started when OS is launched and marked complete when the login prompt is displayed, or auto-login is initiated; Also stated as starting a fraction of a second after the Windows logo appears, and ending with the Windows sign in screen.
* Drivers Invocation:
- This monitor captures listing of drivers and the time each took to load, which occurs during the Machine Boot phase
* User Logon:
- This monitor is either initiated by the user, or initiated automatically immediately following boot (if auto-login is configured). Logon is complete when desktop is rendered and the taskbar appears. Also stated as starting when you press OK at the Windows sign in screen and ending when the Windows desktop Start button appears.
* Automatic Services:
- This monitor measures from the time the first Windows Service was started until the last service has finished. Note - boot process might complete before all the automatic services started, in which case the login prompt is shown, while the services are still being launched in the background.
* Service Invocation:
- Automatic Services phase is broken down to “Service Invocation” components that covers a module name and Start Type (Manual/Automatic). Note that the duration is simply the time it took to start, excluding any additional processing it might have done after it came up.
* Group Policies:
- There are two types of Group Policies - Computer and User. When it's captured each we measure the Download duration and Apply duration. They are not grouped into phases as they are continuously downloaded and applied thought the life of the user’s session. Each measurement will try to gather module name and server ID (the Domain Server, etc.)
* Machine Boot:
- This monitor is initiated by turning the power on, or restarting the computer. Boot is considered started when OS is launched and marked complete when the login prompt is displayed, or auto-login is initiated; Also stated as starting a fraction of a second after the Windows logo appears, and ending with the Windows sign in screen.
* Drivers Invocation:
- This monitor captures listing of drivers and the time each took to load, which occurs during the Machine Boot phase
* User Logon:
- This monitor is either initiated by the user, or initiated automatically immediately following boot (if auto-login is configured). Logon is complete when desktop is rendered and the taskbar appears. Also stated as starting when you press OK at the Windows sign in screen and ending when the Windows desktop Start button appears.
* Automatic Services:
- This monitor measures from the time the first Windows Service was started until the last service has finished. Note - boot process might complete before all the automatic services started, in which case the login prompt is shown, while the services are still being launched in the background.
* Service Invocation:
- Automatic Services phase is broken down to “Service Invocation” components that covers a module name and Start Type (Manual/Automatic). Note that the duration is simply the time it took to start, excluding any additional processing it might have done after it came up.
* Group Policies:
- There are two types of Group Policies - Computer and User. When it's captured each we measure the Download duration and Apply duration. They are not grouped into phases as they are continuously downloaded and applied thought the life of the user’s session. Each measurement will try to gather module name and server ID (the Domain Server, etc.)
NOTICE: Riverbed® product names have changed. Please refer to the Product List for a complete list of product names.
Can't find an answer? Create a case