The DEX Agent suppoert Microsoft Windows 10 and 11. Additional OS support will be added in future updates.
DEX Agent includes an application running as a background Windows service. In addition, computing devices having an Intel WiFi chipset, there will also be an Intel Connectivity Analytics (ICA) Service.
Both of these services report data to the Wyebot cloud infrastructure hosted in Amazon Web Services (AWS). Data is also sent to the Intel cloud separately. Personally Identifiable Information (PII) is stored in hashed form within the Intel cloud infrastructure.
Yes, DEX Agent is able to collect and report on:
At the time of software installation of the software, the user is presented with an End-User License Agreement (EULA), which must be accepted before software installation will proceed.
No, Wyebot does not sell any customer data to 3rd party vendors.
Both DEX Agent and ICA are designed with efficiency in mind, so as not to slow down compute devices, like laptops and desktop computers.
In typical operation, we see approximately 100-300 megabytes of RAM utilization, and less than 1% CPU utilization - this is total for both ICA and the DEX Agent service.
The DEX Agent service collects data reported by the Intel Connectivity Application (ICA) and/or Microsoft Windows Operating System. Some of the data reported by ICA is Intel proprietary, and only available to select Intel partners (Wyebot being one of them).
In addition, the DEX Agent has the ability to run a variety of synthetic network tests, including:
The above tests can be configured by the IT administrator to run at periodic intervals, as well as On-Demand.
In order to use the Microsoft Teams test, the devices also need to install the Microsoft Teams Network Assessment Tool. For instructions, refer to this knowledge base article: Installing Microsoft Teams Network Assessment Tool.
This depends on the IT policy of your organization. In the first release, we do not plan to have a local User Interface to interact with the DEX Agent service. At a later time, this may be possible.
The DEX Agent service transmits and receives very small amounts of data, in the order of a few kilo-bits per second, when averaged out. By default, a small amount of data will be sent once every 10 minutes.
No, the DEX Agent will never wake up the computer to do its job. It will only run if the computer is already awake. If there are any network tests that are scheduled to run on a periodic interval, they will only run when the computer is awake.
No. By default, the DEX Agent will never trigger a network scan by itself. An IT administrator will have the ability to trigger a network scan remotely. This is typically done when support staff is trying to help out a remote worker.
After a customer purchases software licenses from Wyebot, a login will be created for the DEX Agent dashboard, which has a link to download the installer file. This installer can be distributed by the customer to its employees in any way. It can be pushed via a Windows Group Policy, or posted on an Intranet website, from where employees may download and install on their own.
Post-installation, a device-specific certificate is generated which allows the desktop/laptop to communicate with Wyebot cloud service.
DEX Agent dashboard allows each customer the ability to deactivate any specific device license. After deactivation, any future attempts to communicate with the Wyebot cloud are rejected until the license is reactivated again.
DEX Agent licensing is a floating license model, meaning a customer purchases N licenses, and these are added to your account. Each time a device using the customer-specific image contacts the Wyebot cloud, one license is consumed. Once all licenses are used up, no additional devices can be activated within that customer’s account, until more are added, or previously used devices / licenses are deactivated.
The DEX Agent will run network tests using the same interface a client machine is connected to, including wired ethernet connections.
When a new customer (for example, Company X) purchases licenses of the agent software, Wyebot will generate a customer-specific EXE file, which will be available for download from your DEX Agent dashboard. The customer/partner may download that executable and make it available to their end users (employees / students, etc.) by their preffered distribution method. When a user installs that binary and starts communicating with the Wyebot cloud, it automatically identifies the device as belonging to “Company X”, and claims a license from the available “Company X” pool, if available.
All DEX Agent backhaul traffic is sent to our cloud via the following ports and hostnames. Please note that the amazonaws.com host is a load-balanced endpoint, which will resolve to many different IP addresses.
| Type | Port | Host |
|---|---|---|
| MQTT | 8883 | a2txh3sp638hu4-ats.iot.eu-west-1.amazonaws.com |
| TCP | 443 | a2txh3sp638hu4-ats.iot.eu-west-1.amazonaws.com |
The DEX Agent will initially send traffic over port 8883. If the port 8883 traffic is not allowed, it will send the same traffic over port 443. Therefore, only one of these ports needs to be allowed for communication to establish.
For public IP address reporting - at least one of these hostnames must be available:
| Host | Protocol | Port |
|---|---|---|
| checkip.amazonaws.com | HTTPS | 443 |
| ipinfo.io | HTTPS | 443 |
| icanhazip.com | HTTPS | 443 |
| api.ipify.org | HTTPS | 443 |
For Intel Telemetry Data
| Host | Protocol | Port |
|---|---|---|
| sur.telemetry.intel.com | HTTPS | 443 |
| 52.38.251.40 | HTTPS | 443 |
| 34.215.222.122 | HTTPS | 443 |
| 52.13.180.223 | HTTPS | 443 |
When a previously registered device is deleted using the Wyebot cloud interface, the device-specific certificate that was generated at the time of initial enrollment is deleted from the cloud side. This means that the device will need to re-register by uninstalling the Wyebot software and re-installing the software, thus generating a new device-specific certificate
When a new version of the DEX Agent client software is available, it is automatically pushed to end users as an update. If a new update has been downloaded, it will install on the next reboot of the client machine so as to not disrupt the client experience.
No. The only EULA a user agrees to is provided by Wyebot. Intel is not responsible for any data collected, and/or shared with them via the Wyebot Client application. The fact that Wyebot may share data with Intel will be covered in the Wyebot EULA. There is no option to stop sharing data with Intel. If a user does not agree with this data sharing agreement between Wyebot and Intel, they may choose not to accept the Wyebot EULA.
If Wyebot chooses to share data with another 3rd party, the EULA will be updated to indicate that.
We include a list of licenses in the DEX Agent installer in C:\Program Files\WyebotInc\WyebotSensorPC\NonWyebotLicenses.
We also use some 3rd party, open-source software as part of our Web Interface. Those licenses can be found here