![]() For example, in the organization with the slowest average login in the sample users waited for 67.8 seconds, while the champion network had an average login duration of only 9.6 seconds! Looking at the organizational averages might give us a better idea about the results you might find in a given network. The median was 27.5 seconds, dividing between the faster and slower half, 8 organizations in each. In a sample of over 1.8 million logon events from 16 different organizations, the average logon duration was found to be 29.7 seconds (with a standard deviation of 24.4 seconds). Here’s some more on important metrics for VDI: It’s about knowing how the average login duration in your organization ranks against global stats, while also being able to detect and monitor irregular login performance. This also enables IT professionals to easily compare logon performance between different systems, both within the organization and outside it. While application performance may vary greatly and can be very tricky to measure, the logon process involves a small number of relatively well-known phases. The IT department can (and should) use those insights to improve the quality of service delivered by the organization’s computing environment. Second, Windows logon is a well-structured process which can be analyzed to uncover delays and produce actionable insights. ![]() If logon is slow enough, users may even forget why they logged on in the first place! For logons that happen in the middle of a workday, logon duration may influence the speed with which an employee can switch from one task to another. The speed of logon upon an employee’s arrival at the office determines how quickly they are able to start generating value for the organization. The faster a computing environment is delivered to the end user, the greater the user’s ability to react to work challenges, whatever they may be. Logon duration is an important user experience metric for any end-user computing environment, for several reasons.įirst, logon performance may be seen as related to employee productivity. Any further delay experienced from that moment can be attributed to resource bottlenecks associated with applications, and not caused by the logon process itself.įor more details regarding the ways ControlUp measures login duration, see here. To explain this choice of boundaries briefly, let’s just say that the idea was to represent nothing but the machine-caused delay, until the desktop is ready or until the published app takes over. For this “published app” scenario, we’ll consider the logon process complete when the published application is started. When the default Windows shell is not used, an alternative application is configured to be launched by the application delivery mechanism in place. From the user’s perspective, this is the moment when the Start button of the Windows taskbar becomes responsive and opens the Start Menu when clicked. Typically, this happens whenever a user inputs a username and password which are accepted as correct by a domain-joined Windows system.įor a “desktop” scenario, the logon process is considered complete when the Windows Explorer shell is ready. Logon duration is a period of time that begins when the user is successfully authenticated. Logon Duration – What do you mean by that? This article provides the IT community with a first peek into those global statistics. Alongside traditional IT monitoring and reporting, ControlUp Insights offers access to global performance data for comparison and benchmarking. ![]() ![]() ControlUp Insights is a cloud-based IT analytics platform built for IT admins. This article presents statistics from a global dataset of logon duration metrics gathered by the ControlUp Insights platform. How fast is the user logon process in business IT environments? This question is of interest for IT pros because an answer to it can provide a benchmark for user experience.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |