Network speed detection

BACKGROUND

0001In an enterprise environment, a management service can be employed that manages client devices that are associated with various user accounts in the enterprise. Client devices can communicate with the management service through various types of network connections, wired or wireless carriers, private networks, or via the public Internet. The performance of a connection between the client device and the management service can affect user experience and quality in various ways.

0002A user or customer can report issues or errors with respect to the management service. In some cases, these errors are caused by or can be traceable to a quality or speed of a network connection. Therefore, collecting data with respect to network connections of devices associated with a management service can be desirable to provide data with respect to network connections of client devices. Potential errors or issues experienced by users with respect to the management service can be diagnosed or assessed based upon the collected data.

BRIEF DESCRIPTION OF THE DRAWINGS

0003Many aspects of the present disclosure can be better understood with reference to the following drawings. The components in the drawings are not necessarily to scale, with emphasis instead being placed upon clearly illustrating the principles of the disclosure. Moreover, in the drawings, like reference numerals designate corresponding parts throughout the several views.

0004<figref idref="DRAWINGS">FIG. 1</figref> is a drawing of a networked environment according to various examples.

0005<figref idref="DRAWINGS">FIG. 2</figref> is a sequence diagram illustrating interactions between elements in the networked environment of <figref idref="DRAWINGS">FIG. 1</figref>.

0006<figref idref="DRAWINGS">FIG. 3</figref> is a flowchart illustrating an example of functionality implemented by the management service according to various examples.

0007<figref idref="DRAWINGS">FIG. 4</figref> is a flowchart illustrating an example of functionality implemented by the network testing application according to various examples.

0008<figref idref="DRAWINGS">FIG. 5</figref> is a flowchart illustrating an example of functionality implemented by the network testing application according to various examples.

DETAILED DESCRIPTION

0009The present disclosure relates to assessing the speed, quality, or performance of a network connection of a client device with respect to a management service. In some scenarios, users in an enterprise environment can be provided with a client device, such as a smartphone, tablet device, a general purpose computing device, or other computing device. Users can also enroll their own devices within an enterprise environment. The client device can have access to enterprise resources, such as email, files, networks, and other enterprise resources. However, the client device can also be enrolled with a management service such that it becomes a managed device.

0010An enterprise can wish to define one or more compliance rules that can include policies with which a user or the client device must comply in order to access enterprise resources. These policies can include requirements with respect to a location of the device, whether software on the client device is modified, or a requirement that the client device execute a particular version or brand of operating system or other software. In addition, a compliance rule can specify that the client device should be in communication with a management service or a server on which the management service is executed with a connection having a minimum speed.

0011Additionally, systems administrators can wish to assess the speed or quality of a connection of a client device with the management service or a network on which the management service is placed for quality assurance, testing, or other profiling reasons. For example, if a user or enterprise is reporting errors or other issues with performance of a client device or degradation in user experience, an administrator can be able to make a determination with respect to the speed of a network connection of a client device as a potential culprit for the issues. Additionally, the enterprise can have in place compliance rules that specify actions that a client device managed by the management service should take if the speed of the network connection with the management service drops below a threshold. For example, if the speed of a network connection of the client device drops below a particular threshold, a compliance rule can specify that a videoconferencing capability or status of the client device be disabled until the speed of the network connection returns to an acceptable level. As another example, if the speed of the network connection is unacceptably low, a compliance rule can specify that an email client executed by the client device avoid automatically downloading email attachments. The compliance rule can also specify that the client device should access lower quality multimedia until the speed of the network connection returns to an acceptable level.

0012Other examples and variations are discussed in further detail herein. In the following discussion, a general description of the system and its components is provided, followed by a discussion of the operation of the same.

0013With reference to <figref idref="DRAWINGS">FIG. 1</figref>, shown is a networked environment <b>100</b> according to various examples. The networked environment <b>100</b> shown in <figref idref="DRAWINGS">FIG. 1</figref> includes an enterprise computing environment <b>103</b>, a network testing endpoint <b>105</b>, a client device <b>106</b>, and potentially other components, which are in data communication with each other over a network <b>113</b>. The network <b>113</b> includes, for example, the Internet, one or more intranets, extranets, wide area networks (WANs), local area networks (LANs), wired networks, wireless networks, other suitable networks, or any combination of two or more such networks. Such networks can comprise satellite networks, cable networks, Ethernet networks, telephony networks, and/or other types of networks.

0014The enterprise computing environment <b>103</b> can comprise, for example, a server, server computer or any other system providing computing capabilities. Alternatively, the enterprise computing environment <b>103</b> can employ multiple computing devices that can be arranged, for example, in one or more server banks, computer banks, or other arrangements. The computing devices can be located in a single installation or can be distributed among many different geographical locations. For example, the enterprise computing environment <b>103</b> can include multiple servers that together form a hosted computing resource, a grid computing resource, and/or any other distributed computing arrangement. In some cases, the enterprise computing environment <b>103</b> can operate as at least a portion of an elastic computing resource where the allotted capacity of processing, network, storage, or other computing-related resources can vary over time. The enterprise computing environment <b>103</b> can also include or be operated as one or more virtualized computer instances that are executed in order to perform the functionality that is described herein. Generally, the enterprise computing environment <b>103</b> can be operated in accordance with particular security protocols such that it is considered a trusted computing environment.

0015The data store <b>116</b> shown in <figref idref="DRAWINGS">FIG. 1</figref> can be representative of multiple data stores <b>116</b> for storing data. The data stored in the data store <b>116</b> is associated with the operation of the components described below.

0016A management service <b>119</b> and/or other systems can be executed in the enterprise computing environment <b>103</b>. The management service <b>119</b> can be executed to manage and/or oversee the operation of multiple client devices <b>106</b>. In some examples, an enterprise, such as one or more companies or other organizations, can operate the management service <b>119</b> to oversee and/or manage the operation of the client devices <b>106</b> of its employees, contractors, customers, etc. Accordingly, the management service <b>119</b> is considered a trusted system.

0017The management service <b>119</b> can include a management console <b>123</b> and/or other components. The management service <b>119</b> can be executed to manage and/or oversee the operation of multiple client devices <b>106</b>. For example, an employer can operate the management service <b>119</b> to ensure that the client devices <b>106</b> of its employees are operating in compliance with compliance rules. By ensuring that the client devices <b>106</b> of its employees are operated in compliance with the compliance rules, the employer can control and protect access to data. The management service <b>119</b> can also facilitate access to email, calendar data, contact information, documents, or other enterprise data to which an enterprise may wish to provide access by users via client devices <b>106</b>.

0018The management console <b>123</b> can facilitate administration of devices of an enterprise by administrators via the management service <b>119</b>. For example, the management console <b>123</b> can generate one or more user interfaces that are rendered on a display device to facilitate interaction with the management service <b>119</b>. Such user interfaces can facilitate an administrator's inputting of commands or other information for the management service <b>119</b>. Additionally, the user interfaces can include presentations of statistics or other information regarding the client devices <b>106</b> that are managed by the management service <b>119</b>. In some examples, the management console <b>123</b> can provide a user interface accessible by an administrator through which the administrator enroll, activate, remove, deactivate, or otherwise manage devices that are employed to access resources via an application or service provided by the enterprise computing environment <b>103</b>. The user interface can also allow an administrator to define compliance rules with respect to usage of client devices <b>106</b> that are assigned to users of an enterprise.

0019The data stored in the data store <b>116</b> includes, for example, device management data <b>129</b>, network test data <b>133</b>, and potentially other data. The device management data <b>129</b> can include information about particular users of an enterprise as user account data <b>135</b>. User account data <b>135</b> can include data associated with an enterprise user account, such as mailbox data, calendar data, contact data, and other data. User account data <b>135</b> can also include access settings, such as authentication credentials, delegation settings (e.g., information about other users who can be provided access to the user account data <b>135</b> of a particular user), mail and document retention rules and/or policies, and/or other geographic access restrictions or limitations (e.g., information about certain locations and/or networks from which user account data <b>135</b> can be accessed). User account data <b>135</b> can also include other account settings, such as biographical or demographic information about a user, password reset information, multi-factor authentication settings, and other data related to a user account.

0020User account data <b>135</b> can also include a network address of a particular management service <b>119</b> with which a particular client device <b>106</b> should communicate in order to access mailbox data, calendar data, and other corporate data. The user account data <b>135</b> can also specify a polling frequency for a particular user account or a client device, which represents a frequency with which a particular client device <b>106</b> should communicate or “check in” with the management service <b>119</b> for the purposes of reporting status data associated with operation of the client device <b>106</b>. The user account data <b>135</b> can also include a user status indicator with respect to instant messaging, videoconferencing, or other services facilitated by the management service <b>119</b>. Such a user status indicator can be published in a user directory so that other users within the enterprise can initiate communications with a particular user via the client device <b>106</b>. In one scenario, the user status indicator can identify a particular user as available or unavailable for instant messaging, videoconferencing, or other form of communication.

0021Mailbox data can be synchronized with a client device <b>106</b> via the management service <b>119</b>. Mailbox data can include data associated with one or more mailboxes corresponding to a user account of a user. The mailbox data can include electronic mail messages, mail folders into which messages are organized, filtering rules that are applied to incoming and/or outgoing mail messages, attachments associated with mail messages, and/or other data associated with a mailbox of a user. Calendar data can include, for example, calendar information such as appointments, reminders, tasks and/or other data that can be associated with a timestamp or date stamp. Calendar data can include appointments that are associated with a particular location and/or user. For example, an appointment can be linked with a particular location, meeting room, building, address or other location. An appointment can also be linked with another user who is internal or external to an organization or domain of the user as well as with text and/or attachments. Calendar data can also include tasks, reminders, or other types of data that can be associated with a time and/or place and placed on a calendar.

0022Contact data can include personal information manager (PIM) or address book data related to contacts of a particular user such as internal or external email addresses, telephone contact information, mailing addresses, contact notes, and other information associated with contacts that a user may wish to maintain in an address book or contacts store. Contact data can also include user specific address book data as well as global address book data for address books that are shared among multiple users in a domain and/or enterprise. It should be appreciated that a client device <b>106</b> of a user can also be synchronized with various other forms of data other than mailbox data, calendar data and/or contact data and that these are just some examples of data that can be synchronized between an enterprise computing environment <b>103</b> and a client device <b>106</b>.

0023For example, a client device <b>106</b> of a user can also be synchronized or provided access to documents, media or other types of files that are stored in a data store <b>116</b> via a remote mail server or other type of synchronization application in accordance with various examples of the present disclosure. The client device <b>106</b> can be configured to access such resources that are stored in or on the client device <b>106</b>, in a data store <b>116</b> or any other location via any type of application that is executed by the client device <b>106</b>, and the depicted example is but one example.

0024The user account data <b>135</b> can include information regarding the client devices <b>106</b> that are managed and/or controlled by the management service <b>119</b>. The user account data <b>135</b> for a particular client device <b>106</b> can include, for example, the identification of a user assigned to the client device <b>106</b>, the identification of applications that are installed in the client device <b>106</b>, historical data regarding the operation of the client device <b>106</b>, and/or other information.

0025In addition, the device management data <b>129</b> can include one or more compliance rules <b>136</b> that are associated with a particular client device <b>106</b> or a particular user account within the enterprise. A compliance rule can specify one or more conditions that must be satisfied for a client device <b>106</b> to be deemed compliant with the compliance rule. As an example, a compliance rule can specify that particular applications are prohibited from being installed on a client device <b>106</b>. As another non-limiting example, a compliance rule can specify that a lock screen is required to be generated when the client device <b>106</b> is “awoken” from a low power (e.g., “sleep”) state and that a passcode is required for a user to unlock the lock screen. Additionally, one or more compliance rules can be based on time, geographical location, and/or other predefined conditions. When the compliance rules for a particular device profile are satisfied, the management service <b>119</b> can deem the corresponding client device <b>106</b> as being compliant with the device policy.

0026A compliance rule <b>136</b> can also specify one or more actions that should be taken in response to compliance with or a violation of a particular compliance rule <b>136</b>. For example, if a particular client device <b>106</b> exits a particular geographic location or area that is designated as a “geofence” for the client device <b>106</b> or a user account, the compliance rule <b>136</b> can specify that the management service <b>119</b> or software executed by the client device <b>106</b> should take a prescribed action with respect to the client device <b>106</b>. Such a prescribed action can include, for example, deleting certain data from the client device <b>106</b>, restricting access to certain data from the client device <b>106</b>, issuing an alert to the client device <b>106</b> via electronic mail, SMS, or other communications mechanisms, or taking any other action with respect to the client device.

0027Compliance rules <b>136</b> can also specify actions that can be taken with respect to a client device <b>106</b> when a speed of a network connection between the client device <b>106</b> and the device management service <b>119</b> fails to meet a threshold. For example, a compliance rule <b>136</b> can specify that a polling frequency of the client device <b>106</b> that identifies how often the client device <b>106</b> should communicate with or check in with the management service <b>119</b>. In one example, the polling frequency can be modified in response to a speed of the network connection of the client device <b>106</b> dropping beneath a specified threshold. As another example, a compliance rule <b>136</b> can specify that an availability status of a user associated with the client device <b>106</b> with respect to a videoconferencing capability, an instant messaging capability, a voice chat or voice calling capability, or any other communication capability of a client device <b>106</b>. In one example, the availability status can be modified in response a speed of the network connection of the client device <b>106</b> meeting or failing to meet a threshold.

0028For example, should the speed of the network connection of the client device <b>106</b> drop below a particular threshold, a compliance rule <b>136</b> can specify that a videoconferencing capability of the client device <b>106</b> should be disabled or that the user associated with the client device <b>106</b> should be designated as unavailable via videoconferencing on the client device <b>106</b>. As another example, should the speed of the network connection meet the threshold, the status can be updated so that the user is designated as available via videoconferencing. The same analysis can be applied with respect to compliance rules <b>136</b> that are associated with an instant messaging capability or a voice capability of the client device <b>106</b>.

0029As another example, a compliance rule <b>136</b> can specify that the client device <b>106</b> should be served lower quality media when the speed of the network connection drops below a particular threshold or higher quality media when the speed meets the threshold. As another example, a compliance rule <b>136</b> can specify that the management service <b>119</b> should avoid delivering files or files that are larger than a particular size when the speed of the network connection drops below a particular threshold. A compliance rule <b>136</b> can specify that the management service <b>119</b> should avoid enforcing certain compliance rules <b>136</b>, such as a remotely enforce compliance rules, when the speed of the network connection drops below a particular threshold. A compliance rule <b>136</b> can also specify only those compliance rules <b>136</b> that are enforced by the management component <b>143</b> should be enforced when the speed of the network connection drops below a threshold.

0030As another example, a compliance rule <b>136</b> can specify that a polling frequency of the management component <b>143</b> can be lowered when a speed of the network connection drops below a particular threshold or increased when the speed meets the threshold. Additionally, an amount of data reported when the management component <b>143</b> checks in with the management service <b>119</b> can be reduced with the speed drops below a threshold. For example, to reduce bandwidth usage, the management component <b>143</b> can report less data with respect to the status of the client device <b>106</b> when the speed drops below a threshold during a periodic status check in.

0031As another example, a compliance rule <b>136</b> can specify that an email client executed by the client device <b>106</b> should avoid automatically downloading attachments associated with an email message if the speed of the network connection fails to meet a particular threshold. If, however, the speed of the network connection does meet the threshold, the email client can automatically download attachments. As another example, a compliance rule <b>136</b> can specify that a client device <b>106</b> should communicate with a different device management sever <b>119</b> located at a different geographical or network location if the speed of the network connection fails to meet a particular threshold. In one scenario, a management service <b>119</b> can effectuate an action specified by a compliance rule <b>136</b> by transmitting a command to the client device <b>106</b> that is executed by the management component <b>143</b>.

0032Network test data <b>133</b> can represent test results associated with network speed tests conducted by client devices <b>106</b> associated with a particular enterprise. An enterprise computing environment <b>103</b> can service multiple enterprises or user groups. Accordingly, network test data <b>133</b> can facilitate profiling or comparison of network speed tests of a particular enterprise or a set of users with another enterprise or set of users for debugging or other administrative purposes.

0033The client device <b>106</b> is representative of multiple client devices <b>106</b> that can be coupled to the network <b>113</b>. The client device <b>106</b> can comprise, for example, a processor-based system such as a computer system. Such a computer system can be embodied in the form of a desktop computer, a laptop computer, a personal digital assistant, a mobile phone (e.g., a “smartphone”), a set-top box, a music player, a web pad, a tablet computer system, a game console, an electronic book reader, or any other device with like capability. The client device <b>106</b> can include a display as well as one or more input devices, such as a mouse, or touch pad that facilitates a user input.

0034The client device <b>106</b> can be configured to execute a network testing application <b>139</b>, a management component <b>143</b>, and/or other components. The network testing application <b>139</b> can comprise, for example, one or more programs that facilitate conducting a network speed test that assesses the speed of a network connection of the client device <b>106</b>. The network test application <b>139</b>, in some examples, can comprise a browser in which a page is rendered that facilitates conducting a network speed test with a network testing endpoint <b>105</b>.

0035The management component <b>143</b> can be executed in the client device <b>106</b> to monitor and/or manage at least a portion of the data, applications, or hardware components for the client device <b>106</b>. The management component <b>143</b> can also identify whether the client device <b>106</b> is operating in accordance with the one or more compliance rules for one or more device profiles that have been assigned to the client device <b>106</b>. In some examples, the management component <b>143</b> can function as a device management service that operates as a portion of an operating system for the client device <b>106</b>. In other examples, the management component <b>143</b> can function as a device management agent that operates in the application layer of the client device <b>106</b> and that monitors at least some of the activity being performed in the client device <b>106</b>. In other examples, the management component <b>143</b> can comprise an application wrapper that interfaces with a software component to facilitate overseeing, monitoring, and/or managing one or more resources of the client device <b>106</b>. Alternatively, the management component <b>143</b> can be a portion of an application that was developed, for example, using a Software Development Kit (SDK) that facilitates the inclusion of functionality within the application that monitors and/or manages at least a portion of the resources for the client device <b>106</b>.

0036The management component <b>143</b> can be executed by the client device <b>106</b> automatically upon startup of the client device <b>106</b>. Additionally, the management component <b>143</b> can run as a background process in the client device <b>106</b>. Accordingly, the management component <b>143</b> can execute without user intervention in some examples. Additionally, the management component <b>143</b> can communicate with the management service <b>119</b> in order to facilitate the management service <b>119</b> managing the client device <b>106</b>. For example, the management component <b>143</b> can obtain compliance rules <b>136</b> from the management service <b>119</b>, and the management component <b>143</b> can determine whether the client device <b>106</b> is operating in accordance with those compliance rules <b>136</b>. In another example, the management component <b>143</b> transmits data that indicates the status of settings for the client device <b>106</b>, and the management service <b>119</b> uses this data to determine whether the client device <b>106</b> is operating in accordance with compliance rules <b>136</b>. If it is determined that the client device <b>106</b> is not in compliance with one or more compliance rules, the management component <b>143</b> or the management service <b>119</b> causes a remedial action to be performed. Examples of remedial actions include notifying a user of the device or an administrator of the management service <b>119</b>, causing device settings to be changed so that the client device <b>106</b> becomes compliant with the compliance rules <b>136</b>, and erasing data in the client device <b>106</b>.

0037The network testing application <b>139</b> and/or management component <b>143</b> can obtain a network test profile <b>157</b> from the management service <b>119</b> that identifies a particular network testing endpoint <b>105</b> with which network speed tests should be conducted by the client device <b>106</b> as well as a schedule by which network speed tests should be conducted by the client device <b>106</b>. The management service <b>119</b> can generate a schedule to account for variances in the speed of a network connection due to changes in network conditions over the course of a day, week, month, or other interval. The testing can also occur in response to an event. For example, when a user opens a video, a network speed test can execute before, during, or after playback of the video on the client device <b>106</b>. As another example, when the management component <b>143</b> detects that a location or roaming state of the client device <b>106</b> has changed, a network speed test can execute to determine a speed of the network connection.

0038The network testing endpoint <b>105</b> can comprise, for example, a server computer or any other system providing computing capabilities. Alternatively, the network testing endpoint <b>105</b> can employ multiple computing devices that can be arranged, for example, in one or more server banks, computer banks, or other arrangements. The computing devices can be located in a single installation or can be distributed among many different geographical locations. For example, the network testing endpoint <b>105</b> can include multiple computing devices that together form a hosted computing resource, a grid computing resource, and/or any other distributed computing arrangement. In some cases, the network testing endpoint <b>105</b> can operate as at least a portion of an elastic computing resource where the allotted capacity of processing, network, storage, or other computing-related resources can vary over time. The network testing endpoint <b>105</b> can also include or be operated as one or more virtualized computer instances that are executed in order to perform the functionality that is described herein.

0039The network testing endpoint <b>105</b> can be operated by an entity that is a third party relative to the user of the client device <b>106</b> and/or the entity that operates the enterprise computing environment <b>103</b>. The network testing endpoint <b>105</b> can be located at an entry point to a private network on which the enterprise computing environment <b>103</b> is located so that a speed of a network connection of the client device <b>106</b> can be assessed without potential delays of a private network routing or network address translation within the private network. In another scenario, the network testing endpoint <b>105</b> can be located at a proxy server that proxies network traffic to a private network on which the enterprise computing environment <b>103</b> is located. Various systems can be executed in the network testing endpoint <b>105</b>, such as the network testing service <b>126</b>. The network testing service <b>126</b> can perform network speed tests with a client device <b>106</b> via the network <b>113</b>.

0040The network testing service <b>126</b> can perform a network speed tests by exchanging at least one network test packet <b>159</b> with the network testing application <b>139</b> and measuring a speed of the exchange. The speed can be measured in terms of bits per second of data transferred between the client device <b>106</b> and the network testing endpoint <b>105</b>. The network testing service <b>126</b> can also provide test results associated with a network speed test to the client device <b>106</b> and/or the management service <b>119</b>.

0041Next, a description of examples of the operation of the various components in the networked environment <b>100</b> is provided. To begin, the user of the client device <b>106</b> and/or the entity that operates the enterprise computing environment <b>103</b> can enroll the client device <b>106</b> with the management service <b>119</b>. In this sense, the client device <b>106</b> can become associated with a particular user account of an enterprise or becomes a device that is managed by the management service <b>119</b>. Upon enrolling of the client device <b>106</b> with the management service <b>119</b>, the management service <b>119</b> can generate a network test profile <b>157</b> for the client device <b>106</b> that specifies a testing schedule. The network test profile <b>157</b> can also specify one or more network testing endpoints <b>105</b> with which the network testing application <b>139</b> can conduct network speed tests. The management service <b>119</b> can then provide the network test profile <b>157</b> to the network testing application <b>139</b>.

0042The network testing application <b>139</b> can then execute one or more network speed tests in accordance with a testing schedule specified by the network test profile <b>157</b> and can provide the test results indicating a speed of the network connection of the client device <b>106</b> to the management service <b>119</b>. The test results can also include other data associated with the network connection, such as an internet service provider, a wired or wireless carrier, a network address, a geographic location, a time of day, or other properties associated with conditions under which the speed test was conducted.

0043In response to receiving the test results, the management service <b>119</b> can save the test results as network test data <b>133</b> and can facilitate profiling of the network performance of various client devices <b>106</b> associated with a particular enterprise of potentially multiple enterprises that are facilitated by the management service <b>119</b> and the enterprise computing environment <b>103</b>. For example, an operator of the management service <b>119</b> can analyze how the average speed of the network connection of the various client devices <b>106</b> associated with an enterprise compares with other enterprises or is the cause of errors experienced by users of the enterprise.

0044The management service <b>119</b> can also determine whether a network speed of a network connection of a client device <b>106</b> violates a particular compliance rule <b>136</b> associated with the enterprise of the client device <b>106</b> or a user account associated with the client device <b>106</b>. If so, then the management service <b>119</b> can identify an action associated with the compliance rule <b>136</b> and can issue a command to the client device <b>106</b> instructing the client device <b>106</b> to take the prescribed action. The action can be executed by the management component <b>143</b> associated with the client device <b>106</b>. In some examples, the network testing application <b>139</b> can provide the test results to the management component <b>143</b> executed by the client device <b>106</b>, which can also determine whether a compliance rule <b>136</b> specifies an action that should be taken in response to the result of a network speed test.

0045Reference is now made to <figref idref="DRAWINGS">FIG. 2</figref>, which depicts a sequence diagram illustrating one example of interactions between an enterprise computing environment <b>103</b>, client device <b>106</b> and a network testing endpoint <b>105</b> according to one example. <figref idref="DRAWINGS">FIG. 2</figref> illustrates an example of a client device <b>106</b> obtaining a network test profile <b>157</b> from a management service <b>119</b> and initiating a network speed test with a network testing endpoint <b>105</b>.

0046As denoted by step <b>201</b>, the client device <b>106</b> can initiate enrollment with the management service <b>119</b>. In response to enrollment of the client device <b>106</b>, the management service <b>119</b> can generate a network testing profile <b>157</b> for the client device <b>106</b> as shown by step <b>203</b>. The management service <b>119</b> can generate the network testing profile <b>157</b> that specifies a schedule that the network testing application <b>139</b> should employ to conduct network speed tests. The network testing profile <b>157</b> can also identify a particular network testing endpoint <b>105</b> with which the network testing application <b>139</b> should conduct network speed tests.

0047At step <b>207</b>, the management service <b>119</b> can transmit the network test profile <b>157</b> to the network testing application <b>139</b>. As shown by step <b>209</b>, the network testing application <b>139</b> can initiate a network speed test with a network testing service <b>126</b> executed by a particular network testing endpoint <b>105</b>. As noted above, the network testing endpoint <b>105</b> can be located within a proxy server providing access to a private network on which the management service <b>119</b> is executed or at an entry point into the private network. At step <b>211</b>, the network testing service <b>126</b> can generate a test packet that can be exchanged between the network testing application <b>139</b> and network testing service <b>126</b> and from which a network speed of a network connection of the client device <b>106</b> can be determined. At step <b>213</b>, the network testing service <b>126</b> can transmit the test packet to the network testing application <b>139</b>. The network testing application <b>139</b> can return the test packet as shown by step <b>215</b>. It should be appreciated that in some scenarios, the network testing application <b>139</b> can generate a test packet that is transmitted to the network testing service <b>126</b> rather than the scenario that is depicted in <figref idref="DRAWINGS">FIG. 2</figref>.

0048As shown by step <b>217</b>, the network testing service <b>126</b> can determine a speed associated with the exchange of the test packet and transmit a test result to the network testing application <b>139</b>. The network testing application <b>139</b> can then transmit the test results to the management service <b>119</b> as shown by step <b>219</b>. It should be appreciated that in some scenarios, the network testing service <b>126</b> can transmit the test results to the management service <b>119</b>. The management service <b>119</b> can determine whether the speed reflected in the test results causes a compliance rule <b>136</b> associated with the enterprise to be violated. If so, then the management service <b>119</b> can transmit a command reflecting an action that the client device <b>106</b> should take as shown by step <b>221</b>.

0049Referring next to <figref idref="DRAWINGS">FIG. 3</figref>, shown is a flowchart that provides one example of the operation of a portion of the management service <b>119</b> according to various examples. It is understood that the flowchart of <figref idref="DRAWINGS">FIG. 3</figref> provides merely an example of the many different types of functional arrangements that can be employed to implement the operation of the portion of the management service <b>119</b> as described herein. As an alternative, the flowchart of <figref idref="DRAWINGS">FIG. 3</figref> can be viewed as depicting an example of elements of a method implemented in the enterprise computing environment <b>103</b> (<figref idref="DRAWINGS">FIG. 1</figref>) according to one or more examples.

0050Beginning at step <b>303</b>, the management service <b>119</b> can facilitate enrollment of a client device <b>106</b> as a managed device associated with a particular enterprise. At step <b>306</b>, the management service <b>119</b> can generate a network testing profile <b>157</b> that identifies a schedule that the client device <b>106</b> should perform network speed tests as well as identify a network testing endpoint <b>105</b> with which network speed tests should be performed. At step <b>309</b>, the management service <b>119</b> can transmit the network test profile <b>157</b> to the network testing application <b>139</b>.

0051At step <b>312</b>, the management service <b>119</b> can obtain a test result associated with speed tests conducted by the network testing application <b>139</b> executed by a client device <b>106</b>, which can be saved in the data store <b>116</b> as network test data <b>133</b>. At step <b>315</b>, the management service <b>119</b> can determine whether the speed reflected in the test result received from the client device <b>106</b> implicates a compliance rule <b>136</b>. If so, then at step <b>318</b>, the management service <b>119</b> can transmit a command to the client device to implement an action specified by the compliance rule <b>136</b>. Otherwise, the process can proceed to completion.

0052With reference to <figref idref="DRAWINGS">FIG. 4</figref>, shown is a flowchart that provides an example of a portion of the operation of the network testing application <b>139</b> according to various examples. In particular, <figref idref="DRAWINGS">FIG. 4</figref> provides an example of the network testing application <b>139</b> obtaining a network testing profile <b>157</b> and initiating speed tests to assess the speed of a network connection of the client device <b>106</b>. As an alternative, the flowchart of <figref idref="DRAWINGS">FIG. 4</figref> can be viewed as depicting an example of elements of a method implemented in the network testing application <b>139</b> according to one or more examples.

0053At step <b>403</b>, the network testing application <b>139</b> can obtain a network testing profile <b>157</b> from the management service <b>119</b>. As noted above, the network testing profile <b>157</b> can specify a testing schedule as well as identify a network testing endpoint <b>105</b> with which the network testing application <b>139</b> should conduct one or more network speed tests. At step <b>406</b>, the network testing application <b>139</b> can determine a schedule for conducting network speed tests from the network testing profile <b>157</b>.

0054At step <b>409</b>, the network testing application <b>139</b> can initiate a network speed test with a network testing endpoint <b>105</b> identified by the network testing profile <b>157</b>. At step <b>412</b>, the network testing application <b>139</b> can transmit a test result associated with the network speed test to the management service <b>119</b>. At step <b>415</b>, the network testing application can obtain a command associated with a test result from the management service <b>119</b> or determine, from the network speed test, that an action is required based upon a compliance rule <b>136</b> specifying an action in response to a determination of the speed of the network connection of the client device <b>106</b>. At step <b>418</b>, the network testing application <b>139</b> can facilitate implementation of an action specified by a compliance rule <b>136</b> should the speed of the network connection implicate a compliance rule <b>136</b>. Otherwise, the process can proceed to completion.

0055With reference to <figref idref="DRAWINGS">FIG. 5</figref>, shown is a flowchart that provides an example of a portion of the operation of the network testing application <b>139</b> according to various examples. In particular, <figref idref="DRAWINGS">FIG. 5</figref> provides an example of the network testing application <b>139</b> initiating speed tests according to a network testing profile <b>157</b> to assess the speed of a network connection of the client device <b>106</b>. As an alternative, the flowchart of <figref idref="DRAWINGS">FIG. 5</figref> can be viewed as depicting an example of elements of a method implemented in the network testing application <b>139</b> according to one or more examples.

0056At step <b>503</b>, the network testing application <b>139</b> can determine from a network testing profile <b>157</b> whether a scheduled network speed test should be conducted. If so, then at step <b>506</b>, the network testing application <b>139</b> can initiate a network speed test with a network testing endpoint <b>105</b> identified by the network testing profile <b>157</b>. At step <b>509</b>, the network testing application <b>139</b> can transmit a test result associated with the network speed test to the management service <b>119</b>. At step <b>512</b>, the network testing application can obtain a command associated with a test result from the management service <b>119</b> or determine, from the network speed test, that an action is required based upon a compliance rule <b>136</b> specifying an action in response to a determination of the speed of the network connection of the client device <b>106</b>. At step <b>515</b>, the network testing application <b>139</b> can facilitate implementation of an action specified by a compliance rule <b>136</b> should the speed of the network connection implicate a compliance rule <b>136</b>. Otherwise, the process can proceed to completion.

0057The flowcharts of <figref idref="DRAWINGS">FIGS. 3-5</figref> show examples of the functionality and operation of implementations of components described herein. The components described herein can be embodied in hardware, software, or a combination of hardware and software. If embodied in software, each element can represent a module of code or a portion of code that comprises program instructions to implement the specified logical function(s). The program instructions can be embodied in the form of, for example, source code that comprises human-readable statements written in a programming language and/or machine code that comprises machine instructions recognizable by a suitable execution system, such as a processor in a computer system or other system. If embodied in hardware, each element can represent a circuit or a number of interconnected circuits that implement the specified logical function(s).

0058Although the flowcharts show a specific order of execution, it is understood that the order of execution can differ from that which is shown. For example, the order of execution of two or more elements can be switched relative to the order shown. Also, two or more elements shown in succession can be executed concurrently or with partial concurrence. Further, in some examples, one or more of the elements shown in the flowcharts can be skipped or omitted. The enterprise computing environment <b>103</b>, the client device <b>106</b>, the network testing endpoint <b>105</b>, and/or other components described herein can each include at least one processing circuit. The processing circuit can include, for example, one or more processors and one or more storage devices that are coupled to a local interface. The local interface can comprise, for example, a data bus with an accompanying address/control bus or any other suitable bus structure. The client device <b>106</b> or the computing devices or servers in an enterprise computing environment <b>103</b> can also include a network interface facilitating communication via the network <b>113</b>. For example, the network interface can also allow a computing device or server in an enterprise computing environment <b>103</b> to transmit or receive data, such as test results associated with a network test, from the client device <b>113</b>.

0059The one or more storage devices for a processing circuit can store data and/or components that are executable by the one or more processors of the processing circuit. For example, the management service <b>119</b>, the network testing application <b>139</b>, the network testing service <b>126</b>, and/or other components can be stored in one or more storage devices and be executable by one or more processors. Also, a data store, such as the data store <b>116</b> and/or the storage provider data store <b>146</b>, can be stored in the one or more storage devices.

0060The management service <b>119</b>, the network testing application <b>139</b>, the network testing service <b>126</b>, and/or other components described herein can be embodied in the form of hardware, as software components that are executable by hardware, or as a combination of software and hardware. If embodied as hardware, the components described herein can be implemented as a circuit or state machine that employs any suitable hardware technology. The hardware technology can include one or more microprocessors, discrete logic circuits having logic gates for implementing various logic functions upon an application of one or more data signals, application specific integrated circuits (ASICs) having appropriate logic gates, programmable logic devices (e.g., field-programmable gate array (FPGAs) and complex programmable logic devices (CPLDs)).

0061Also, one or more or more of the components described herein that comprise software or program instructions can be embodied in any non-transitory computer-readable medium for use by or in connection with an instruction execution system such as, for example, a processor in a computer system or other system. The computer-readable medium can contain, store, and/or maintain the software or program instructions for use by or in connection with the instruction execution system.

0062A computer-readable medium can comprise a physical media, such as, magnetic, optical, semiconductor, and/or other suitable media. Examples of a suitable computer-readable media include, but are not limited to, solid-state drives, magnetic drives, flash memory, etc. Further, any logic or component described herein can be implemented and structured in a variety of ways. For example, one or more components described can be implemented as modules or components of a single application. Further, one or more components described herein can be executed in one computing device or by using multiple computing devices.

0063It is emphasized that the above-described examples of the present disclosure are merely examples of implementations to set forth for a clear understanding of the principles of the disclosure. Many variations and modifications can be made to the above-described examples without departing substantially from the spirit and principles of the disclosure. All such modifications and variations are intended to be included herein within the scope of this disclosure.